• The HRUN for that rod has all the necessary runs (pedestal + physics)
• Those runs are all good runs
• They are not already scheduled for analysis (i.e. they are already in analysiscache)
• They have not been already analyzed (i.e. the anal_status in the runhistory table is null)
• There are no similar and more recent runs (i.e. same rod, same hrun, same subrun, a more recent date) which have already been analyzed

In the daqlet interface, you see the HRUNs ready for analysis; by clicking "Details" you can see which runs make them. By clicking the "Analyze" button you can send them to analysis. You can also click "All" to send all the visualised HRUNs to analysis, or check the checkbox to automatically send HRUNs while they arrive. NOTE: the database is checked for new runs every 5 minutes. So if you send any hrun to analysis, they will disappear from the interface only at the next round. Anyway, sending an HRUN multiple times will NOT trigger multiple analysis process: every HRUN is processed only once.

On this basis, the run numbers are extracted, and put in a table called analysiscache, which holds the run number, and a started and completed field. The started field will hold the date and time when the analysis will start, and the completed field will hold a boolean (1 or 0) information saying if the analysis has been completed. But these will be set by the AnalysisDistributor program.