Hi Pelle,
On Wed, Jan 28, 2015 at 5:17 PM, Hansson Adrian, Per Ola <[log in to unmask]> wrote:
Hi,
I think the main problem here is that you are using the wrong detector in SLIC. You are specifying that you want to simulate the Test Run detector “HPSTestRunTracker2014-v0/HPSTestRunTracker2014-v0.lcdd” while you should be using the “2014” detector “HPSTracker2014-v0/HPSTracker2014-v0.lcdd”. Running with the Test Run detector is kind of a mess and needs tricks so I would expect it to fail. I have been able to run it but using older tagged version of hps-java.
At least what I was thinking was that we would use the new detector to look at the A’ events to validate both the detector geometry and the rotation/translations. If we have time we can go back and study the Test Run detector with data (we probably won’t have time).
Omar, Sho or Jeremy: what does the default (run number 0 or not specifying run at all) give us in terms of conditions (noise, pedestals, dead/channels, and what not)?
Run 0 for the SVT has the following ideal conditions:
-- pedestal for samples 0-5: 4300-- noise for samples 0-5: 84.69-- gain=0.09-- offset = 100-- No bad channels
A signal pulse will have an amplitude of 2500 ADC counts, a tp of 20 ns and a shaping time of 35 ns.
I ported these conditions from the text files we were using before. That said, if you are going to generate MC data to study the alignment of the SVT, we might want to change the noise and pulse shape parameters to values that are closer to what we expect. Especially since they will affect your single hit resolution. What do you think?
I think for this study we would like a kind of an “ideal” detector when studying basic alignment if possible. Noise, dead channels and other stuff is not a problem really, but just adds irrelevant stuff for this study.
So Alessandra, try running slic with the "HPSTracker2014-v0.lcdd” detector instead and then see what happens. I don’t think we specify a run number in slic as there are no “real" conditions loaded (but I might be wrong here). And depending on the answer to the above I think we just want the default conditions loaded.
Using my steering file with the simple digitization I believe noise is there (but not treated as rigorously) but no dead channels (option to drop them is false)? Sho, can you clarify this once and for all for me (the “Noiseless readout chip” looks like it has noise)?
Why not use SimpleSvtReadout with no pileup?
Btw., the names for the detectors may not be great (and a little confusing)…that is my fault.
/pelle
On Jan 28, 2015, at 3:36 AM, Alessandra Filippi <[log in to unmask]> wrote:
> Hi all,
> and than you for your help and patience. I'm (almost) in business again!
> So, the problem is in my .slcio file, with Pelle's one everything works.
> I tried to run readout on my file including in Pelle's lcsim this stanza:
>
> <driver name="ConditionsDriver" type= "org.hps.conditions.ConditionsDriver">
> <runNumber>2014</runNumber>
> <detectorName>HPSTestRunTracker2014-v0</detectorName>
> <freeze>true</freeze>
> </driver>
>
> is it ok? I'm not sure why I should give a Test Run number if I'm running a 2014 detector, so I chose 2014 (> 1365). Like this, it works.
> It works even if I give a smaller number (say 1350), but the output is slightly different. Which would you reccommend? Is there a "standard" run number for 2014 mc runs?
> Anyhow, the issue was really the missing run number.
>
> Just to make sure I run everything correctly, here's the slic command I use to produce the slcio file (on rhel6-64 machines at slac, so I think the slic version is a bit dated, but it should not matter so much, right?):
>
> slic -P ${PARTICLE_TBL} -i /nfs/slac/g/hps2/hps_data/stdhep/e2.2gev/aprime/ap2.2gev075mev.stdhep -p /nfs/slac/g/hps3/users/afilippi/hps/SCRATCH/OUT2014_v0 -o ap2.2gev075mev_all
> -g /nfs/slac/g/hps3/users/afilippi/hps/hps-trunk/detector-data/detectors/HPSTestRunTracker2014-v0/HPSTestRunTracker2014-v0.lcdd -x -d0 -r 5000000
>
> is ot ok?
> Last: can you please tell me how to include the run number with slic? I wasn't able to find any slic command line option to set it. As I have to rerun slic every time I change geometry (many tens of times), I guess it would make sense to set it properly at this point, at the beginning I mean.
> Thank you all,
> Alessandra
>
>
>
>
> On Wed, 28 Jan 2015, McCormick, Jeremy I. wrote:
>
>> Hi,
>> So I think I know the problem...
>> This isn’t working because the data file references a Test Run detector, but the conditions are
>> getting loaded as run 0, which is ambiguous. If you don’t specify anything else, then run 0 is
>> interpreted as the default detector setup, which is not the Test Run.
>> So then the conditions system gets into some detector setup code and there is an
>> UnsupportedOperationException having to do with setting a FEB ID from the DAQ mapping, which for
>> some reason I’m still trying to understand, has its traceback suppressed and never prints out.
>> But the job definitely fails because of this.
>> You will need to use the ConditionsDriver in your steering file to force the job to setup Test Run
>> conditions using a valid run number, and then you should freeze it so that it doesn’t get reset
>> back to run 0. (This is covered in previous emails to the software list, and the documentation
>> for ConditionsDriver in the conditions module has all the details listed in the class’s javadoc as
>> well.)
>> Or you could regenerate the events with SLIC with a run number between 1 and 1365 which is assumed
>> to be the Test Run. The slic command line interface accepts a run number. Then the conditions
>> system in LCSim will see that run number and load everything correctly.
>> The first option is probably the easiest as it doesn’t require regenerating the MC data.
>> —Jeremy
>> On Jan 27, 2015, at 5:33 PM, Hansson Adrian, Per Ola <[log in to unmask]> wrote:
>>
>> Standard cmd:
>> java -jar hps-distribution-3.1-SNAPSHOT-bin.jar HPSTrackingDefaults.lcsim -i
>> ap2.2gev075mev_SLIC-v04-00-00_Geant4-v10-00-02_QGSP_BERT_HPSTracker2014-v0.slcio
>> -DoutputFile=apout.slcio
>> I’m not sure what file Alessadra used. I think her slcio was generated by herself but the
>> underlying std hep file was the same.
>> Alessandra, can you verify that you see events with my lcio file? Maybe you generated the
>> slcio file with an old version of the detector lcdd?
>> /Pelle
>> On Jan 27, 2015, at 5:08 PM, Graham, Mathew Thomas <[log in to unmask]> wrote:
>>
>> Ah, I didn’t realize the file Pelle linked to wasn’t the same as what Alessandra
>> sent initially; when I run on Pelle’s file it works ok.
>> What’s the difference in the generation between Alessandra’s and Pelle’s generation?
>> On Jan 27, 2015, at 4:42 PM, Graham, Mathew Thomas <[log in to unmask]> wrote:
>>
>> I think I’m seeing the same as I saw before…quitting after 0 events. What
>> is the command you’re using to run this?
>> On Jan 27, 2015, at 4:24 PM, Hansson Adrian, Per Ola
>> <[log in to unmask]> wrote:
>> I just did a clean checkout of lcsim and hps-java trunk on a different
>> machine and ran the linked steering file over the linked slic output file.
>> It looks fine. Can someone verify this as well?
>> http://www.slac.stanford.edu/~phansson/files/temp/HPSTrackingDefaults.lcsim
>> ap2.2gev075mev_SLIC-v04-00-00_Geant4-v10-00-02_QGSP_BERT_HPSTracker2014-v0.slcio
>> /Pelle
>> On Jan 27, 2015, at 3:11 PM, McCormick, Jeremy I.
>> <[log in to unmask]> wrote:
>>
>> Do you have any local changes that aren’t checked in to SVN
>> Pelle?
>> My guess is that when this problem is occurring on Alessandra’s
>> machine that there is an error occurring but for some reason the
>> traceback/message is being suppressed.
>> On Jan 27, 2015, at 2:49 PM, Hansson Adrian, Per Ola
>> <[log in to unmask]> wrote:
>> It works fine for me. It feels like it should be the other
>> way, but I guess I should figure out why it works :)
>> <Screen Shot 2015-01-27 at 2.49.17 PM.png>
>> On Jan 26, 2015, at 10:30 AM, Sho Uemura
>> <[log in to unmask]> wrote:
>>
>> Never mind, I don't think that's right. There's
>> nothing wrong with that config. I'll look at this
>> during lunch.
>>
>> On Mon, 26 Jan 2015, Sho Uemura wrote:
>>
>> You;re right.
>>
>> The clusterer settings are not
>> correct:
>>
>> <inputHitCollectionName>EcalReadoutAnalogHits</inputHitCollectionName>
>>
>> should be
>>
>> <inputHitCollectionName>EcalReadoutHits</inputHitCollectionName>
>>
>> I can't make or test the change on my
>> computer here, but maybe someone else
>> can.
>>
>> On Mon, 26 Jan 2015, Hansson Adrian,
>> Per Ola wrote:
>>
>> Can this be related to
>> changes on the ECal side?
>> Maybe collection names has
>> been changing? What
>> happens if a collection is
>> not found, maybe it skips
>> the event?
>> On Jan 26, 2015, at 10:08
>> AM, Graham, Mathew Thomas
>> <[log in to unmask]>
>> wrote:
>> I?m using this
>> to run:
>> ===============================================
>> $steering="resources/org/hps/steering/readout/HPS2014ReadoutNoPileup.lcsim";
>> $in="Data/ap2.2gev075mev_all_alessandra.slcio";
>> $out="Data/foobar.slcio";
>> $jarfile="hps_trunk/distribution/target/hps-distribution-3.1-SNAPSHOT-bin.jar";
>> `java -jar
>> $jarfile -f
>> $steering -n
>> 1000 -i $in
>> -DoutputFile=$out
>> >& foobar`;
>> ============================
>> On Jan 26,
>> 2015, at 10:05
>> AM, Alessandra
>> Filippi
>> <[log in to unmask]>
>> wrote:
>> good...
>> at
>> least
>> I
>> am
>> not
>> alone
>> ;-)
>> thanks
>> for
>> any
>> hints
>> you
>> might
>> have.
>> It
>> seems
>> it
>> goes
>> for
>> a
>> dry
>> run
>> by
>> default
>> -
>> maybe
>> there
>> are
>> some
>> more
>> new
>> parameters
>> to
>> pass?
>> number
>> of
>> events
>> to
>> be
>> processed?
>> something
>> trivial
>> like
>> this?
>> On
>> Mon,
>> 26
>> Jan
>> 2015,
>> Graham,
>> Mathew
>> Thomas
>> wrote:
>> Yeah,
>> I
>> can
>> finally
>> verify
>> I
>> get
>> the
>> same
>> thing.
>> I
>> can
>> browse
>> through
>> events
>> (w/o
>> running
>> a
>> driver)
>> no
>> problem,
>> but
>> when
>> I
>> run
>> (via
>> command
>> line)
>> /org/hps/steering/readout/HPS2014ReadoutNoPileup.lcsim
>> it
>> says
>> it
>> sees
>> and
>> endOfData
>> without
>> going
>> through
>> events.
>> [IMAGE]
>> On
>> Jan
>> 26,
>> 2015,
>> at
>> 9:38
>> AM,
>> Hansson
>> Adrian,
>> Per
>> Ola
>> <[log in to unmask]>
>> wrote:
>>
>> Hi,
>>
>> sorry
>> for
>> not
>> being
>> able
>> to
>> help
>> much
>> here
>> (trying
>> to
>> get
>> the
>> SVT
>> in
>> shape
>> for
>> shipping).
>> I
>> will
>> try
>> to
>> run
>> again
>> as
>> well
>> sometime
>> today;
>> it
>> was
>> working
>> last
>> week
>> so
>> it?ll
>> be
>> interesting
>> to
>> see.
>>
>> /Pelle
>>
>> On
>> Jan
>> 23,
>> 2015,
>> at
>> 9:44
>> AM,
>> Alessandra
>> Filippi
>> <[log in to unmask]>
>> wrote:
>>
>> Hi
>> Pelle,
>> no,
>> not
>> yet,
>> I
>> am
>> stuck...
>> I
>> have
>> the
>> same
>> problem
>> (and
>> same
>> behaviour)
>> if
>> I
>> try
>> to
>> run
>> the
>> reconstruction
>> at
>> slac,
>> so
>> I
>> doubt
>> it
>> could
>> be
>> an
>> issue
>> related
>> to
>> the
>> connection
>> to
>> the
>> database.
>> Cheers
>> Alessandra
>>
>> On
>> Fri,
>> 23
>> Jan
>> 2015,
>> Hansson
>> Adrian,
>> Per
>> Ola
>> wrote:
>>
>> Alessandra,
>> did
>> you
>> solve
>> your
>> problem?
>> I
>> think
>> Jeremy
>> added
>> a
>> fix
>> for
>> this?
>>
>> On
>> Jan
>> 21,
>> 2015,
>> at
>> 9:01
>> PM,
>> Graham,
>> Mathew
>> Thomas
>> <[log in to unmask]>
>> wrote:
>>
>> Actually,
>> I
>> can?t
>> seem
>> to
>> connect
>> to
>> the
>> DB
>> at
>> all
>> from
>> where
>> I
>> am
>> (Fermilab).
>> I
>> think
>> FNAL
>> has
>> SLAC
>> cut
>> off,
>> somehow;
>> they?ve
>> always
>> been
>> jealous
>> of
>> us..I
>> can?t
>> get
>> to
>> the
>> svn
>> repository
>> either.
>> Here?s
>> the
>> log
>> file
>> for
>> those
>> interested:
>> <foobar>
>>
>> On
>> Jan
>> 21,
>> 2015,
>> at
>> 10:38
>> PM,
>> Graham,
>> Mathew
>> Thomas
>> <[log in to unmask]>
>> wrote:
>>
>> So
>> there
>> are
>> definitely
>> TrackerHits
>> in
>> your
>> slcio
>> file?it
>> looks
>> fine
>> to
>> me.
>> I?ll
>> try
>> running
>> some
>> readout.
>>
>> On
>> Jan
>> 21,
>> 2015,
>> at
>> 10:23
>> AM,
>> Alessandra
>> Filippi
>> <[log in to unmask]>
>> wrote:
>>
>> hi,
>> you
>> can
>> find
>> the
>> ap2*
>> slcio
>> it
>> here:
>> /nfs/slac/g/hps3/users/afilippi/hps/SCRATCH/OUT2014_v0/ap2.2gev0
>> 75mev_all.slcio
>>
>> can
>> you
>> try
>> to
>> see
>> if
>> you
>> can
>> read
>> it
>> properly?
>> (and
>> there's
>> something
>> in?)
>> thanks!
>>
>> On
>> Wed,
>> 21
>> Jan
>> 2015,
>> Hansson
>> Adrian,
>> Per
>> Ola
>> wrote:
>>
>> Hi,
>>
>> can
>> you
>> point
>> us
>> to
>> the
>> slcio
>> file?
>>
>> On
>> Jan
>> 21,
>> 2015,
>> at
>> 7:30
>> AM,
>> Alessandra
>> Filippi
>> <[log in to unmask]>
>> wrote:
>>
>> Hi
>> all,
>> sorry
>> for
>> the
>> stupid
>> question,
>> but
>> I
>> am
>> not
>> able
>> to
>> get
>> any
>> result
>> in
>> running
>> readout
>> simulations,
>> whichever
>> steering
>> lcsim
>> file
>> I
>> use,
>> and
>> I
>> need
>> some
>> help
>> to
>> get
>> going.
>> I
>> produced
>> a
>> .slcio
>> file
>> with
>> slic
>> on
>> two
>> kinds
>> of
>> stdhep
>> files
>> (ap2.2gev075mev*
>> and
>> Takashi's
>> new
>> brems-mad1.92gev*),
>> using
>> the
>> slic
>> installation
>> at
>> slac
>> (old,
>> but
>> working
>> -
>> I
>> think).
>> I
>> am
>> using
>> the
>> HPSTestRunTracker2014-v0.lcdd>> dry
>> geometry
>> file.
>> Then,
>> I
>> try
>> to
>> produce
>> a
>> readout
>> file,
>> using
>> the
>> instructions
>> in
>> the
>> confluence
>> "Running
>> Readout
>> Simulation"
>> page
>> (lcsim
>> and
>> hps_trunk
>> freshly
>> updated).
>> All
>> I
>> get,
>> with
>> both
>> the
>> .slcio
>> files
>> and
>> whichever
>> HPS2014Readout*.lcsim
>> file,
>> is
>> the
>> geometry
>> survey
>> of
>> SVT
>> (I
>> guess),
>> and
>> nothing
>> else:
>> the
>> reconstruction
>> ends
>> with
>> Ecal/svt
>> setup
>> info
>>
>> Wed
>> Jan
>> 21
>> 16:19:15
>> CET
>> 2015
>> ::
>> EcalDetectorSetup
>> ::
>> INFO
>> ::
>> loading
>> ECAL
>> conditions
>> onto
>> subdetector
>> Ecal
>> Wed
>> Jan
>> 21
>> 16:19:15
>> CET
>> 2015
>> ::
>> EcalDetectorSetup
>> ::
>> INFO
>> ::
>> building
>> ECAL
>> geometry
>> channel
>> map
>> Wed
>> Jan
>> 21
>> 16:19:15
>> CET
>> 2015
>> ::
>> EcalDetectorSetup
>> ::
>> INFO
>> ::
>> built
>> ECAL
>> geometry
>> channel
>> with
>> 442
>> entries
>> Wed
>> Jan
>> 21
>> 16:19:15
>> CET
>> 2015
>> ::
>> EcalDetectorSetup
>> ::
>> INFO
>> ::
>> done
>> loading
>> ECAL
>> conditions
>> onto
>> subdetector
>> Wed
>> Jan
>> 21
>> 16:19:26
>> CET
>> 2015
>> ::
>> SvtDetectorSetup
>> ::
>> INFO
>> ::
>> loading
>> SVT
>> conditions
>> onto
>> subdetector
>> Tracker
>> Wed
>> Jan
>> 21
>> 16:19:26
>> CET
>> 2015
>> ::
>> SvtDetectorSetup
>> ::
>> INFO
>> ::
>> setting
>> up
>> 20
>> SVT
>> sensors
>> Wed
>> Jan
>> 21
>> 16:19:26
>> CET
>> 2015
>> ::
>> SvtDetectorSetup
>> ::
>> INFO
>> ::
>> channel
>> map
>> has
>> 23040
>> entries
>> End
>> of
>> file
>> reached
>> Wed
>> Jan
>> 21
>> 16:19:26
>> CET
>> 2015
>> ::
>> DatabaseConditionsManager
>> ::
>> INFO
>> ::
>> connection
>> closed
>>
>> and
>> the
>> readout
>> file
>> is
>> empty.
>> If
>> I
>> use
>> HPSTrackingDefaults.lcsim,
>> again
>> on
>> whichever
>> kind
>> of
>> slcio
>> file,
>> after
>> the
>> drivers
>> being
>> loaded,
>> I
>> get
>>
>> Executed
>> run.
>> No
>> events
>> processed!
>>
>> and
>> again
>> nothing
>> else
>> is
>> done.
>> What
>> am
>> I
>> doing
>> wrong?
>> Thanks,
>> cheers
>> Alessandra>> __________________________________________________________________________________________________
>>
>> ps.
>> I
>> wanted
>> to
>> inspect
>> the
>> slcio
>> files
>> to
>> see
>> whether
>> they
>> had
>> problems,
>> but
>> I
>> cannot
>> install
>> JAS3
>> for
>> the
>> issue
>> mentioned
>> in
>> my
>> previous
>> e-mail.
>> ####################################################
>> ####################
>> Use
>> REPLY-ALL
>> to
>> reply
>> to
>> list
>>
>> To
>> unsubscribe
>> from
>> the
>> HPS-SOFTWARE
>> list,
>> click
>> the
>> following
>> link:
>> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1
>> =HPS-SOFTWARE&A=1
>> ##########################################################
>> ##############
>> Use
>> REPLY-ALL
>> to
>> reply
>> to
>> list
>>
>> To
>> unsubscribe
>> from
>> the
>> HPS-SOFTWARE
>> list,
>> click
>> the
>> following
>> link:
>> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-S
>> OFTWARE&A=1
>> ################################################################
>> ########
>> Use
>> REPLY-ALL
>> to
>> reply
>> to
>> list
>>
>> To
>> unsubscribe
>> from
>> the
>> HPS-SOFTWARE
>> list,
>> click
>> the
>> following
>> link:
>> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWAR
>> E&A=1
>> ######################################################################
>> ##
>> Use
>> REPLY-ALL
>> to
>> reply
>> to
>> list
>>
>> To
>> unsubscribe
>> from
>> the
>> HPS-SOFTWARE
>> list,
>> click
>> the
>> following
>> link:
>> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1
>>
>> ########################################################################
>> Use REPLY-ALL to reply to
>> list
>> To unsubscribe from the
>> HPS-SOFTWARE list, click
>> the following link:
>> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1
>>
>> ########################################################################
>> Use REPLY-ALL to reply to list
>>
>> To unsubscribe from the HPS-SOFTWARE
>> list, click the following link:
>> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1
>> Use REPLY-ALL to reply to list
>> To unsubscribe from the HPS-SOFTWARE list, click the following
>> link:
>> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1
>> __________________________________________________________________________________________________
>> Use REPLY-ALL to reply to list
>> To unsubscribe from the HPS-SOFTWARE list, click the following link:
>> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1
>> __________________________________________________________________________________________________
>> Use REPLY-ALL to reply to list
>> To unsubscribe from the HPS-SOFTWARE list, click the following link:
>> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1