OITools Roadmap

The roadmap

• 20/10/2017:
  • Personal presentation: prepare the presentation of my work on OITools and the explanations of my involvement. A link to this presentation will be available after this one (9/11)
  • Review the project documentation, API Usage Tutorial.
  • Functional addition on version 2 of OITOOLS.
  • Improve the OIFitsValidator test to compare the validation results.
  • Nom.tam.fits update.
  • Github.

Roadmap Detail

Personal presentation

Project documentation

• Project documentation

Functional addition on version 2 of OITOOLS

Units:

• 23/10/2017:
  • The choice that has been made is to change the operation of Units (creating subclass) and to treat the case of special units in the loading of the file and the validation. Units are directly retrieving OIFits files.

• 20/10/2017:
• The case of the treatment of the Units must be reviewed, because in certain cases it agrees to accept any unit, currently in the form of an enumeration that does not allow us to create a permissive unit. The columns concerned by this unit are RVIS (RVIS_ERR), IVIS (IVIS_ERR) and VISDATA (VISERR) of table OI_VIS and FLUXDATA of table OI_FLUX.
• The parts impacted by this change are:
  • unit validation : OIFitsLoader
  • OIFitsExplorer : Display of column units
  • writing or rewriting files
• The choices that were discussed:
  • either realize an enum Units more permissive, in this case it will be necessary to fix the validation of the units (OIFitsLoader.parseColumn ()), choose where are store these 'special' units because this one will reserve us. Be careful because they are reused in the data display under OIFitsExplorer as well as retrieve them for writing files with WriteOifits.
  • or proceed to a rewrite of the enumeration Units in class which would allow us to be directly more permissive and to directly manage the case of these units which can vary.

Checksum/Datasum

Management of dimensions (NWaves)

Extra table/column

OI_INSPOL rules

Improve the OIFitsValidator test to compare the validation results

Message:

• checker.sever delete and create new message: pointer to file, line number, severity, declare the rule bound... (error list with full info)

Filter message

Define error profiles

• (lenient, strict, software)

Xml

• Output of the messages in xml to reuse them after, impact possible on other classes. (oival/oidb)

Viewer

• Reflection on a possible graphical panel displaying these new messages. (Widget GUI) (litpro/oixp)

Nom.tam.fits update

• We must succeed in saving our code while deleting this library

Github

• You have to open a repository and send our project on GitHub
• Licence

-- CharleenKemps - 20 Oct 2017