Release RemoteCalib-0-1

Foreseen release date

Tuesday 31 July 2007

Functionalities to be included

  • Start STcontrol without tags and partition name (-m option), connect to IPC (choose partition), choose tag, choose crate(s), allocate actions for RODs in connectivity, if not allocated by other user
  • Enable/disable RODs
  • Enable/disable modules (locally as before + PixActionSingleROD test, call the action every time the status changes)
  • Initialise RODs (in parallel on more than one crate)
  • Reset all modules
  • Configure all modules
  • Start preset scan (no config change)
  • Start STcontrol with tags and partition name (-mt option), load and allocate everything

Release RemoteCalib-0-2

Foreseen release date

Friday 24 August 2007

Functionalities to be included

  • Possibility to start without IPC and first choose connectivity tag, then maybe connect to IPC (if not, issue warnings)
  • Inspect, modify and save configurations (as before, configs loaded locally when choosing connectivity tag)
  • Start scan reading configuration from hardcoded filename
  • Buffer enable/disable modules and send new mask only at the start of a scan or before initialising the ROD, etc.
  • Start scan in a separated thread

Release RemoteCalib-0-3

Foreseen release date

? 2007

Functionalities to be included

  • Publish ROD status in IS.
  • Possibility to deallocate disabled RODs

Functionalities as of today

Last update

Saturday 18 August 2007


  • Release RemoteCalib-0-1
  • Start the scan process on different threads

Almost done / To be tested

  • Start preset scan on two different crates. Waiting for a set up.
  • Start a custom scan, reading configuration from a root file. Some investigations inside STRodCrateRemote code needed.
  • Test the scan execution in different threads on two RODs and on two Crates.


  • Abort function implemented in PixLib. We have to figure out how to handle it in STcontrol. At the moment there is NO safety in STcontrol panel after starting the scan and the red abort button doesn't appear.

Problems as of today

Last update

Saturday 18 August 2007

Being debugged

  • PixBroker::updateConnectivityDB method is not working properly: it is not doing an update, but a complete reloading.

To be debugged

  • If the 2 crates are present, but only one is in the ConnectivityDB chosen by STcontrol, updateConnectivity doesn`t load the connectivity (bug in the master STRodCrateRemote?)
  • Old Local version in pixeldaqdev account seems not working properly: when you chose a preset, it does another scan!
  • RODs appear OK when you start STcontrol. The correct check on the ROD status must be added, in order to initialize always the RODs before scanning. Can only be fixed when the ROD publishes its status to IS.

Open questions

Module Mask for scan

  • why the scan configuration set as default only group0 enable? (changed NOW in the cvs head code)
  • have a look in PixModuleGroup::setModuleActive()

Temporary saving of ROD/module configurations

  • In a later version, when configurations are not loaded in memory anymore, there should be a temporary storage of modified configurations, to be kept until a scan is performed. Then they are saved to the DB and deleted from memory.
  • Do we need additional flags to remember what was changed?
  • How do the RODs update the configurations? Always read from DB before starting a scan? Get a list of objects with new config? When do the RODs load configurations?

Scan configurations

  • Saved to DB similar to module config DB
  • Interface through PixConfiguration class, similar to PixConnectivity, containing at least the following methods:
    1. listTags()
    2. setTag(string tag)
    3. listObjects()
    4. readConfig(string objname)
    5. saveConfig(string tag=m_tag)
    6. getConfigFileName(string objname)

Environment variables

  • Need to synchronise between different machines
  • Shall STcontrol be able to ask the SBCs which DB they are using?

EXAMPLE: Sending the tag is not enough if the user is reading the connectivity from a local copy of the DB and the SBCs use the oracle server. Same problem for scan and analysis configs, etc.

-- LuciaMasetti - 07 Jun 2007

Edit | Attach | Watch | Print version | History: r16 < r15 < r14 < r13 < r12 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r16 - 2007-08-20 - LuciaMasetti
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback