Open frbliaker opened 1 year ago
Hi @frbliaker,
The exposure for CHIME/FRB's catalog 1, can be found here: https://www.canfar.net/storage/vault/list/AstroDataCitationDOI/CISTI.CANFAR/21.0007/data/exposure We provided a tutorial on how to use this data: https://chime-frb-open-data.github.io/exposure/
The exposure until 2021 May 1 (associated with this paper: https://arxiv.org/abs/2301.08762) will soon (in the next few days) be publicly available here: https://www.canfar.net/storage/vault/list/AstroDataCitationDOI/CISTI.CANFAR/23.0004/data/exposure
Feel free to reach out again if you run into issues accessing or interpreting the data.
Best, Ziggy
Dear Ziggy, I want to calculate the burst'energy of FRB by fluence , but I find same burst has different fluence . Such as the website http://www.chime-frb.ca/repeaters/FRB20190116B and https://www.chime-frb.ca/catalog/FRB20190116B , https://www.chime-frb.ca/catalog/FRB20190116A . Burst id 190116A'fluence is 0.8 Jyms the former and 3.7 Jyms the latter,burst id 190116B is 2.8 Jyms the former and 2.0 Jyms the latter .So which one should I choose?Or can you provide me with a complete data of all FRBs including fluence data. It will be of great help to my work . Looking forward to your reply .
Best, frbliaker ------------------ 原始邮件 ------------------ 发件人: "chime-frb-open-data/community" @.>; 发送时间: 2023年3月2日(星期四) 晚上11:09 @.>; @.**@.>; 主题: Re: [chime-frb-open-data/community] How to obtain the total observation time of FRBS (Issue #84)
Hi @frbliaker,
The exposure for CHIME/FRB's catalog 1, can be found here: https://www.canfar.net/storage/vault/list/AstroDataCitationDOI/CISTI.CANFAR/21.0007/data/exposure We provided a tutorial on how to use this data: https://chime-frb-open-data.github.io/exposure/
The exposure until 2021 May 1 (associated with this paper: https://arxiv.org/abs/2301.08762) will soon (in the next few days) be publicly available here: https://www.canfar.net/storage/vault/list/AstroDataCitationDOI/CISTI.CANFAR/23.0004/data/exposure
Feel free to reach out again if you run into issues accessing or interpreting the data.
Best, Ziggy
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>
Expected Behavior
Current Behavior
Possible Solution
Steps to Reproduce (for bugs)
1. 2. 3. 4.
Context
Your Environment