-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SOFTWARE and VERSION #10
Comments
Up to now, there is no way to know which software was used to create an OI-Interface image. We could use an heuristic to infer it but I think, it should be in the standard somehow |
The ESO standard is: PROCSOFT Indicates the reduction software system including its version number used |
Ok. PROCSOFT keyword may be already used by the reduction pipeline. As an example, PIONIER oifits files contains in the primary header : |
I think its clear from the context of being in a different hdu. |
there is already VERSION ? |
There in no eso keyword for version. The version number seems to be usually added to the software name in the PROCSOFT keyword |
Now that I have the hands in MiRA, I am going to give a try to
|
For bsmem see https://gitlab.com/jsy1001/bsmem/-/issues/9 |
I've implemented |
I created an issue for OImaging JMMC-OpenDev/oimaging#96 |
What would be the version of Wisard at any moment? At the moment it is 3.2.2 . This is not an internal Wisard number, it is a Github release number triggered by Laurent. It would be nice to have PROCSOFT set to the release number 'automatically'. Since the number is a string, I figure a GH script could insert the actual release number in the Wisard "code", as it is not compiled but just a procedure. |
Ok. That seems doable, it is probably just a few lines to add in the dockerfile : https://github.com/JMMC-OpenDev/oimaging-uws-server/blob/master/runtime/docker/oiservices/Dockerfile |
We should document this usage of PROCSOFT in the specification document. |
We should add a software (or algorithm) and software version keywords in
IMAGE-OI OUTPUT PARAM
:SOFTWARE
SOFT_VER
The text was updated successfully, but these errors were encountered: