Difference: 2022PabloDrakeResearchJournal (7 vs. 8)

Revision 82022-08-12 - PabloDrake

Line: 1 to 1
 
META TOPICPARENT name="2022Journals"

Pablo Drake Research Journal (Summer '22)

06/06-06/10

Line: 17 to 17
 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.
Changed:
<
<
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
Changed:
<
<
ModuleNotFoundError: No module named 'encodings'

06/10

>
>
ModuleNotFoundError: No module named 'encodings' 06/10
 
  • Started writing a log/manual fermipy document, noting down the different errors that appear.
  • Found out the error was caused when simultaneously calling through my .myprofile doc VEGAS and fermipy code, possibly because of a conflict between subpackages. Another error appeared:
Changed:
<
<
Traceback (most recent call last):

File "./run_analysis.py", line 348, in <module> free_sources=pipeline_config.get('free_sources'))

>
>
Traceback (most recent call last):
File "./run_analysis.py", line 348, in <module> free_sources=pipeline_config.get('free_sources'))
 File "./run_analysis.py", line 50, in run_analysis gta.setup()
Deleted:
<
<
 File "/a/share/ged/src/miniconda3/envs/fermipy-1.0.1/lib/python3.7/site-packages/fermipy/gtanalysis.py", line 1082, in setup c.setup(overwrite=overwrite)
Deleted:
<
<
 File "/a/share/ged/src/miniconda3/envs/fermipy-1.0.1/lib/python3.7/site-packages/fermipy/gtanalysis.py", line 5121, in setup self._ltc = LTCube.create(self.files['ltcube'])
Deleted:
<
<
 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])
Changed:
<
<
IndexError: list index out of range
>
>
IndexError: list index out of range
 
  • Read EGRET (GeV) Blazars by Prof. Mukherjee. Wrote a set of reference notes.

06/13-06/17

Line: 52 to 43
  06/15
  • Started working on creating a full dataset lightcurve. The following error appeared:
Changed:
<
<
Traceback (most recent call last):

File "/nevis/milne/files/pd2629/fermi_analysis/run_analysis_std.npy", line 349, in <module>

>
>
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)
Deleted:
<
<
 File "/nevis/milne/files/pd2629/fermi_analysis/run_analysis_std.npy", line 253, in run_lightcurve
Deleted:
<
<
 gta.load_roi('{}.npy'.format(prefix))
Deleted:
<
<
 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,
Deleted:
<
<
 roi_data = utils.load_data(infile, workdir=self.workdir)
Deleted:
<
<
 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
Deleted:
<
<
 Exception('Input file does not exist.')
Deleted:
<
<
 Exception: Input file does not exist.
Changed:
<
<
>
>
 
  • 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:
Changed:
<
<
Traceback (most recent call last):

File "/nevis/milne/files/pd2629/fer mi_analysis/run_analysis_std. py", line 350, in <module>

>
>
Traceback (most recent call last):
<span>File "/nevis/milne/files/pd2629/fer mi_analysis/run_analysis_std. py", line 350, in <module></span>
 run_lightcurve(fermipy_config, prefix, num_sections, section)
Changed:
<
<
File "/nevis/milne/files/pd2629/fer mi_analysis/run_analysis_std. py", line 261, in run_lightcurve
>
>
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)
Changed:
<
<
File "/a/share/ged/src/miniconda3/e nvs/fermipy-1.0.1/lib/python3. 7/site-packages/fermipy/ lightcurve.py", line 289, in lightcurve
>
>
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)
Changed:
<
<
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
>
>
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']:
Changed:
<
<
KeyError: '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, I focused on finishing the Jupyter notebook matplotlib data plotting manuals.
Line: 105 to 78
  06/23
  • However, another issue started popping up. The lightcurve analysis actually started, with the gtcube process finishing. However, when trying to fit the different time bins, the following sequence would happen (as can be checked in the log file):
Changed:
<
<
Analysis failed in time range 675480000 675566400

<class 'TypeError'>

Analysis failed in time range 675566400 675652800

<class 'TypeError'>

Analysis failed in time range 675652800 675739200

<class 'TypeError'>

Analysis failed in time range 675739200 675825600

<class 'TypeError'>

Analysis failed in time range 675825600 675912000

<class 'TypeError'>

>
>
<span>Analysis failed in time range 675480000 675566400</span>
<span><class 'TypeError'></span>
<span>Analysis failed in time range 675566400 675652800</span>
<span><class 'TypeError'></span>
<span>Analysis failed in time range 675652800 675739200</span>
<span><class 'TypeError'></span>
<span>Analysis failed in time range 675739200 675825600</span>
<span><class 'TypeError'></span>
<span>Analysis failed in time range 675825600 675912000</span>
<span><class 'TypeError'></span>
 
  • As a matter of fact, a fits file would result from this analysis, but it wouldn't include any datapoints.
06/24
  • Contacted Dr. Qi Feng about
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback