Project

General

Profile

Bug #6607

Multiplicity spectra

Added by Markus Diefenthaler over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Start date:
07/10/2014
Due date:
% Done:

0%

Estimated time:
Duration:

Description

Don reported a problem with the multiplicity spectra:

"There seems to be a problem with the muliplicity spectra filtered with intime hits. It takes forever to return and seems to give 0 most of the time."

problem.png (163 KB) problem.png Mariusz Witek, 07/12/2014 01:50 PM

History

#1 Updated by Markus Diefenthaler over 5 years ago

Mariusz had a first look into this:

Here is an example of a query for Hodoscope 1, display mode: multiplicty filter: intime.

SELECT IF="P",CONCAT,"_",RIGHT),detectorName)
AS `grpName`, `multiplicity`, COUNT()
FROM (SELECT detectorName, COUNT(
) as `multiplicity` FROM run_009218_R001.Hit WHERE spillID BETWEEN 319981 AND 319985 AND inTime = 1 GROUP BY detectorName, eventID) slice WHERE detectorName
IN ("H1T", "H1B", "H1L", "H1R") GROUP BY grpName, `multiplicity`
ORDER BY grpName ASC, `multiplicity` ASC

The query is always written to the console after: "INFO in db [C:\Users\Mariusz Witek\seascapeNEW\seascape\seascape\db.py:181]:
Executing query:" which is where I got this from.

I tried loading other detectors with the same display mode and filter and I got what seemed to be good looking data (it wasn't only 0). Attached is a picture of what I got for Drift Chamber D3m with the following query:

SELECT IF="P",CONCAT,"_",RIGHT),detectorName)
AS `grpName`, `multiplicity`, COUNT()
FROM (SELECT detectorName, COUNT(
) as `multiplicity` FROM run_009218_R001.Hit WHERE spillID BETWEEN 319988 AND 319992 AND inTime = 1 GROUP BY detectorName, eventID) slice WHERE detectorName
IN ("D3mU", "D3mX", "D3mV", "D3mUp", "D3mXp", "D3mVp") GROUP BY grpName, `multiplicity` ORDER BY grpName ASC, `multiplicity` ASC

Is the problem the long section of 0's that I highlighted? I checked to see if the query consisted of on values 0 and it didn't, that's just flot putting in 0 if it has no value for it.

#2 Updated by Mariusz Witek over 5 years ago

Picture which shows the highlighted problem area.
-Mariusz

#3 Updated by Bryan Dannowitz over 5 years ago

  • Status changed from New to Closed

This does not appear to be a problem. Especially with the in-time restriction, there will be fewer and fewer events with higher multiplicity until there are zero, and that number will stay zero at even higher multiplicities.

Unless there are plots that are showing all zero, giving reason to investigate, I will mark this bug as 'closed'.



Also available in: Atom PDF