Search
Text Size:
Smaller Text Normal Text Larger Text

Facebook

Follow us on Twitter

HowTo: Re-run FIEStool when it has failed

FIEStool versions in alona

There are now a few datared folders in alona:
datared this one contains the classical GUI FIEStool
ddatared-devs this one is to play with it and test modifications before adding them to the production version
datared-headless this one contains the classical FIEStool headless version, which was running permanently just like a daemon process, it was constantly monitoring /data/fies for incoming new files
datared-headless-test this one is to play with the classical headless version and test modifications before adding them to the production version
datared-headless-argv this is the newest headless version, it is called by system daemons as "./hlFiestoll filename" everytime a new FIES file is created in /data/fies
datared-headless-argv-dev this one is to play with the new headless version and test modifications before adding them to the production version


How to re-run FIEStool when it has failed for some files


Option one: re-running it on a specific file (headless) if the file is still in /data/fies
  1. ssh to alona as postprocess ( ssh postprocess@alona )
  2. make sure the file is in /data/fies
  3. go to datare-headless-argv folder ( cd fies/datared-headles-argv )
  4. run the software by calling hlFIEStoll and giving the filename as an argument (only the filename without preceeding path) ( ./hlFIEStool filename )
  5. check /data/reduced/fies/auto for files with the same root name as your filename and the typicall _stepXX_XXX.fits extensions
  6. if something fails check for errors in textlog.log ( cat textlog.log ) and report


Option two: re-running it on a specific file (headless) if the file is in /data/fies/NightId
  1. ssh to alona as postprocess ( ssh postprocess@alona )
  2. copy the file to /data/fies
  3. wait for the headless version of FIEStool to do its job, it should start automatically and should take ~40 seconds
  4. check /data/reduced/fies/auto for files with the same root name as your filename and the typicall _stepXX_XXX.fits extensions
  5. remove the file from /data/fies
  6. if something fails check for errors in textlog.log ( cat textlog.log ) and report


Option three: re-running it with the GUI version
  1. ssh to alona as postprocess ( ssh postprocess@alona )
  2. go to the fies datared folder ( cd fies/datared )
  3. run the FIEStool software ( ./FIEStool )
  4. queue the input file(s), start the processing, and wait and see
  5. check /data/reduced/fies/manual for files with the same root name as your filename and the typicall _stepXX_XXX.fits extensions
  6. if something fails check for errors in the GUI log and report
      REMEMER: IN THIS CASE OUTPUT FILES ARE SAVED IN /DATA/REDUCED/FIES/MANUAL

Re-running for all files on a whole night


Case 1: If the night has already been archived (data is already in /data/fies/NightId, for example /data/fies/FIAe16) then:
  1. ssh to alona as postprocess ( ssh postprocess@alona )
  2. go to the fies folder ( cd fies )
  3. run the rerunpipeline script passing two arguments to it, the mode "1", and the night filename prefix as an argument (for example ./rerunpipeline 1 FIAe16 )
  4. check /data/reduced/fies/auto for files with the same root name as your filename and the typicall _stepXX_XXX.fits extensions
  5. if something fails check for errors in textlog.log ( cat textlog.log ) and report


Case 2: If the night has not been archived yet (i.e., data is still under /data/fies):
  1. proceed as before, steps 1 and 2
  2. use the mode "0" as first argument for rerunpiepline (for example ./rerunpipeline 0 FIAe16 )
  3. check /data/reduced/fies/auto for files with the same root name as your filename and the typicall _stepXX_XXX.fits extensions
  4. if something fails check for errors in textlog.log ( cat textlog.log ) and report


Case: re-running it with the GUI version
  1. ssh to alona as postprocess ( ssh postprocess@alona )
  2. go to the fies datared folder ( cd fies/datared )
  3. run the FIEStool software ( ./FIEStool )
  4. queue the input file(s), start the processing, and wait and see
  5. check /data/reduced/fies/manual for files with the same root name as your filename and the typicall _stepXX_XXX.fits extensions
  6. if something fails check for errors in the GUI log and report
      REMEMER: IN THIS CASE OUTPUT FILES ARE SAVED IN /DATA/REDUCED/FIES/MANUAL

Back to top Last modified: 19-May-2017