| | 1 | == dev work needed before Jan 31 release == |
| | 2 | |
| | 3 | * ippTools / ippTasks / ippMonitor |
| | 4 | * finish the error handling in all scripts / tasks |
| | 5 | * finish adding outpath to all scripts / tasks |
| | 6 | * test multiple databases in pantasks |
| | 7 | * include output logs in ippMonitor |
| | 8 | * include output plots in ippMonitor pages |
| | 9 | * ippMonitor pages showing summaries (by date, by ???) |
| | 10 | |
| | 11 | * analysis tasks |
| | 12 | * test fringe creation / subtraction |
| | 13 | * convert OBSTYPE names to real obstype names |
| | 14 | * finish psphot and psastro I/O for cmp and cmf |
| | 15 | * include psastro +mosastro in phase3.pl |
| | 16 | * include addstar in phase3.pl |
| | 17 | |
| | 18 | == other issues outstanding == |
| | 19 | |
| | 20 | * we need a p2tool option to set labels on the basis of a query: |
| | 21 | p2tool -setlabel -filter -begin_date -end_date -etc -etc -label myVrun |
| | 22 | |
| | 23 | * I had a crash of pcontrol running the flat stack. these images (without masks) have a large number of bad pixels, with lots of error messages. it seems like a buffer overflow is a reasonable answer; in that case i would expect the log for that process to be missing. indeed, this is the case... |
| | 24 | |
| | 25 | * need a tool to list the known nights and groups of nights (useful for a user) |
| | 26 | |
| | 27 | * in ppMerge, the names 'flat' are too rigidly defined: we need to have the abstract concepts of how the processing takes place be independent of the actual detrend type : the relationship should be defined in the config tools |
| | 28 | |
| | 29 | * I think the bg stats (mean of stdev and/or stdev of mean) are still not being carried correctly. |
| | 30 | |
| | 31 | * choices for greyscale need to be adjusted |
| | 32 | |
| | 33 | |
| | 34 | == work needed for ippMonitor == |
| | 35 | |
| | 36 | * sort on various fields |
| | 37 | * select by ranges (for numbers) and string match (for strings) |
| | 38 | * buttons to navigate through all the data for a detrun |
| | 39 | * the << < > >> buttons don't carry the 'where' data |
