Autonicer

Latest version: v1.3.0

Safety actively analyzes 714792 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 3

1.1.0

Not secure
- Added two new columns to the output log: CALDB_ver and DateTime. Also changed the "Name" column to "OBSID". This should lead to less confusion and give the user a better idea of which calibration version was used to process their data, and at what point in time they processed that data.

1.0.2

Not secure
- Limited the astropy dependency to versions less than v5.1 since the changes in astropy v5.1 mess with the time conversions. (Future versions will make autonicer compatable with astropy v5.1)

1.0.1

Not secure
- PRIMARY: Changed the way output ques/logs are written out. Users may now select if they want to add to an exisiting log file or create a new log file.
- SECONDARY: Added testing of functions that can be tested without requiring the retrieval of NICER observational data for CI testing on the github end.
- Added coloration of text in the terminal when running autoNICER so a user can be more aware of the where in the procedure autoNICER is.

1.0.0

- Added cycle selection functionality with the command "cycle [cycle ]"
- Added rm command to remove either all selected obsid's with `rm all`, or a specific obsid with `rm obsid` where "obsid" is the observation ID we want removed from the processing queue

Changes Pre-v1.0.0 release
- Original version of this code specifically written for work on a small VM
- Elimination of the count rate functionality tool
- Streamiling so it runs from the directory its called in
- Changed the barycenter correction to include the modern ephemeris set to JPLEPH.430 and to custom set RA and DEC without changing the code
- Added further automation to pull directly from heasarc
- Auto pulls year, month, ra, and dec
- Added auto queing generation option
- Added automatic tar.gz compression to all .evt files with the exception of the bary-center corrected mpu7_cl.evt file
- Fixed issue of outpath not being fully written out in the output que

Page 3 of 3

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.