Skip to content
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

Focus on Variables 1 #37

Open
rstrub opened this issue Feb 21, 2024 · 0 comments
Open

Focus on Variables 1 #37

rstrub opened this issue Feb 21, 2024 · 0 comments
Assignees

Comments

@rstrub
Copy link
Contributor

rstrub commented Feb 21, 2024

We met with DJG and he outlined the first rough cut of how he would like us to approach the variables, how to handle the stepper tables, what situations to expect, etc. So before we forget the action items from this meeting. We'd like to set aside a branch to make these changes:

Within sweep times, each stepper time may jump around:

  1.      In L1A store the actual µsec times.
       In L2/Quicklook usec step[0] time + the regular settle times in the stepper table
    

34 Azimuth?
2. In Level 1 put all 34 of the azimuth in each step.
3. I Level 1 don’t divide the azimuth into a separate [en][decl] matrix but accum should read [256][34] for each sweep/sec/skymap
Counter 1 and Counter 2
Indeed these are the number of counts in the skymap but they are counting differently. They should be the same most of the time.
4. Since we have an energy profile, we should have an angle profile too. (but I’m not sure if this goes in L1 or QuickLook)
Stepper Tables may have different lengths
5. Code for arbitrary. number of energies and declinations.
6. Also, it is easier for the hardware to change energies than to change angles BUT we cannot count on this hierarchy.
7. The settle times should be recorded in 1 dimension in the L1A
8. Record to the end of the file even if incomplete…perhaps the beginning too. But in general we will process the data to reach the end of the sweep
9. We need to record the stepper table monicker

@rstrub rstrub self-assigned this Feb 21, 2024
rstrub added a commit that referenced this issue Apr 17, 2024
rstrub added a commit that referenced this issue Apr 17, 2024
rstrub added a commit that referenced this issue Apr 17, 2024
rstrub added a commit that referenced this issue Jun 27, 2024
    destination_dir = data_filename.parent
necessitated a couple of small changes on my part...plus more familiarity with vscode
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant