EranOfek
commented
4 months ago AstroPack version is stored in proc images by pipeline
On Sun, 9 Jun 2024 at 18:38 EastEriq @.***> wrote:
Context: PolishookDavid/LAST_OCS#28 https://github.com/PolishookDavid/LAST_OCS/issues/28
Problem: record together with the images observed the version identifiers of all software components which contributed to the process. Among them, we should store the version/tag of Astropack in use for acquisition.
For the various classes I maintain, which inherit from LAST_Handle, I have created an utility function https://github.com/EastEriq/LAST_Handle/blob/mastrolindo/%2Bobs/%2Butil/%2Btools/getgitversion.m, and solved the problem for all my instument and abstract class. I'm just missing AstroPack.
It will be trivial for me to call such a function also against AstroPack on creation of unitCS, so to store also that key. For that I would need an absolute path to a file of the AstroPack repo (robust to all vagaries of installation, perhaps derived from the startup script), or the name of an AstroPack function which is immutable throughout the life of the universe (I could use which, i.e. which('celestial.time.julday')). What would you suggest?
— Reply to this email directly, view it on GitHub https://github.com/EranOfek/AstroPack/issues/455, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABJUQ4M4NSYFO6AQWVVRNULZGRZGBAVCNFSM6AAAAABJA7NRU6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGM2DEMZUGE3TOMI . You are receiving this because you are subscribed to this thread.Message ID: @.***>
EastEriq
Context: https://github.com/PolishookDavid/LAST_OCS/issues/28
Problem: record together with the images observed the version identifiers of all software components which contributed to the process. Among them, we should store the version/tag of Astropack in use for acquisition.
For the various classes I maintain, which inherit from LAST_Handle, I have created an utility function https://github.com/EastEriq/LAST_Handle/blob/mastrolindo/%2Bobs/%2Butil/%2Btools/getgitversion.m, and solved the problem for all my instument and abstract classes. I'm just missing AstroPack.
It will be trivial for me to call such a function also against AstroPack on creation of unitCS, so to store also that key. For that I would need an absolute path to a file of the AstroPack repo (robust to all vagaries of installation, perhaps derived from the startup script), or the name of an AstroPack function which is immutable throughout the life of the universe (I could use
which, i.e.which('celestial.time.julday')). What would you suggest?