Changes

Page history
Update Team Meeting minutes authored by Moreau Nicolas's avatar Moreau Nicolas
Hide whitespace changes
Inline Side-by-side
02-10-2021.md
View page @ ee942dd5
--- ---
title: "Meeting minutes" title: Team Meeting minutes
author: [Philippe Salome] author:
date: "2021-10-03" - Philippe Salome
subject: "Markdown" date: '2021-10-03'
keywords: [Meeting, Minutes] subject: Markdown
subtitle: "Attendees : M. Caillat, N. Moreau, P. Salome" keywords:
lang: "en" - Meeting
page-background: "backgrounds/background1.pdf" - Minutes
... subtitle: 'Attendees : M. Caillat, N. Moreau, P. Salome'
lang: en
# Meeting minutes page-background: backgrounds/background1.pdf
---
## Attendees : M. Caillat, N. Moreau, P. Salome
# Meeting minutes
Short term perspective : deliver a stable version to IRAM for an open access to users via IRAM on ## Attendees : M. Caillat, N. Moreau, P. Salome
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. Short term perspective : deliver a stable version to IRAM for an open access to users via IRAM on
Large Program data for beginning of 2022. Discussion about the last debugs. PCMI conference, ADASS XXXI Meeting.
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 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.
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.
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.
## Documentation
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.
Several level of documentation have been discussed/identified
## Documentation
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 Several level of documentation have been discussed/identified
3. User-Level : In separated documents (pdf, screen capture with indications, text in the webpage, videos...)
1. Developper-Level : Inside the code, use sphinx (python) and javadoc (js). Standards are defined in the gitlab wiki
Open question: should we buy a license for pycharm (200e). It is possible to do so if useful. 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...)
## Unit-test
Open question: should we buy a license for pycharm (200e). It is possible to do so if useful.
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).
## Unit-test
## Organisation
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).
- 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. ## Organisation
- The stable version must be robust.
- Issues/New features should all be via gitlab Issues. Add specific Tags if needed.
## To do List - 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.
- 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. ## To do List
- 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) - 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"
- 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". - 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.
- 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 ... - Help 3D : add the link to the video (tips)
- Yafitssel : add the possibility to export the results in a csv format - 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".
## New feature - 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
```java
After the documentation and the robustness of the Stable version. The first priority identified ## New feature
for IRAM is to add in Yafits the possibility to display spectrum only (no image, no interaction)
``` ```java
After the documentation and the robustness of the Stable version. The first priority identified
## Next meeting for IRAM is to add in Yafits the possibility to display spectrum only (no image, no interaction)
```
10/11/2021 at 1.30pm
## Next meeting
[minutes_021021.pdf](uploads/5e6caa20cab617f804c6633775090e52/minutes_021021.pdf)
10/11/2021 at 1.30pm
PDF generated by
[minutes_021021.pdf](uploads/5e6caa20cab617f804c6633775090e52/minutes_021021.pdf)
```java
pandoc minutes_021021.md -o minutes_021021.pdf --from markdown --template eisvogel --listings PDF generated by
```java
pandoc minutes_021021.md -o minutes_021021.pdf --from markdown --template eisvogel --listings
``` ```
\ No newline at end of file