-
Notifications
You must be signed in to change notification settings - Fork 2
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
Mb/explicit #82
Mb/explicit #82
Conversation
I guess there are issues remains with the simulation data. Since there is no conflict with current code. I would suggest we rebase and merge it first. |
Yes, also on my other machine everything works and passes all the tests now... but I do not understand the actual problem. Still, I think that the benefits of merging now (even without these four tests passing) outweigh the problems it will cause if we diverge too much. |
I would prefer that we at least identify the problem before merging anything. Could someone else reproduce the problem? |
My bad. |
I've made a bug report, https://jira.eso.org/browse/PIPE-12044 , and two PR's, one with some tests https://gitlab.eso.org/cpl/pyesorex/-/merge_requests/18 , and one with your fix, https://gitlab.eso.org/cpl/pyesorex/-/merge_requests/19 . I don't think you can access those, but I thought it would be good to add a link to them anyway. I can put the branches also on our fork. But it shouldn't be too hard to work around this bug for now right? Maybe we can automatically add a dummy parameter to every recipe or something like that? I much prefer adding such an ugly workaround than having broken tests. |
Or perhaps we can keep these lines in?
I also want to note that I still had problems even with your fixed pyesorex. Because wouldn't removing this line result in |
Yes, we should keep this line in, as a system-wide If I understand it correctly, |
By the way, in my bug report I noted that the first recipe on https://www.eso.org/sci/software/pycpl/pycpl-site/user/basics.html does not specify any parameters, so it actually is I added a suggestion to add a dummy parameter; would that work for now? |
I pushed my test branch to our fork as well, see https://github.com/AstarVienna/pyesorex/tree/addtests . (By the way, I deleted all the nonsense branches in the pyesorex fork, but they keep turning up again, so need to figure out what is happening.) |
Here we go 🥇 |
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.
It would be good to also add these new recipes to the esorex and EDPS tests, but we can do that later.
Finished converting the
InputSet
s andInput
classes to the implicit detection of tag parameters (detector, target, ...).Also added more test to cover for new edge cases (not many though).