Phot2lc

Latest version: v1.8.1

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

Scan your dependencies

Page 4 of 7

1.5.5

--------------------------
> Bug in quicklook's import statements. Fixed.

1.5.4

--------------------------
> Added more functionality to the "quicklook" tool.
- Now includes 4 command line options:
1) -f --files
Input file(s) to perform quicklook on.
2) -s --show
Whether to display the quicklook plot.
3) -p --prewhiten
Whether to perform a pre-whitening sequence.
4) -w --wqedlc
Whether the input file(s) are from WQED.
5) -h --help
Print out command line options.

1.5.3

--------------------------
> Forgot to edit the setup.py file to include the new
"quicklook" tool as a script. Bug has been fixed
and quicklook is now available.

1.5.2

--------------------------
> Fixed the command list printed with "?" to include all
available options, a few had been missing from the
"Aperture Selection" list.
> Improved the layout of the Aperture Selection Window.
- Now show significance thresholds for both the
User and Grid periodograms.
- Uses only red and white color scheme to more
clearly indicate what lines/markers/values
correspond to the Grid vs. User light curves.
- Now shows the maximum signal-noise of the highest
peak in the periodogram:
(Max S/N = Max Peak Height / Average Noise Level)
> Created a new command line tool named "quicklook"
which generates a plot of an extracted light curve
along with its periodogram and marks significant
peaks determined by a pre-whitening routine.

1.5.1

--------------------------
> Fixed bug related to improper exposure time format. The
"get_time" function within photfunc.py assumed that
FITS header's exposure time value was a float, but
occasionally it would be a different format. This
resulted in errors within phot2lc when doing float
arithmetic on the exposure time parameter. Now, the
get_time function will convert the exposure time to
type float upon loading it from the header.

1.5.0

--------------------------
> Found and fixed a significant issue related to the
calculation of the Barycentric Julian Date (BJD) at
the start of the exposure sequence which gets saved
as the header keyword BJED in the .lc and .phot files.
The BJD should have have been referencing the very
first image, regardless of whether the first data point
got removed from the final light curve. Instead, it was
referencing the first non-deleted data point. The
barycentric corrected timestamps were shifted to
reference this time, so the timings from previous versions
won't be incorrect, but the raw timings were not shifted
to reference this time, so large discrepancies could
sometimes be seen when comparing the raw and barycorr
time columns. This has been fixed so that the BJED
keyword now always references the first image of a run,
and both time columns now reference the same BJED.

Page 4 of 7

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.