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
Triple-Gauss PSF format #21
Comments
@JouvinLea commented via email:
I agree, having a normalised PSF is nicer. Thoughts? |
@jknodlseder - Could you please comment on the following questions concerning the triple-Gauss PSF format?
I think for the coming months / years we need some scheme to do backwards-incompatible changes to DL3 formats anyways to avoid being stuck with early mistakes, and we could use this as a test case on how to do this? |
The SCALE parameter is in fact not used by GammaLib as the GCTAPsf2D class assures internally the normalisation. So in principle the SCALE parameter can be dropped. For the moment, the order of the parameter blocks in the FITS file are hardwired in GCTAPsf2D which is anyways a bad idea. Enhancing GCTAPsf2D so that the required parameter blocks are dynamically extracted from the column names would handle the two formats transparently. So we would not need to use the version header keyword for that (and to increment the number). You may create a change request asking for an automatic detection of the parameter blocks based on column names. Note that this implies that the column names will then be fixed. We also need to change GCTAResponseIrf::load_psf which for the moment checks the presence of columns and infers from that whether to use a Gaussian or a King PSF. We just need to remove the table.contains("SCALE") condition. Le 2 févr. 2016 à 12:37, Christoph Deil a écrit :
|
@jknodlseder - Thank you for the quick reply! Change request for Gammalib is here:
I would much prefer to have declarative scheme. E.g. HDUCLASS and maybe a version as e.g. here: Having to maintain code that pokes and guesses formats in Gammalib / Gammapy for the coming years is painful and not really needed if we tell data producers via these specs what to put, right? |
I fully agree that a declarative scheme should be implemented. As we had so far no conventions, we simply put the emphasize on a system that "works", but now that the conventions start to emerge, we should of course fully support them. Le 3 févr. 2016 à 11:02, Christoph Deil a écrit :
|
I've added a formula for the triple-Gauss PSF:
http://gamma-astro-data-formats.readthedocs.org/en/latest/irfs/psf/psf_3gauss/index.html
as well as some background info on radial PSFs:
http://gamma-astro-data-formats.readthedocs.org/en/latest/irfs/psf/index.html#point-spread-function
I think some discussion / checks are needed:
1/pi
factor to go fromdP/dr^2
(which is what HAP fits) todP/d\Omega
(which is what Fermi and OGIP use as PSF value).==> there is no 3-gauss exporter in PA.
===> This is work in progress, HAP-FR can put whatever we decide here.
The text was updated successfully, but these errors were encountered: