-
Notifications
You must be signed in to change notification settings - Fork 44
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
bump everything #1778
bump everything #1778
Conversation
Signed-off-by: Gemma Fardell <[email protected]>
and `__cuda` selector
added astra packages for GPU and non-CPU systems. Loosened version constraints in optional dependencies.
58f405f
to
2e6bf76
Compare
Signed-off-by: Gemma Fardell <[email protected]>
Passing! I Need to confirm builds with |
Did you fix TIGRE? I didn't see a PR. |
Oh I see TomographicImaging/TIGRE-conda@0141368 directly pushed to |
Yeah, I build and upload manually so I uploaded them to test and then pushed after :) |
Everything worked for me on windows and Linux! So I think we can merge and tag. |
Signed-off-by: Gemma Fardell <[email protected]>
Signed-off-by: Gemma Fardell <[email protected]>
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.
python-version: [3.9] | ||
numpy-version: [1.22] | ||
python-version: [3.11] | ||
numpy-version: [1.25] |
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.
why were these particular versions chosen for the conda action?
Sorry I realise my above screenshot didnt properly demonstrate it but basically none of the tigre plugin was rendered |
- astra-toolbox>=1.9.9.dev5,<2.1 | ||
- tigre=2.4 | ||
- ccpi-regulariser=22.0.0 | ||
- astra-toolbox>=1.9.9.dev5,<=2.1 |
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.
are we happy with a range of ASTRA versions or do we want to pin to 2.1 only?
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.
There's no interface changes between the two so I think it's ok. Backend changes are the user's responsibility.
- tigre=2.4 | ||
- ccpi-regulariser=22.0.0 | ||
- astra-toolbox>=1.9.9.dev5,<=2.1 | ||
- tigre>=2.4,<=2.6 |
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.
Do we accept a range of versions for TIGRE too?
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.
There's no interface changes between the two so I think it's ok. Backend changes are the user's responsibility.
force jenkins Signed-off-by: Gemma Fardell <[email protected]>
- `tomophantom` can generate phantoms to use as test data [Tomophantom](https://github.com/dkazanc/TomoPhantom) | ||
- `ipywidgets` enables visulisation tools within jupyter noteboooks |
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 wonder, shouldn't we need a table with versions requirements in the README?
Changes
merged all of the following into one branch:
Testing you performed
Related issues/links
Checklist
Contribution Notes
Please read and adhere to the developer guide and local patterns and conventions.