-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added tests for LongitudinalProfileFromData and fix for issue #185 #309
Merged
MaxThevenet
merged 37 commits into
LASY-org:development
from
em-archer:spectrum_from_file
Oct 17, 2024
Merged
Added tests for LongitudinalProfileFromData and fix for issue #185 #309
MaxThevenet
merged 37 commits into
LASY-org:development
from
em-archer:spectrum_from_file
Oct 17, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adding tests to allow for longitudinal profile from spectral data, whether monotonically increasing or decreasing
Editing LongitudinalProfileFromData to allow for monotonically decreasing spectral data
for more information, see https://pre-commit.ci
Updated tests for monotonically increasing or decreasing specta
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
Wavelength and wavelength axis given different names
for more information, see https://pre-commit.ci
Analytic ft of GaussianLongitudinalProfile needs checking
Analytic spectrum checked in separate script
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
…omega When data["datatype"] = "spectral", data["axis"] can either be wavelength lambda in m or angular frequency omega in s^-1. The user doesn't need to specify, it will automatically detect and convert to wavelength if the latter is passed.
for more information, see https://pre-commit.ci
User must now specify axis type (wavelength by default). Also added proper conversion for spectral intensity if axis is omega.
for more information, see https://pre-commit.ci
Co-authored-by: Maxence Thévenet <[email protected]>
Co-authored-by: Maxence Thévenet <[email protected]>
MaxThevenet
changed the title
[Correct branch] Added tests for LongitudinalProfileFromData and fix for issue #185
Added tests for LongitudinalProfileFromData and fix for issue #185
Oct 17, 2024
MaxThevenet
reviewed
Oct 17, 2024
MaxThevenet
approved these changes
Oct 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Editing LongitudinalProfileFromData to allow for monotonically decreasing spectral data (fix for #185) and adding relevant tests to test_laser_profiles. Currently no tests exist for LongitudinalProfileFromData, so adding tests for monotonically increasing/decreasing spectral data. Test for temporal data could be added in future.