20230321 - CARS Webinar - ATLAS soft
===
###### tags: `Templates` `Meeting`
:::info
- **Location:** Visio
- **Date:** Mar 21, 2023 2:00 PM (CET)
- **Agenda**
1. ATLAS presentation `45min`
> [name=Nikos SIomos]
- **Participants:**
- CP (CP)
- ACTRIS Community
- **Contact:** Max <nnicol>
- **Host:** DN
- **Reference:** - [Webinar link](/s/template-meeting-note)
:::
:dart: Goals
---
- Installation and Using ATLAS
- Preapration training course in Bucharest
:closed_book: Tasks
--
==Importance== (1 - 5) / Name / **Estimate** (1, 2, 3, 5, 8, 13)
### Development Team:
- [ ] ==5== Email invite
- [x] ==4== Email registration page **5**
- [ ] ==5== Email invitees **3**
- [ ] ==4== Setup e2e test in production **2*
:notebook_with_decorative_cover:Notes
---
<!-- Other important details discussed during the meeting can be entered here. -->
- ATLAS=AuTomated Lidar Analysis Software
- Folders drt and nrm to put data. no moatter path
- tlc, north east etc...
- polar cal: pcb with -45 and +45
- radiosonding: could be .txt files but future it could handle scc nc files
- !!!! configuration ATLAS overwrites Licel raw headers
- OK if both telescope
- SIRTA uses different file names for normal RM, Dark, depolar etc... --> ATLAS handle that as long as everything is in the correct folder
- Present foder paths options
- Discussed and show rayleigh fit
- Discussed and shows telecover (sevral iteration possible)
- Discussed and show depolar cal
- Victor present the ATLAS GUI but still command line is still ok but still under development
:tongue:Q&A excanges
---
from Chris to Everyone14:11
Just one remark: all your raw files have the same names, rm...., rm...., rm....
from Volker to Everyone14:12
Which name do the tlc ring folders haveß
from Dominika Szczepanik, UW to Everyone14:13
How many rounds for telecover one can upload to ATLAS?
from Chris to Everyone14:13
Hummmmmm. We made the choice to change that because it could be confuse in the future..... With Licel you can change.... We have RM, DP, DM, TC etc..... which is much better. Don't know. It might help others. ATLAS can handle that? or the files should always be RM....... etc....?
from Alejandro Rodríguez UPC to Everyone14:13
Is there documentation about this file structure?
from Holger Baars TROPOS to Everyone14:14
in case no radiosonde is available, will ECMWF model profiles be valid as well?
from Holger Baars TROPOS to Everyone14:19
to clarify: Station ID and Lidar ID will be something different, right?
from Aldo Amodeo, CNR-IMAA to Everyone14:22
polarization folder is only for cross and parallel channels or also for cross and total?
from Aldo Amodeo, CNR-IMAA to Everyone14:22
if we have two or more telescopes, we should provide a set of folder for each telescope?
from bernd to Chris (privately)14:23
You are aware of the prefix variable at https://licel.com/manuals/ethernet_pmt_tr.pdf#page.66 ?
from Alejandro Rodríguez UPC to Everyone14:23
Ok
from Chris to Everyone14:24
Dear Aldo: at SIRTA we have both telescope in same raw files..... BT and BC numbers are different so I assume we should use same raw files for both telescope . ANd I assume ATLAS config files should handle that..... Nikos? you agree?
from bernd to Chris (privately)14:26
and the SETFIRSTLETTER command from the remote API ( https://licel.com/manuals/ethernet_pmt_tr.pdf#page.180)
from Chris to bernd (privately)14:26
Yep,,,,, bernd. This is what I meant. We use the Licel prefix to change our filera names. This is why I asked if ATLAS will handle that.....
from Aldo Amodeo, CNR-IMAA to Everyone14:28
Thanks
from Chris to Everyone14:34
At the end of the presentation (not now.... but just not to forgot) what is the status of ATLAS installation in personal computer? shared servers ? etc... We should be able to do wget .... something or git install .... something or anaconda .... something ...pip something.... Either way but it should be straightforward.
from Volker to Everyone14:35
@Chris and @Aldo: if signals from different telescopes are in the same LICEL file, they are just different channels - no matter what telescope.
from Chris to Everyone14:35
As well as upgrade should be easy. If you ugrade the soft. User should be easily update their version..... Is it the case currentley?
from Chris to Everyone14:36
In our institute, this theonly way to convince our computer/network guys to spend dome times to implement our tools in our platforms.
from Volker to Everyone14:39
Does the radisonde have a date?
from Adolfo Comerón, UPC to Everyone14:41
I see that the normalization (Rayleigh fit) region seems to be given in km. Ranges in other parts were in m. Wouldn't it be better to use the same units eveywhere to avoid confusion?
from bernd to Everyone14:42
I would rather put units in variables names if possible
from Chris to Everyone14:42
OK. I have my answer.....if it is github, no problem...
from Chris to Everyone14:44
Yep, ut with git it is nice since you can keep previous version and deploy new version and see the difference. But at least you can keep what you've done before....
from Alejandro Rodríguez UPC to Everyone14:46
If the Rayleigh fit region has to be specified... a Rayleigh fit needs to be done before entering the data into ATLAS, I presume.
from Aldo Amodeo, CNR-IMAA to Everyone14:46
The config file plans to have use the same height range for all the channels for Rayleigh fit calibration and for telecover normalization?
from Chris to Everyone14:48
This is because you deal with raw files....... However you convert raw files to netcedf (same as scc). If you do so, then dealing with units should be straightforward using CF convention.... Am I right ? or not?
from Pedro Catalan Valdelomar to Everyone14:49
Hello Nikos, I am so sorry because I had a technical problem and a I joined to the meeting late. Have you talked about the hardware requirements of ATLAS?
from Vanda Salgueiro to Everyone14:57
Hello! Maybe this is a basic question, but I didn't understand. In a same pollyXT file.nc we have telecover and polarization measurements. How to tell to Atlas where are these measurements in the file? Do we have to indicate the time corresponding to the measurement for telecover, for example? Or do we have to do files with these data? Or Atlas can detect them automatically?
from Chris to Everyone15:01
I see
from Volker to Everyone15:02
How much RAM is recommended?
from Pedro Catalan Valdelomar to Everyone15:02
What kind of graphic card? I tell you because we have a problem with gpu library.
from Chris to Everyone15:04
As I said, the best would be to rely on Licel software. You can change the two first digits of the files. This makes things much more easier for later analysis.....Bernd confirmed....
from Maria Filioglou, FMI to Everyone15:05
We perform telecover test for each sector separately so N,S,E,W and N again will be in 5 different files one for each sector
from Chris to Everyone15:05
you can also change the header to indicate if it is depolar +45 or depolar -45
from Chris to Everyone15:07
One thing we can feedback to Licel is that the sensitivity of the tuning is low: 2 digits for the file names, only station names in header.... wth 8 digits. so exemple:SIRTAP45 SIRTAN45 SIRTA-NO SIRTA-EA etc....
from Holger Baars TROPOS to Everyone15:08
I think we can discuss solutions later
from Holger Baars TROPOS to Everyone15:09
both is possible,
from Daniele Bortoli - UEVORA to Everyone15:09
Holger, please, think also to the old Evora system!!!
from Holger Baars TROPOS to Everyone15:10
@daniele: For sure! but if old or not, should not afftect the telecover...
from Holger Baars TROPOS to Everyone15:15
we will discuss with Nikos what is best for him (ATLAS)
from Alejandro Rodríguez UPC to Everyone15:15
We still have to send Nikos a sample of our new format. My apologies.
from Johannes Speidel KIT to Everyone15:27
Will the python environment also be accessible within the github repository in order to avoid version conflicts?
from Holger Baars TROPOS to Everyone15:29
Nikos, could you provide the toml file which packages and versions are needed?
from Aldo Amodeo, CNR-IMAA to Everyone15:31
Does this mean that we must use only the indicated package versions?
from Nikos Papagiannopoulos CNR-IMAA to Everyone15:33
Nikos, did you test it for windows/macos?
from Holger Baars TROPOS to Everyone15:46
I have to leave sorry! Thanks for the great introduction!
from Adolfo Comerón, UPC to Everyone15:46
What do you call "iteration" in the telecover test?
from Chris to Everyone15:48
I think it is several telecover procedure in a raw (2, 3 more.....)
from Ioana Popovici to Everyone15:51
Does ATLAS do the GHK calculations or the user must provide them in the config_file?
from Ioana Popovici to Everyone15:53
Ok, thank you.
from National Institute of R&D for Optoelectronics to Everyone15:54
https://www.actris.eu/topical-centre/cars/announcements-resources/documents
rom National Institute of R&D for Optoelectronics to Everyone15:54
this is where you can find documentation and tools, including the GHK calculator