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

Different exposure times per filter #150

Open
oconnorb opened this issue Sep 23, 2023 · 4 comments
Open

Different exposure times per filter #150

oconnorb opened this issue Sep 23, 2023 · 4 comments

Comments

@oconnorb
Copy link

We note an issue where attempting to use two filters with different exposure times (i.e., --filters g,i --exposuretimes 60.0,100.0) leads to only using the longer exposure time in both the output schedule.dat file and based on the total exposure time and number of tiles observed it appears that the software also does this, and that it is unlikely simply a bug in the output of schedule.dat.

@mcoughlin
Copy link
Collaborator

@oconnorb Does it work if the exposuretimes are factors of one another, e.g. 50 and 100?

@oconnorb
Copy link
Author

I will try this and get back to you.

@oconnorb
Copy link
Author

oconnorb commented Sep 23, 2023

Using --exposuretimes 50.0,100.0 still leads to the same issue.

e.g., 46 tiles with 44/46 observed at least twice (i.e., both filters) with the total exposure = 2.5 hr (9000 s)

(100 + 100)x44 + 2x100 = 9000 s
wheres (100 + 50)x44 + 2x100 = 6800 s

Also just to add I confirmed that the schedule.dat file contains 46+44 = 90 observations all listed with 100 s exposure

Let me know if this doesn't make sense.

@mcoughlin
Copy link
Collaborator

@oconnorb @Theodlz @robertdstein it would be great if someone could dig into it a bit to understand how the slots get allocated?

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

No branches or pull requests

2 participants