|  | --- |  | --- | 
|  | title: "Meeting minutes" |  | title: "Meeting minutes" | 
|  | author: [Philippe Salome] |  | author: [Philippe Salome] | 
|  | date: "2021-10-03" |  | date: "2021-11-10" | 
|  | subject: "Markdown" |  | subject: "Markdown" | 
|  | keywords: [Meeting, Minutes] |  | keywords: [Meeting, Minutes] | 
|  | subtitle: "Attendees : M. Caillat, N. Moreau, P. Salome" |  | subtitle: "Attendees : Y.-A. Ba, M. Caillat, N. Moreau, P. Salome" | 
|  | lang: "en" |  | lang: "en" | 
|  | page-background: "backgrounds/background1.pdf" |  | page-background: "backgrounds/background1.pdf" | 
|  | ... |  | ... | 
|  |  |  |  | 
|  | # Meeting minutes |  | # Meeting minutes | 
|  |  |  |  | 
|  | ## Attendees : M. Caillat, N. Moreau, P. Salome |  | ## Attendees : Y.-A. Ba, M. Caillat, N. Moreau, P. Salome | 
|  |  |  |  | 
|  |  |  | Short term perspective : | 
|  |  |  |  | 
|  | Short term perspective : deliver a stable version to IRAM for an open access to users via IRAM on |  | ## New server | 
|  | Large Program data for beginning of 2022. Discussion about the last debugs. PCMI conference, ADASS XXXI Meeting. |  |  | 
|  |  |  |  | 
|  | It is decided that the priority will now be to document and clean up at max the current stable version. No new feature should be added but if very limited. |  | 1. Developper-Level : | 
|  |  |  | 2. Technic-level : | 
|  | It is discuss if cleanup of the code should be done with the Documentation. It is decided that is will be done in a second step. Examples are given : how the fits header are read (different kinds) inside the proc. One single format for computation should be used. The conversion to the proper format should be done elsewhere. |  |  | 
|  |  |  |  | 
|  | It has been asked to J Pety to install a Docker version > 18.09 on the IRAM server. The goal is to have the stable version of Yafits install for Nov. 15th (Victor's return). This will leave 1.5 months for tests. |  |  | 
|  |  |  |  | 
|  | ## Documentation |  |  | 
|  |  |  |  | 
|  | Several level of documentation have been discussed/identified |  |  | 
|  |  |  |  | 
|  | 1. Developper-Level : Inside the code, use sphinx (python) and javadoc (js). Standards are defined in the gitlab wiki |  |  | 
|  | 2. Technic-level : Doc Rest API, use if graphical view (data flow, class dependances...), introspection |  |  | 
|  | 3. User-Level : In separated documents (pdf, screen capture with indications, text in the webpage, videos...) |  |  | 
|  |  |  |  | 
|  | Open question: should we buy a license for pycharm (200e). It is possible to do so if useful. |  |  | 
|  |  |  |  | 
|  | ## Unit-test |  |  | 
|  |  |  |  | 
|  | NM shows how to make unit-tests. Ideally, the tests show be designed when the code is written. The idea now is to define a list of tests to make sure that the procedure are not broken by changes. There are easy tests (types, loops) and more sophisticated ones : on specific datasets (with comparison to expected values computed elsewhere). |  |  | 
|  |  |  |  | 
|  | ## Organisation |  |  | 
|  |  |  |  | 
|  | - Issues/New features should all be via gitlab Issues. Add specific Tags if needed. |  |  | 
|  | - Pay special attention to new developments to make then on dev or in new branches if significative changes are expected. |  |  | 
|  | - The stable version must be robust. |  |  | 
|  |  |  |  | 
|  | ## To do List |  | ## To do List | 
|  |  |  |  | 
|  | - Add links to Yafitssel i) in 3D top menu add a link "Show query", ii) in the 2D top menu add a link "show query" iii) in Artemix (in the >Tools menu : add an entry "Show query" |  |  | 
|  | - Homogeneity : Change the 2D top menu to make it the same as in the 3D. |  |  | 
|  | - 2D and 3D top menu in Yafits : the link is towards artemix (see more FITS files) : needs to be modified. |  |  | 
|  | - Help 3D : add the link to the video (tips) |  |  | 
|  | - Bug : after a given time, the file is no longer loaded in memory : change the error message to make it clear for the user : add "Please reload the webpage, the FITS file is no longer in memory". |  |  | 
|  |  |  |  | 
|  | - Yafitssel : add a way to prevent the return of too many lines (impossible to display), ie first 1000. Find a way to display ranges: From ...  to ... |  |  | 
|  | - Yafitssel : add the possibility to export the results in a csv format |  |  | 
|  |  |  |  | 
|  | ## New feature |  |  | 
|  |  |  |  | 
|  | ```java |  |  | 
|  | After the documentation and the robustness of the Stable version. The first priority identified |  |  | 
|  | for IRAM is to add in Yafits the possibility to display spectrum only (no image, no interaction) |  |  | 
|  | ``` |  |  | 
|  |  |  |  | 
|  | ## Next meeting |  | ## Next meeting | 
|  |  |  |  | 
|  | 10/11/2021 at 1.30pm |  | XX/12/2021 at 1.30pm | 
|  |  |  |  | 
|  | [minutes_021021.pdf](uploads/5e6caa20cab617f804c6633775090e52/minutes_021021.pdf) |  |  | 
|  |  |  |  | 
|  | PDF generated by |  | PDF generated by | 
|  |  |  |  | 
| ... |  | ... |  | 
| ... |  | ... |  |