[[PageOutline]]

== Running The !AddStar Pantasks ==

There are a few steps to get addstar running:
 * are you restarting after a db corruption, fault or move? Please see here before starting: AddstarPantasksRestart
 * the DVODB that is specified can be either a real path, or one defined in site.config. 
 * make sure the appropriate modules are loaded in addstar's pantasks (addstar.pro, minidvodb.pro, survey.pro)
 === Setting up the !ThreePi catalog ===

ThreePi's addstar runs on ipp004.  To restart
{{{
ssh ippdvo@ipp004
cd addstar
pantasks_server &
pantasks_client
server input input
setup.3pi

}}}

Now look in the gpc1 database table {{{minidvodbRun}}} and see if there is an entry for {{{ThreePi.V3}}} that has a state of 'active':

  yes: do {{{survey.addstar.off}}}

  no: do nothing it is all configured

Now type {{{run}}}

If there was no ThreePi.V3 minidvodb in 'active' state, wait until there is one, then turn survey.addstar back on.

 === Setting up the LAP catalog ===
 
The same steps as before:

LAP's addstar runs on ipp005.  To restart
{{{
ssh ippdvo@ipp005
cd addstar
pantasks_server &
pantasks_client
server input input
setup.lap

}}}

Now look in the gpc1 database table {{{minidvodbRun}}} and see if there is an entry for {{{LAP.ThreePi.20110809}}} that has a state of 'active':

  yes: do {{{survey.addstar.off}}}

  no: do nothing it is all configured

Now type {{{run}}}

If there was no LAP minidvodb in 'active' state, wait until there is one, then turn survey.addstar back on.




 === A general example ===

 * survey.add.addstar (label) (dvodb) (minidvodb_group) (stage)
 * add.minidvodb (minidvodb_group) (minidvodb) (dvodb) (interval days) (camera)
 * add.label (minidvodb_group)

 === The arguments ===

 * (label) - the label used in addtool -definebyquery to queue the exposures
 * (dvodb) - defined in site.config. This is where the final (merged) dvodb will go.
 * (minidvodb_group) - Something sensibly chosen (in this case, ThreePi). It works a bit like a label here.
 * (stage) - what stage for addstar (cam/staticsky/stack)
 * (minidvodb) - defined in site.config - this is the location where the minidvodbs will go. 
 * (interval days) - how long before the minidvodbs are rotated (there is also a cut of 500 exposures)
 * (camera) - I couldn't figure out how to suck this out of the available information, and it's needed, so you have to provide it on the command line.

 === What each task does ===

 * {{{survey.add.addstar}}} - queues the exposures using addtool
 * {{{add.minidvodb}}} - creates the minidvodbRun table (like a survey task). This is essential for minidvodbs
 * {{{add.label}}} - it's pantasks - it needs to know what label to munch on.

For other purposes, for example, if you have a different sort of query (not one that can be queued off of the label), do not run survey.add.addstar. You will still need add.minidvodb and add.label. You will have to queue the exposures using addtool 

 === Some 'by hand' examples ===

To queue a minidvodb (which will get merged automatically)


{{{
 addtool -definebyquery -destreaked -comment %SAS% -set_dvodb ROYSAS.V1 -set_minidvodb_group RoySAS.V1 -set_minidvodb -set_label RoySAS.V1 -dbname gpc1 -stage cam
}}}

in pantasks


{{{
add.minidvodb RoySAS.V1  ROYSAS.V1   ROYSAS.V1 1 GPC1
add.label RoySAS.V1 
}}}

To queue something that is not a minidvodb (this is not tested yet - I need to test it):

{{{
addtool -definebyquery -destreaked -comment %SAS% -set_dvodb ROYSAS.V1 -set_label RoySAS.V1 -dbname gpc1 -stage cam
}}}

in pantasks 

{{{
add.label RoySAS.V1 
}}}