T Ehrhardt
T Ehrhardt
See https://github.com/icecube/pisa/blob/a752eaf0f7d75c3d002d3c8ccde4a100ca1bf594/setup.py#L311 and https://setuptools.pypa.io/en/latest/userguide/entry_point.html. Console scripts that are non-existent (test by running each command) and should be removed: * `pisa-analysis` * `pisa-postproc` * `pisa-fit_discrete_sys` and `pisa-fit_discrete_sys_nd` * `pisa-make_asymmetry_plots` * `pisa-make_systematic_variation_plots`...
Currently, it is not exactly obvious to the user which sequence of stage.services can be combined into one working pipeline configuration without digging through a lot of code. While each...
Trying to access the [`representation` attribute](https://github.com/icecube/pisa/blob/a752eaf0f7d75c3d002d3c8ccde4a100ca1bf594/pisa/core/container.py#L62) of a newly instantiated `ContainerSet` results in: `AttributeError: 'ContainerSet' object has no attribute '_representation'. Did you mean: 'representation'?` because `self._representation` is [not assigned a...
Expected to be Python 3.11 and 3.12 compatible. Some tests done after updating versioneer (see https://github.com/icecube/pisa/issues/779#issuecomment-2289994626): * successful installation of PISA with Python 3.10.14, version number returned by [`pisa.__version__`](https://github.com/icecube/pisa/blob/master/pisa/__init__.py#L84) agrees...
One might be inclined to use the above python releases because [the installation guide](https://github.com/icecube/pisa/blob/master/INSTALL.md) states that "you can choose your preferred version of python >= 3.10". This is followed by...
Global best-fit values from various [NuFIT](http://www.nu-fit.org) versions beyond 2.2 are defined in the config files in https://github.com/icecube/pisa/tree/f739ae4280ebdd5dc36d5b5ed0132f1feec34368/pisa_examples/resources/settings/osc, but the readme doesn't reflect that. It might also be helpful to point...
Apart from the issues that * supposedly, "the analysis guide" explains the difference between "parameterized-Monte Carlo (MC) stages and reweighted-MC stages", * and that the readme refers to the ezFIT...
* https://github.com/icecube/pisa/blob/master/pisa_tests/test_changes_with_combined_pidreco.py uses nonexistent pipeline configs to address pisa 2 vs. 3 compatibility issues * https://github.com/icecube/pisa/blob/master/pisa_tests/test_command_lines.sh tries to run a nonexistent python script (pisa/scripts/make_toy_events.py) and assumes every `.py` file to...
This should be a part of general [PISA conventions](https://github.com/icecube/pisa/blob/master/pisa/general_conventions.md) (again). The short readme https://github.com/icecube/pisa/blob/master/pisa/stages/README.md contains some useful bits and pieces but is far from comprehensive. See also https://github.com/icecube/pisa/issues/513.
I decided to open this issue as a place to document any future discussion about this topic. The PISA guide on general conventions has been stating for a long time...