sphenix-hcal-l AT lists.bnl.gov
Subject: sPHENIX HCal discussion
List archive
Re: [Sphenix-hcal-l] [Sphenix-emcal-l] IEEE Proceedings Due Friday!
- From: Joe Osborn <jdosbo AT umich.edu>
- To: Megan Connors <meganeconnors AT gmail.com>
- Cc: sphenix-emcal-l AT lists.bnl.gov, sphenix-hcal-l AT lists.bnl.gov
- Subject: Re: [Sphenix-hcal-l] [Sphenix-emcal-l] IEEE Proceedings Due Friday!
- Date: Wed, 15 Nov 2017 20:18:43 -0500
l60 - beams -> single particle beams or something like this, beams seems vague
l86 - define FTBF
l92 - The energy resolution of the EMCal
l93 - remove “at”
l119 - sheild -> shield
l141 - done -> performed
l143 - "there will be no" -> there will not be
l146 - Using the position of the clusters as identified within the EMCal, a position dependent energy correction was applied to the 2017 test beam results.
l149 - your figure references are question marks
l159 - it looks like there is a word missing in this sentence
l164 - I would emphasize that these were the first ever 2D SPACAL blocks built, and this is part of the reason why the block boundaries were not so good as we are learning how to build them. Then you can lead into a statement about the 2018 blocks and block boundaries
l168-170 - This seems awkward as a standalone paragraph, and I think the point is that we shouldn’t make any concrete quantifiable conclusions until the 2018 test beam. Rather than bring in the simulation agreeing and/or disagreeing, I would just say something along the lines of “we will be able to make more quantitative statements about the overall resolution of the 2D projective calorimeter in 2018”
l176 - again your figure reference is question marks
l187 - extraneous “for”
l187 - figure reference
l191 - figure reference
l195 - Is there a deeper justification for this deviation from linearity? For example for the EMCal the deviation from linear at small energies is due to uncertainty in the actual beam energy, and at high energies the deviation is due to energy leakage. This isn’t mentioned in the EMCal section (and perhaps doesn’t need to be as it is mentioned in the 2016 paper), but I’m wondering if something more should be said in this sentence.
-MeganBest,Dear all,I posted a draft of the proceedings for my IEEE talk to today's HCal agenda (link below). The deadline for submission is already this Friday November 17! Sorry for the late posting and thanks for your quick feedback.
https://indico.bnl.gov/conferenceDisplay.py?confId=3873
_______________________________________________
sPHENIX-EMCal-l mailing list
sPHENIX-EMCal-l AT lists.bnl.gov
https://lists.bnl.gov/mailman/listinfo/sphenix-emcal-l
-
[Sphenix-hcal-l] IEEE Proceedings Due Friday!,
Megan Connors, 11/15/2017
- Re: [Sphenix-hcal-l] [Sphenix-emcal-l] IEEE Proceedings Due Friday!, Joe Osborn, 11/15/2017
-
Message not available
-
Re: [Sphenix-hcal-l] [Sphenix-emcal-l] IEEE Proceedings Due Friday!,
Megan Connors, 11/15/2017
-
Re: [Sphenix-hcal-l] [Sphenix-emcal-l] IEEE Proceedings Due Friday!,
Craig Woody, 11/16/2017
- Re: [Sphenix-hcal-l] [Sphenix-emcal-l] IEEE Proceedings Due Friday!, John Haggerty, 11/16/2017
-
Re: [Sphenix-hcal-l] [Sphenix-emcal-l] IEEE Proceedings Due Friday!,
Craig Woody, 11/16/2017
-
Re: [Sphenix-hcal-l] [Sphenix-emcal-l] IEEE Proceedings Due Friday!,
Megan Connors, 11/15/2017
-
Re: [Sphenix-hcal-l] [Sphenix-emcal-l] IEEE Proceedings Due Friday!,
Huang, Jin, 11/16/2017
- Re: [Sphenix-hcal-l] [Sphenix-emcal-l] IEEE Proceedings Due Friday!, Megan Connors, 11/17/2017
Archive powered by MHonArc 2.6.24.