Bug #1870
TS value of large components
Status: | New | Start date: | 10/06/2016 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assigned To: | - | % Done: | 0% | |
Category: | - | |||
Target version: | - | |||
Duration: |
Description
I recently made the test in simulating a few hundred hours of HESS data (only background) and analysing them with background and a large source in the FoV. Weirdly, the large component yields a TS value around ~100 for the unbinned analysis and ~10 for the stacked analysis. I hope to be able to provide a test case for CTA as well.
Recurrence
No recurrence.
History
#1 Updated by Knödlseder Jürgen about 8 years ago
- Target version set to 1.2.0
#2 Updated by Knödlseder Jürgen about 8 years ago
A test case would indeed be good. I guess large means spatially large? How large was the component?
Maybe some issue with the Npred computation.
Did the ctlike fit converge easily or does the log file indicate issues?
#3 Updated by Mayer Michael about 8 years ago
The component was about half the size of the FoV (maybe even extending across and the log-file didnt indicate any issues (no warnings whatsoever). I will try to reproduce this problem with a similar set of pointings for CTA IRFs. Then we might be able to track it down more easily.
#4 Updated by Knödlseder Jürgen about 8 years ago
Mayer Michael wrote:
The component was about half the size of the FoV (maybe even extending across and the log-file didnt indicate any issues (no warnings whatsoever). I will try to reproduce this problem with a similar set of pointings for CTA IRFs. Then we might be able to track it down more easily.
I was wondering how the ctlike fit went. Did the fit stall? Or had any other convergence issues? How many iterations did you need?
#5 Updated by Knödlseder Jürgen almost 8 years ago
- Target version changed from 1.2.0 to 1.3.0
#6 Updated by Knödlseder Jürgen over 7 years ago
- Target version changed from 1.3.0 to 1.4.0
#7 Updated by Knödlseder Jürgen over 7 years ago
- Target version deleted (
1.4.0)