Tarek Hassan

Hi @cdeil , Sorry I took so long to answer. I was terribly busy with the MAGIC general meeting last week. >We should not duplicate work in ctapipe, so @TarekHC...

Wow, thank you for answering so quickly! :D I will test this right away! Although I have another simple question: I understand the times to be used are UTC times...

Thank you both! @vallis and @mattpitkin !! Good news and bad news: * I was able to make it work relatively easily. So thank you! * I seem to have...

Hi again @mattpitkin Ok, I'm actually ashamed I didn't know there is actually a np.float128... Not sure it is relevant to you guys... But I'm not able to reproduce the...

Hi all, Thank you @fabiopintore for opening the issue! Associating events with IRFs is a long standing issue that we have discussed a lot. My 2 cents on the topic!...

> It associates an EVENTS table to its IRFs via the `OBS_ID` column. I see. I feel current `OBS_ID` specifications are not clear for the case of an IRF, specially...

Argh, ok. I was mixing in my head HDUCLASn keywords with the HDU index files that you were referring to. Its been a while since I took a look to...

I agree with you Max: This is something that definitely needs the input from lower-level (provenance) experts. Certainly should not be discussed here. @fabiopintore please close the issue if you...

Hi all, This is clearly a provenance issue, and unfortunately it will be strongly related to details of the lower-level analysis, which may be very different for different instruments. It...

I also agree with @GernotMaier. Current specifications are full of jargons and we should definitely improve the wording. The best way to proceed is for @GernotMaier to create a pull-request...