Astromon version 1.3 promotion

[javierggt]

Standing issues

• PR Add astromon-excluded-region script, ensure revision consistency, properly determine asol filename #38
• PR Added Gaussian source detection #39
• rename the "archive" directory to "xray_observations", which means they can live side-by-side since the moment astromon is promoted in ska3-aca until it is promoted in ska3-flight.

Promotion process

• promote astromon to ska3/aca.
• create xray_observations symlink from $SKA/data/astromon
• start astromon weekly processing in ska3/aca using a custom task schedule (this produces all astromon data products in a different location, so it does not interfere with flight processing). These will be the changes to the schedule:

   <task astromon_update>
     cron       * * * * *
     check_cron * * * * *
   -  exec 1: cp $ENV{SKA}/data/astromon/astromon.h5 $ENV{SKA}/data/astromon/tmp
   -  exec 1: astromon-cross-match --archive-dir $ENV{SKA}/data/astromon/tmp --db-file $ENV{SKA}/data/astromon/tmp/astromon.h5
   -  exec 1: chown -R :aspect-kadi $ENV{SKA}/data/astromon/tmp/obs*
   -  exec 1: rsync -a --remove-source-files $ENV{SKA}/data/astromon/tmp/obs* $ENV{SKA}/data/astromon/archive
   -  exec 1: mv $ENV{SKA}/data/astromon/tmp/astromon.h5 $ENV{SKA}/data/astromon/
   -  exec 1: astromon-web-pages --out $ENV{SKA}/data/astromon/web
   +  exec 1: cp $ENV{SKA}/data/astromon/astromon.h5 $ENV{SKA}/data/astromon/tmp_aca
   +  exec 1: astromon-cross-match --archive-dir $ENV{SKA}/data/astromon/tmp_aca --db-file $ENV{SKA}/data/astromon/tmp_aca/astromon.h5
   +  exec 1: chown -R :aspect-kadi $ENV{SKA}/data/astromon/tmp_aca/obs*
   +  exec 1: rsync -a --remove-source-files $ENV{SKA}/data/astromon/tmp_aca/obs* $ENV{SKA}/data/astromon/xray_observations
   +  exec 1: mv $ENV{SKA}/data/astromon/tmp_aca/astromon.h5 $ENV{SKA}/data/astromon/rc
   +  exec 1: astromon-web-pages --out $ENV{SKA}/data/astromon/rc/web -db-file $SKA/data/astromon/rc/astromon.h5
     <check>
       <error>
         #    File                  Expression
  

• we can be in this state for as long as we want. The official processing is still in ska3/flight.
• make sure the entire mission has been reprocessed using the astromon in ska3/aca
• verify that the revision number in all observations in ska3/aca matches those in ska3/flight. Fix if needed.
• compare the data products and make sure everything is fine.
  $SKA/data/astromon/astromon.h5 and $SKA/data/astromon/rc/astromon.h5 should be equivalent (so no need to copy this on promotion)
  It is possible that there are differences here, but I hope they are not big.
• promote astromon promoted in ska3/flight
• optionally copy $SKA/data/astromon/astromon.h5 to $SKA/data/astromon/rc/astromon.h5
• change the task schedule used in astromon processing from ska3/aca processing to use the default,
• stop the astromon processing from ska3/flight
• remove $SKA/data/astromon/archive symlink