You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 23 Next »

Introduction

This work is performed to provide and produce a "browsable"  summary of pixel calibration data. The tool was born out of the need to quickly access a set of information, common to a variety of scans, with a specified granularity.

The program is available here:
http://atlsr1.cern.ch/PixelCalibrationWebBrowser/pixcalwebbrowser.cgi

Please send us comments about bugs, features and suggestions. Anything is helpful!

Manual

Browse scans taken between two dates

  1. Go to the search section in the State Selection at the top of the start page.
  2. Specify since and until dates
  3. To list scans for a given type select it in the drop down list (note: If you favorite scan is missing please contact us!)
  4. Select the location where the scan was taken: PIT or SR1
  5. Change the Preset if needed
  6. To only list scans with an analysis tick the Require Analysis box.
  7. Finally, click the List Scans button

Select scan(s) to analyze

There are two ways of selecting the scan to analyze:

  1. By using the search function to find scans taken between two dates (see above).
  2. By manually entering a list of comma-separated scan ID's in the text box at the top of the page and clicking the List Scans button (note that only scans with analysis are found)

Now you should have list of scans with the corresponding analyses.

  1. Select the scans/analysis you are interested in using the check boxes to the left of the scan ID in the list
  2. Press Calibration Results.

NOTE: At the moment the DB access is slow and so it is not un-common for the request to take up to 20s so please be patient. We are working on speeding this up!

Task list

This section contains tasks already foreseen to go into future updates. The idea is that these tasks are mainly provided form the user community.

  • Clicking on analysis/scan link in list should submit results DONE
  • When selecting scans 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
Technical tasks
  • Do I really need to copy around the result, why not keep the all_res as the member variable?
  • 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
  • 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
  • No labels