tessellation should not be fixed in recipe

[eugene]

currently, the tessalation used by the warp analysis is determined from the tessalation list in the camera.config file. each tessalation listed is used. this is too limiting; the tessalation should be specified as part of the input parameters to the warp stage; they can then be selected for a given exposure on the basis of some other information. For example, the routine (pantasks level) which defines new warp runs can examine things like the OBJECT, the otis script, or the (yet undefined) survey / observation sequence keywords to choose the tessalation. or alternatives can be chosen manually.

[Paul Price]

I believe we are going to have the tessellation for a particular exposure specified upon registration.

[Paul Price]

Desired tess_id is now specified in the database for a newExp, and tracked through to the warp. I don't think there's a capability to set it in the register task, so we need to think about how it's initially set.

warp_overlap.pl no longer iterates over multiple possible tessellations, but uses the provided tessellation.

[eugene]

tess_id can be added at inject (pxinject -newExp), and there is supposed to be an option to set it differently with -queue for each of the science stages.

the option -set_tess_id is defined for camtool -queue, warptool -definerun, but not for chiptool -queue.

gene

[Paul Price]

OK, then, I think we can call this resolved.