Difficult (impossible?) to relate expID to mysql database

[morganson]

A lot of image information seems to only be available via the mysql database (as opposed to dvo via imextract). This is probably a bug in and of itself. But in the short run, it would be good if there were an easy way to relate a detection (via mextract or even via imextract) to an image in the mysql database.

expid (from mextract) does not appear to be in the mysql database

externid (from imextract) does not appear to be in the mysql database (it is not expid, camid or chipid)

"NAME ' / name of original image'" exists in Images.dat, but is not accesible via imextract (at least not as 'NAME' or any other documented field)

Please make 'NAME' or some other reference to the exposure in the mysql database accessible via imextract (alternately, update imextract --help fields to include whatever NAME is called).

[bills]

Certainly not impossible. Arguably not difficult. Clearly obscure, and to my knowledge undocumented.

Given the imageiD for a measurement, get the externID.

dvo: imextract externID where imageID == 39805
dvo: echo externID[0]
3243814

This can be passed to chiptool to get the information about the chip processing

(ipp053:~/ipp/Ohana) bills% chiptool -processedimfile -chip_imfile_id 3243814
chipProcessedImfile MULTI

chipProcessedImfile  METADATA  
   chip_id          S64       56729          
   chip_imfile_id   S64       3243814        
   class_id         STR       XY43            
   uri              STR       neb://ipp031.0/gpc1/ThreePi.nt/2010/02/13/o5240g0511o.134997/o5240g0511o.134997.ch.56729.XY43.ch.fits 
   bg               F32       255.588        
   bg_stdev         F32       17.7827        
   bg_mean_stdev    F32       2.399          
   path_base        STR       neb://ipp031.0/gpc1/ThreePi.nt/2010/02/13/o5240g0511o.134997/o5240g0511o.134997.ch.56729 
   magicked         S64       16249          
   data_state       STR       full            
   fault            S16       0              
   quality          S16       0              
   state            STR       update          
   workdir          STR       neb://@HOST@.0/gpc1/ThreePi.nt/2010/02/13 
   label            STR       ps_ud_TEST      
   data_group       STR       ThreePi.20100213 
   exp_id           S64       134997         
   exp_tag          STR       o5240g0511o.134997 
   exp_name         STR       o5240g0511o     
   filter           STR       y.00000         
   camera           STR       GPC1            
   telescope        STR       PS1             
   filelevel        STR       CHIP            
   dateobs          TAI       2010-02-13T15:37:25.000000
   ra               F64       3.946888       
   decl             F64       -0.505937      
   exp_time         F32       30             
   raw_magicked     S64       0              
   burntool_state   S16       -14            
   dsRun_state      STR       new             
   magic_ds_id      S64       39403          
END

Given the exp_name or exp_id one can use regtool -processedexp to get all of the information about the raw exposure that is stored in the database.

Note that imageID values only refer to the current CATDIR while
externID == chip_imfile_id is a unique value for the chipRun.

Note also that chip_imfile_id may be used in postage stamp requests to
select the image of interest

IMG_TYPE chip
REQ_TYPE byid
ID the chip_imfile_id value
OPTION_MASK |= PSTAMP_USE_IMFILE_ID

Arguably we should make image->externID and image->name selectable by mextract.
I will leave this ticket open for that request for enhancement.

[bills]

I've added externID to the list of fields supported by mextract.
Since mextract doesn't support extracting strings returning the name isn't
easily implemented.