-
Notifications
You must be signed in to change notification settings - Fork 4
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
Differences between input and simulated grating spectrum #34
Comments
hamogu
added a commit
to hamogu/ciao-contrib
that referenced
this issue
Nov 26, 2018
`fullgarf` runs a loop over all ACIS chips (or HRC plates for the HRC). When it does, it dynamically constructs the `detsubsys` keyword for `mkgarf`. Previously, there was no way to add ardlib qualifiers to this `detsubsys` keyword, it would always use the bare e.g. "ACIS-5". Unfortunately, that means that fullgarf is incompatible with MARX simulations, see Chandra-MARX/marx#34 . This change adds a way to add ardlib qualifiers.
This was referenced Nov 26, 2018
nplee
pushed a commit
to nplee/ciao-contrib
that referenced
this issue
Mar 26, 2019
`fullgarf` runs a loop over all ACIS chips (or HRC plates for the HRC). When it does, it dynamically constructs the `detsubsys` keyword for `mkgarf`. Previously, there was no way to add ardlib qualifiers to this `detsubsys` keyword, it would always use the bare e.g. "ACIS-5". Unfortunately, that means that fullgarf is incompatible with MARX simulations, see Chandra-MARX/marx#34 . This change adds a way to add ardlib qualifiers.
nplee
pushed a commit
to nplee/ciao-contrib
that referenced
this issue
Mar 26, 2019
`fullgarf` runs a loop over all ACIS chips (or HRC plates for the HRC). When it does, it dynamically constructs the `detsubsys` keyword for `mkgarf`. Previously, there was no way to add ardlib qualifiers to this `detsubsys` keyword, it would always use the bare e.g. "ACIS-5". Unfortunately, that means that fullgarf is incompatible with MARX simulations, see Chandra-MARX/marx#34 . This change adds a way to add ardlib qualifiers.
nplee
pushed a commit
to nplee/ciao-contrib
that referenced
this issue
Mar 27, 2019
`fullgarf` runs a loop over all ACIS chips (or HRC plates for the HRC). When it does, it dynamically constructs the `detsubsys` keyword for `mkgarf`. Previously, there was no way to add ardlib qualifiers to this `detsubsys` keyword, it would always use the bare e.g. "ACIS-5". Unfortunately, that means that fullgarf is incompatible with MARX simulations, see Chandra-MARX/marx#34 . This change adds a way to add ardlib qualifiers.
nplee
pushed a commit
to nplee/ciao-contrib
that referenced
this issue
Mar 27, 2019
`fullgarf` runs a loop over all ACIS chips (or HRC plates for the HRC). When it does, it dynamically constructs the `detsubsys` keyword for `mkgarf`. Previously, there was no way to add ardlib qualifiers to this `detsubsys` keyword, it would always use the bare e.g. "ACIS-5". Unfortunately, that means that fullgarf is incompatible with MARX simulations, see Chandra-MARX/marx#34 . This change adds a way to add ardlib qualifiers.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This bug report came to me third hand:
Secondly, I have tripped over something in MARX that doesn't seem right. I've been employing MARX in an attempt to understand the role of the cluster on the extracted AGN spectrum. But, even when I just simulate an isolated point source with a pure power-law spectrum, the spectrum I then recover has wiggles at the ±10% level (see marx.ps attached). So MARX doesn't seem to be internally consistent with CALDB. Is this unavoidable given that (I believe) MARX uses a physical model that must presumably differ in detail from CALDB? Or is there someway of creating and then extracting a completely self-consistent simulated HETG spectrum from MARX?
Debugging indicates that this is due to MARX not using QEU maps. In particular the BI chips have up to 20% drops near the chip edge. MARX does not use QEU maps, and all observations should be reduced with the ardlib qualifier
UNIFORM
. It turns out that fullgarf does not offer the option to do that, introducing these spurious wiggles.Two options to solve this:
Option 1 is much faster and should solve this problem, but option 2 needs to be investigated long-term.
The text was updated successfully, but these errors were encountered: