OITools Roadmap

Updated: 20/10/2017

In progress:

• Project documentation
• Personal presentation
• New features for OITOOLS 2 : Units

In Study:

• OIFitsValidator enhancements
• Nom.tam.fits update
• Github

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)

Project documentation

• Complete the changelog & documentation wiki pages
  • Project documentation
• API Usage Tutorial ?
• Javadoc
• Complete / create new schema ?

New features for OITOOLS 2

Units: [IN PROGRESS]

Description:

• Units handling: In OIFITS V2, the physical units for few columns are 'user-defined' i.e. given in the column description (TUnit keyword). OITools already parse column keywords but does not store such units in the column meta data
• Impacted columns are:
  • OI_VIS table: RVIS (RVIS_ERR), IVIS (IVIS_ERR) and VISDATA (VISERR)
  • OI_FLUX table: FLUXDATA

Study:

• Currently units are implemented by an Enumeration that is not extendable !
• Possible choices:
  • 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 serve again. 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. They will directly store and manage here.

Impacts:

• unit parsing & validation : OIFitsLoader
• OIFitsExplorer : Display of column units
• writing or rewriting files

Feedback:

• 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. The units are recover directly from OIFits files.
• FitUnit reporting units for images, Merge Units and FitsUnit ?

Checksum/Datasum

TODO: description & study

Management of dimensions (NWaves)

TODO: description & study

Extra table/column

TODO: study

OI_INSPOL rules

TODO: description & study

OIFitsValidator enhancements: [IN PROGRESS]

Description:

• A validation suitable for OIFITS Version 2.
• An error message more provided of information and more explicit. As well as a clearer display and more exploitable for users (filter).
• The ability to re-use error messages (xml)
• Update test to compare the validation results.

Study:

Impacts:

• OIFitsChecker
  • in creating error messages and validation
  • to define error profiles
• OIFitsExplorer for the error message display and the implementation of a filter
• OIFitsValidatorTest test save & compare validation results
• getCheckReport() is used in OITools, Aspro2, LITpro, OImaging, OIFitsExplorer
• OIVal & OIDB to the re-use of xml error messages

Feedback:

Validation messages

• 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

TODO: description & study

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

GitHub

TODO: description & study

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