-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Number of detectors per tube #15
Comments
It is in the instrument design file here: https://docs.google.com/spreadsheets/d/1X0x8wYhjHdI_WPjhgbtyVlVQrX86tTgxgqEUhan2Hxg/edit?usp=sharing You'll want to go to the 19 tube LAT tabs and the SAT tab. There is a field for detectors per optics tube in each. |
can I link that spreadsheet in the README of this repository? so I can find it more easily in the future |
Yes, absolutely |
ok thanks |
@keskitalo how did you get the number of detectors into the TOAST simulations? have you extracted them from the spreadsheet and pasted into the TOAST config files? |
The detector counts are encoded in the default hardware map in |
how do I extract those? I tried grepping and looking around but cannot find them |
@zonca It is not trivial to get them from the instrument configuration files. https://github.com/CMB-S4/s4sim/blob/master/s4sim/hardware/config.py has the number of pixels per wafer (x2 to get the number of pixels at a given frequency). But the wafer numbers include partial wafers so you can't just multiply the detector/wafer by the number of wafers (and you'd need to know what type of partial wafer). I calculated all the detector numbers based on the layouts and the pBD spreadsheet was updated to reflect those values, so they're consistent and you should feel free to use the pBD spreadsheet if that is simpler. |
You can always simulate the focalplane:
Will print
|
ok, let me just copy paste from the pDB. I added this to the rest of information I pull out from s4sim. then I dump everything into a CSV so I have a place to quickly cross-check everything, it would be nice to instead just have such a simple format to start from. |
Agreed ... if such a spreadsheet is going to be the official record of the
instrument design then we need a tool to populate an IMo from that
spreadsheet.
J
…On Thu, Jul 2, 2020 at 8:56 PM Andrea Zonca ***@***.***> wrote:
ok, let me just copy paste from the pDB.
I added this to the rest of information I pull out from s4sim.
then I dump everything into a CSV so I have a place to quickly cross-check
everything, it would be nice to instead just have such a simple format to
start from.
https://github.com/CMB-S4/s4mapbasedsims/blob/master/202006_foregrounds_extragalactic_cmb_tophat/cmbs4_tophat.csv
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#15 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAC4LSSMNVJOSHOMO3P3USTRZVJD5ANCNFSM4ONCWY5A>
.
|
I think we could start from the pDB, reformat it to make more machine readable. |
I think it's going to be hard to reformat the spreadsheet layout per se.
However, we could certainly request a new IMo tab that is automatically
populated from the existing tabs and layed out in a way that makes
automatic ingestion to our preferred intermediate format straightforward.
Julian
…On Fri, Jul 3, 2020 at 9:37 AM Andrea Zonca ***@***.***> wrote:
I think we could start from the pDB, reformat it to make more machine
readable.
Then write a tool that just dumps a CSV from that programmatically
<https://stackoverflow.com/questions/12842341/download-google-docs-public-spreadsheet-to-csv-with-python>
and then commit that to a repository, so it's versioned robustly.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#15 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAC4LSQVMOOFRGR5ZWS54QDRZYCMJANCNFSM4ONCWY5A>
.
|
@smsimon also for the new release I need the number of detectors per tube, is there an easier way to get this information now? |
We can add this as an item to implement in the next iteration. The LAT tubes all only have one wafer, so the number of detectors per frequency band is the number of pixels/wafer*2. The pixel/wafer numbers are in lines 600-610 in config.py, so you just need to multiply those by 2. For the SATs, you can use https://docs.google.com/spreadsheets/d/1X0x8wYhjHdI_WPjhgbtyVlVQrX86tTgxgqEUhan2Hxg/edit?usp=sharing. Line 46 has the number of detectors per optics tube per band. |
ok, I exported the instrument model to a text file, can you plase doublecheck I got the right number of detectors per tube? https://github.com/CMB-S4/s4mapbasedsims/blob/6dadbf44e7afa34b1397bc048f4e512e396cf267/202102_design_tool_run/instrument_model/cmbs4_instrument_model.tbl |
Those are the correct number of detectors per tube though the Pole LAT fwhm will need to be updated with the new values (now committed in 85-tube_LAT branch) |
ok, I am going to leave this issue open to remind that for next release it would be nice to have the number of detectors per tube written into the instrument model. |
Sorry, I can't find the number of detectors per tube either, can you please point me to those?
The text was updated successfully, but these errors were encountered: