Conversation
data is not installed by the pip command so it is not useful to clone the repo recursively
Added information about creating a shallow clone with --depth parameter.
| - Command | ||
| - Status | ||
| * - Linux | ||
| - ``conda env create -f https://tomographicimaging.github.io/scripts/env/cil_development.yml`` |
There was a problem hiding this comment.
conda env create -f https://tomographicimaging.github.io/scripts/env/cil_development.yml
CondaHTTPError: HTTP 404 NOT FOUND for url https://tomographicimaging.github.io/scripts/env/cil_development.yml
There was a problem hiding this comment.
For anyone else who is testing the files are here and you need to use them instead of the url:
https://github.com/TomographicImaging/scripts/pull/9/changes
There was a problem hiding this comment.
That's right, I didn't want to link to a PR, so I wrote the link as it will be once #9 is merged
casperdcl
left a comment
There was a problem hiding this comment.
a bit concerned about:
- repetition in
README.md&developer_guide.rst(would prefer one to link to the other) - lack of mention of conda env names (
create --name <env_name>&&activate <env_name)
Signed-off-by: Casper da Costa-Luis <casper.dcl@physics.org>
Co-authored-by: Nalin Gupta <nalin.gupta3142@gmail.com> Signed-off-by: Laura Murgatroyd <60604372+lauramurgatroyd@users.noreply.github.com>
| bash ./scripts/create_local_env_for_cil_development.sh | ||
| ``` | ||
|
|
||
| Or with the CIL build and test dependencies: |
There was a problem hiding this comment.
Should we remove the batch script file itself if we no longer recommend to use it?
There was a problem hiding this comment.
I have done this, please let me know if ok
|
|
||
| You can achieve this in two ways: | ||
|
|
||
| 1. by opening a "Developer Command Prompt for Visual Studio" and activating the conda environment from there. This requires you |
There was a problem hiding this comment.
| 1. by opening a "Developer Command Prompt for Visual Studio" and activating the conda environment from there. This requires you | |
| 1. by opening a "Developer Command Prompt for VS" and activating the conda environment from there. This requires you |
I do not have anything called "Developer Command Prompt for Visual Studio"
There was a problem hiding this comment.
Please can you check the name of yours @paskino , I wonder if its a typo or if the name of the program is different in different versions
There was a problem hiding this comment.
x64 Native Tools Command Prompt for VS
might be the better option here?
There was a problem hiding this comment.
yes that's what mine is called, and was in my original instructions
|
|
||
| If you are developing on Windows with conda, you need to have access to both the Visual Studio compiler and the conda environment. | ||
|
|
||
| You can achieve this in two ways: |
There was a problem hiding this comment.
I just retested and found the instructions below worked for me, so I am happy that they are correct provided we state versions we tested with. I added the version of Visual Studio I had, as a suggested change Any other versions we should include a note of?
|
Hi @paskino I am going to take over your branch. I will merge in my suggestions from yesterday, just leaving the questions I had. In stand-up today we agreed to remove duplication and have all of the content in the developer guide, and the README linking to the developer guide. I will make this change. |
Co-authored-by: Casper da Costa-Luis <casper.dcl@physics.org> Co-authored-by: Laura Murgatroyd <60604372+lauramurgatroyd@users.noreply.github.com> Co-authored-by: Edoardo Pasca <14138589+paskino@users.noreply.github.com> Signed-off-by: Laura Murgatroyd <60604372+lauramurgatroyd@users.noreply.github.com>
|
Hi, this PR is now ready for review again. I actioned the changes I suggested. Please see the unresolved threads for open questions. |
gfardell
left a comment
There was a problem hiding this comment.
I'm confused by the environment file links not working, maybe they are in an unmerged PR?
However, I would have thought that using the environment files that ship with CIL is good enough as users will need to clone the repositories by default. Was there a reason to move away from that?
| - cvxpy maximum version set to 1.7.5 to fix #2303 (#2304) | ||
| - Documentation: | ||
| - Render the user showcase notebooks in the documentation (#2189) | ||
| - Update on build instructions in README and developer guide for all OS |
There was a problem hiding this comment.
Adds conda environment paths to find IPP command in cmake?
|
|
||
| You can achieve this in two ways: | ||
|
|
||
| 1. by opening a "Developer Command Prompt for Visual Studio" and activating the conda environment from there. This requires you |
There was a problem hiding this comment.
x64 Native Tools Command Prompt for VS
might be the better option here?
Co-authored-by: Gemma Fardell <47746591+gfardell@users.noreply.github.com> Signed-off-by: Laura Murgatroyd <60604372+lauramurgatroyd@users.noreply.github.com>
This PR in scripts has the env file: https://github.com/TomographicImaging/scripts/pull/9/changes I am not sure where they should live - we need to discuss what the purpose of https://github.com/TomographicImaging/scripts is |
Signed-off-by: Casper da Costa-Luis <casper.dcl@physics.org>
casperdcl
left a comment
There was a problem hiding this comment.
We could also move scripts/requirements-test.yml to just environment.yml in the root.
|
We will move the dev environment files into CIL, not host them in scripts, see: TomographicImaging/scripts#9 (review) |
Co-authored-by: Gemma Fardell <47746591+gfardell@users.noreply.github.com> Signed-off-by: Laura Murgatroyd <60604372+lauramurgatroyd@users.noreply.github.com>



Description
FindIPP.cmaketo find IPP libraries on WindowsExample Usage
Contribution Notes
Changes
README.md-Ccmake.define.IPP_ROOT=$CONDA_PREFIXwas passedTesting you performed
Local build on:
Checked the artifact documentation produced by GHA.
Linux
On Linux a total of 43 tests are skipped:
Plus these which test compatibility with SIRF (which is not installed)
Windows
Related issues/links
Checklist