| |
| META TOPICPARENT |
name="2022Journals" |
Pablo Drake Research Journal (Summer '22)
06/06-06/10 |
| | 06/09
- Completed the VEGAS tutorial
- Started working again with fermipy. An error popped up when attempting to carry out the ROI analysis of FSRQ J1350.8+3033.
|
|
<
< | Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding Python |
>
> | Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding Python |
| | |
|
<
< | runtime state: core initialized |
>
> | runtime state: core initialized |
| | |
|
<
< | ModuleNotFoundError: No module named 'encodings' |
>
> | ModuleNotFoundError: No module named 'encodings' |
| |
06/10
- Started writing a log/manual fermipy document, noting down the different errors that appear.
|
| | File "/a/share/ged/src/miniconda3/envs/fermipy-1.0.1/lib/python3.7/site-packages/fermipy/ltcube.py", line 192, in create ltc = cls.create_from_fits(files[0])
IndexError: list index out of range |
|
>
> | |
| |
- Read EGRET (GeV) Blazars by Prof. Mukherjee. Wrote a set of reference notes.
06/13-06/17
06/13
- Worked on adjusting the legends and the colors for the skymaps and pie chart plots that I coded last week. Also adjusted the sizes in order for them to look better in the slides. Finally, researched and included a paragraph of information on general blazar populations at the present time.
- Reinstalled fermipy using the files provided by Massimo (run_analysis_std.py). The ROI analysis worked without any errors.
|
|
<
< |
- As per Prof. Mukherjee's suggestion, I started working in both a matplotlib/data plotting manual as continued updating the fermipy guide.
|
>
> |
- As per Prof. Mukherjee's suggestion, I started working in creating a matplotlib data plotting manual, using the code created for the TeVCat/4LAC graphs. Also continued working with the fermipy guide.
|
| | 06/14
- Completed ROI analysis. Redid the analysis in order for the graphs to be created (sometimes the plots aren't created automatically when the run_analysis_std.py finishes).
- Read The future of gamma-ray astronomy by Jürgen Knödlseder (https://arxiv.org/abs/1602.02728
 ). Wrote a set of notes on it.
06/15 |
|
<
< |
- Started working on creating a full dataset lightcurve.
|
>
> |
- Started working on creating a full dataset lightcurve. The following error appeared:
Traceback (most recent call last):
File "/nevis/milne/files/pd2629/fermi_analysis/run_analysis_std.npy", line 349, in <module>
run_lightcurve(fermipy_config, prefix, num_sections, section)
File "/nevis/milne/files/pd2629/fermi_analysis/run_analysis_std.npy", line 253, in run_lightcurve
gta.load_roi('{}.npy'.format(prefix))
File "/a/share/ged/src/miniconda3/envs/fermipy-1.0.1/lib/python3.7/site-packages/fermipy/gtanalysis.py", line 3600, in load_roi roi_file,
roi_data = utils.load_data(infile, workdir=self.workdir)
File "/a/share/ged/src/miniconda3/envs/fermipy-1.0.1/lib/python3.7/site-packages/fermipy/utils.py", line 79, in load_data raise
Exception('Input file does not exist.')
Exception: Input file does not exist.
- Found out that the error described by this code had to do with a naming mismatch in Ari Brill's pipeline code. In particular, the input file for the lightcurve analysis had to be refered to as _initial.npy, as this was the output of the baseline analysis.
06/16
- Regarding the full dataset lightcurve, the following error appeared:
Traceback (most recent call last):
File "/nevis/milne/files/pd2629/fer mi_analysis/run_analysis_std. py", line 350, in <module>
run_lightcurve(fermipy_config, prefix, num_sections, section)
File "/nevis/milne/files/pd2629/fer mi_analysis/run_analysis_std. py", line 261, in run_lightcurve
gta.lightcurve(fermipy_config[ 'selection']['target'], make_plots=True)
File "/a/share/ged/src/miniconda3/e nvs/fermipy-1.0.1/lib/python3. 7/site-packages/fermipy/ lightcurve.py", line 289, in lightcurve
o = self._make_lc(name, **config)
File "/a/share/ged/src/miniconda3/e nvs/fermipy-1.0.1/lib/python3. 7/site-packages/fermipy/ lightcurve.py", line 452, in _make_lc
if not next_fit['fit_success']:
KeyError: 'fit_success'
- This error happened during the computation of the first time bin in the lightcurve analysis, and so I tried changing the conditions of that bin regarding both TS requirements and length, to no avail. The error persisted.
06/17
- As I was not being able to carry out the whole lightcurve analysis,
|
| | 06/21-06/24
06/27-07/01
07/05-07/08 |
|
<
< | 07/05 |
>
> | 07/05 |
| |
- As per Deivid's suggestion, I attempted carrying out lightcurve analysis freeing lower TS sources and a larger radius. Carried out this modification for the whole baseline analysis, the 1-week timeframe around the flare, and the source J0658. The fit still won't converge, and by looking at the residmap, it seems like there is no abnormal source, nothing unaccounted by the model.
- I had a Zoom chat with Janeth Valverde to consult on the lightcurve problem. Janeth pointed out that the problem might have to do with some of fermitools not running properly for a source this faint. Instead of using Ari's pipeline, she recommended doing a general check on that by running fermitools directly on the command line. She also recommended focusing solely in the last 6 months, and doing an unbinned analysis.
- Janeth also discussed trying out an adaptive binning strategy (in parallel to the other analyses). She shared this example as a demonstration of the usefulness of adaptive binning.
07/06 |
|
<
< | |
>
> |
- Contacted Ari Brill regarding the problem. He asked the following questions, as a sanity check:
"1) Did the baseline analysis using the entire dataset converge successfully? Were you able to look at the validation plots and see that the results seemed reasonable? 2) To follow up on what Qi was saying, if you look at the monthly lightcurve, you can see that there are years-long stretches in between the flares when the source isn't detected at all. So there are parts of the lightcurve that might not be detected even with a 12-week time bin. That shouldn't cause the fit to fail though. It should converge and report an upper limit. 3) Are you able to see the error message that's printed out? Just to make sure, do you have enough space in your output directory to store all of the output files?"
-
|
| |
--  Massimo Capasso - 2022-06-16 |
Copyright © 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.