Releases: mmzdouc/fermo_core
Releases · mmzdouc/fermo_core
v0.4.3
v0.4.2
v0.4.1
v0.3.3
v0.3.2
v0.3.1
[0.3.1] 05-06-2024
Changed
- Loosened typing restrictions for Feature and Sample object attributes: area and height (intensity) now accept float values.
Removed
- [Breaking change] Removed toggle 'nonbiological' from 'FragmentAnnotator' and from parameters file; 'nonbiological' fragment annotation is now performed automatically
Security
- Instead of full file paths, only filenames are now written to the 'out.fermo.session.json' file
v0.3.0
[0.3.0] 03-06-2024
Changed
- [Breaking change] Parameter settings for
additional_modules/feature_filtering
were changed from a list of ranges to a dictionary with explicit values. - Reworked score assignment for qualitative phenotype data: phenotype-associated features now always receive a score of 1.0, and non-associated ones a score of 0.0.
- For all modules with runtime restriction, the 'maximum_runtime' parameter was set to a default of '0' (unlimited runtime). Therefore, runtime restriction must now be specified explicitly.
- Added a 'module_passed' parameter to all modules. This allows a more accurate description via the SummaryWriter (e.g. module was activated but timed out, and lack of e.g. annotation is due to premature ending and not because there were no hits).
v0.2.2
v0.2.1
v0.2.0
[0.2.0] 26-05-2024
Changed
- Replaced global logger with logger specific for
main_cli()
.main()
now needs an argumentlogger
- Reworked output file naming: all output files now start with
out.fermo.
and a suffix specifying their type - Removed output directory selection: the output directory is now always
results
located in the directory in which the peaktable resides. - Features now always have default result values (before, some Features could have an empty dictionary)
- MS2Query assignment now uses temporary directories for data reading/writing
Fixed
- Removed
sys.exit(0)
in case of successful run to fix compatibility issue with Celery task manager (fermo_gui
)