-
Notifications
You must be signed in to change notification settings - Fork 10
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
Fix compatibility with glue 1.19+ #110
Closed
Closed
Changes from 5 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
e8d0d90
Revert "temporarily avoid conflicts introduced by recent glue release…
kecnry a6d7b09
update jdaviz pin to pull in upstream fix
kecnry fe6cb7f
changelog entry
kecnry 7c82d59
bypass jdaviz unit converter
kecnry 692970d
avoid error for incompat unit conversion request
kecnry e8dedb3
TMP: expose traceback for incompat unit conversion
kecnry File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not sure why this would be necessary. If you comment this out and put a print statement in its place, you can see that glue is calling
to_unit
to convert between time and flux units. @dhomeier - any ideas? Is this safe for now or not a good idea?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not surprised it wants some flux-like units for
data.get_component('flux').units
, the question perhaps still remains, how did thecid
get assigned to 'flux' here?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added a commit that raises the traceback if that helps. From the
values
, it seems that this is actually the time (dt
) component, but getting a request to translate units with and incorrectcid
andtarget_units
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This traceback can be reproduced with this branch of
lcviz
(with theraise ValueError
included in the if-statment), jdaviz released (3.9.1) or main, and glue 1.19+.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just for the record, got the traceback I just mentioned with released glue-core==1.18.0, jdaviz==3.9.1, lcviz==0.3.0 on
lcviz.load_data(tpf)
:With the current main branch this works up to displaying the TPF, but I don't see much functionality in selecting another frame or time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Screenshot is with main (same with this branch) and glue 1.18; there are no exceptions raised, just trying to figure out how this is supposed to work (e.g. what the time axis is mapped to).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With this branch and 1.20 I am also getting a units-related error, but at a different point than #110 (comment) in setting up a callback:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if you want to actually use the slicing, then you can add a light curve as well:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, that works better – with the default stretch the image was indeed saturated almost everywhere and thus never seemed to change; also when shown on its own the TPF
x
range is set to [0, 1] d, when not much is happening at all.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dhomeier - are there any updates on this? I'm migrating this work over to #105 now, but would like to avoid this hacky workaround if possible.