...
This section contains tasks already foreseen to go into future updates. The idea is that these tasks are mainly provided form the user community.
- GENERAL Help for user when problems
- If a module name is entered together with a scan number and the scan do not contain the module display this message
- If no scans/analyses display a message saying this
- Implement a cut off in time for very long queries?
- Move the module name input to the normal search to make sure the user understands that it can be used to select a set of scans/analyses
- Put the dump module information button together with the other buttons in the bottom
- Implement search for analyses as well
- Change the input field to be of either scan or analysis
- Add radio button to select search for scan or analysis
- Add drop down menu to look for analysis names, this should be made interactively so that selecting the radiobutton for analysis switches the type list. Interim solution is to have two type searches.
- Show BOTH scan AND analysis date, add column
- Make sure that they are sorted according to analysis (scan) if the search is for analysis (scan)
- If the search is for analysis, table should list analysis number to the left and scan in later columns.
- Clicking on analysis/scan link in list should submit results DONE
- When selecting scans/analyses manually from the text box, mark all analysis that exist directly so that the user need only to deselect the analyses to be excluded
- With no query or selection the until date should be todays date (fix with javascript?)
- Change the date format, skip the time, use only date DONE
- Implement a selection of scans/analysis by giving a scan or analysis ID DONE
- Implement a variable fall-out menu for each calibration scan, understand why the javascript behaves so strangely for different browsers (Make sure that the makeplot can handle trend/overlay i n this case)
- Finalize the detector browsable menu
- Add option to select modules/PP0(other object?) to compare in different scans (This should be merged with the detector browser navigation menu)
- Split all plots to show pixel types (were applicable from DB variables)
- Separate main calibration view with an expert output in the lower part
...
- Do I really need to copy around the result, why not keep the all_res as the member variable?NO GAIN IN SPEED
- Make a shell script that can supply the same input to the exe in order to quicker test the output without apache PARTLY DONE
- Make sure all the scan names are transmitted when listing scans in dbutils (to remove the complicated current_scan_name business in the list) DONE
- Fix the unnecessary multiple query when asking for result from already specified variables, need to modify the sql query to remove multiple calls to the getAnalysisResultsFromDB DONE
- Remove the ul in the result section to save space DONE
- Clean-up and tag the plot files
- Look into the difference between the Firefox and Safari (+ other browsers)
- The plots are displayed in 3 columns but this is incinsistent if for one detector level there are no overlapping modules
- Fix bug so that when the 2nd or later analysis of the same scan is selected the correct name is output DONE
- Fix bug so that the scan type is correct even when not selected it in the drop-down menu or when it is summy (see above bug)DONE
- Only fetch the scan type selected from the DB
- Optimize the DB access to speed up the displays
- Implemented new getAnalysis function in PixResultsCoral package which does 'OR' of connNames and and 'OR' of variables DONE
- Try to make an OR of all the foreign keys obtained from the analysis ID table and check speed DONE
- Make sure that the FindMods function loops over only one variable!
- Optimize the browsable menu, at the moment it is slow due to multiple calls to DB