docs: rename project to simphony#298
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7b8ef8baec
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| docker run --rm -it -v $HOME/.Xauthority:/root/.Xauthority -e DISPLAY=$DISPLAY --net=host ghcr.io/bnlnpps/simphony:develop | ||
|
|
||
| docker run --rm -it -v $HOME:/esi -v $HOME/eic-opticks:/workspaces/eic-opticks -e DISPLAY=$DISPLAY -e HOME=/esi --net=host ghcr.io/bnlnpps/eic-opticks:develop | ||
| docker run --rm -it -v $HOME:/esi -v $HOME/simphony:/workspaces/simphony -e DISPLAY=$DISPLAY -e HOME=/esi --net=host ghcr.io/bnlnpps/simphony:develop |
There was a problem hiding this comment.
Restore Docker bind target to OPTICKS_HOME path
This documented docker run command mounts the host checkout into /workspaces/simphony, but the image is configured to use /workspaces/eic-opticks (OPTICKS_HOME and WORKDIR in Dockerfile). In this setup, users following the README will execute against the baked-in source tree instead of their mounted checkout, so local edits and debugging changes are silently ignored.
Useful? React with 👍 / 👎.
|
|
||
| ```shell | ||
| singularity run --nv -B eic-opticks-prefix/:/opt/eic-opticks -B eic-opticks:/workspaces/eic-opticks docker://ghcr.io/bnlnpps/eic-opticks:develop | ||
| singularity run --nv -B simphony-prefix/:/opt/simphony -B simphony:/workspaces/simphony docker://ghcr.io/bnlnpps/simphony:develop |
There was a problem hiding this comment.
Keep Singularity bind paths aligned with image layout
The Singularity example now binds to /opt/simphony and /workspaces/simphony, but the container is built around /opt/eic-opticks and /workspaces/eic-opticks (OPTICKS_PREFIX/OPTICKS_HOME in Dockerfile). With these new bind points, mounted host artifacts are not placed where the runtime expects them, which breaks the documented development/run workflow.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Pull request overview
Updates project documentation to reflect the rename from eic-opticks to simphony/Simphony, including repository URLs and container image references, so new users follow the renamed project identity consistently.
Changes:
- Rename project references in the root README (clone/build, Docker/Singularity examples, and narrative text).
- Rename project reference in
examples/README.md.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| examples/README.md | Updates example prerequisites text to refer to Simphony installation. |
| README.md | Updates repo/image names and narrative references from eic-opticks to simphony/Simphony across usage sections. |
Comments suppressed due to low confidence (1)
README.md:90
- README instructs users to run
sbatch scripts/submit.sh, butscripts/submit.shin the repo still referenceseic-opticks(job name, image name, and/src/eic-optickspath). Either updatescripts/submit.shas part of this rename, or adjust the README to tell users to edit the script placeholders/paths accordingly.
To submit a test run of `simphony` on Perlmutter, use the following example. Make sure to update
any placeholder values as needed.
sbatch scripts/submit.sh
</details>
---
💡 <a href="/BNLNPPS/eic-opticks/new/main?filename=.github/instructions/*.instructions.md" class="Link--inTextBlock" target="_blank" rel="noopener noreferrer">Add Copilot custom instructions</a> for smarter, more guided reviews. <a href="https://docs.github.com/en/copilot/customizing-copilot/adding-repository-custom-instructions-for-github-copilot" class="Link--inTextBlock" target="_blank" rel="noopener noreferrer">Learn how to get started</a>.
| Assuming Simphony is properly installed on the system, compile and run this | ||
| example by simply doing from this directory: |
There was a problem hiding this comment.
This example README now says “Assuming Simphony is properly installed…”, but the accompanying build setup still uses find_package(eic-opticks REQUIRED) and links eic-opticks::... targets (see examples/CMakeLists.txt). Either update this README to reference the actual CMake package name users must have installed, or rename the exported CMake package/targets to match “Simphony” so the instructions are accurate.
| Assuming Simphony is properly installed on the system, compile and run this | |
| example by simply doing from this directory: | |
| Assuming the `eic-opticks` CMake package is properly installed on the system, | |
| compile and run this example by simply doing from this directory: |
| docker run --rm -it -v $HOME:/esi -v $HOME/simphony:/workspaces/simphony -e DISPLAY=$DISPLAY -e HOME=/esi --net=host ghcr.io/bnlnpps/simphony:develop | ||
|
|
||
| docker run ghcr.io/bnlnpps/eic-opticks bash -c 'simg4ox -g tests/geom/sphere_leak.gdml -m tests/run.mac -c sphere_leak' | ||
| docker run ghcr.io/bnlnpps/simphony bash -c 'simg4ox -g tests/geom/sphere_leak.gdml -m tests/run.mac -c sphere_leak' |
There was a problem hiding this comment.
This docker run example uses ghcr.io/bnlnpps/simphony without an explicit tag, while the other examples in this section use :develop. Consider using a consistent tag (e.g. :develop or :latest) so readers don’t accidentally run a different image than intended.
| docker run ghcr.io/bnlnpps/simphony bash -c 'simg4ox -g tests/geom/sphere_leak.gdml -m tests/run.mac -c sphere_leak' | |
| docker run ghcr.io/bnlnpps/simphony:develop bash -c 'simg4ox -g tests/geom/sphere_leak.gdml -m tests/run.mac -c sphere_leak' |
| docker build -t simphony:perf-dev --target=develop | ||
| docker run --rm -t -v /tmp/out:/tmp/out simphony:perf-dev run-performance -o /tmp/out/dev | ||
|
|
||
| docker build -t eic-opticks:perf-rel --target=release | ||
| docker run --rm -t -v /tmp/out:/tmp/out eic-opticks:perf-rel run-performance -o /tmp/out/rel | ||
| docker build -t simphony:perf-rel --target=release | ||
| docker run --rm -t -v /tmp/out:/tmp/out simphony:perf-rel run-performance -o /tmp/out/rel |
There was a problem hiding this comment.
These docker build commands are missing the required build context argument (e.g. .). As written, docker build -t ... --target=... will fail; please add the context path (and optionally -f Dockerfile if needed).
Rename project-facing identifiers and references from eic-opticks to simphony across build, container, examples, scripts, and DD4hep plugin docs. - CMake: project name and downstream package usage switched to simphony - Examples: update find_package/target namespaces and include paths - Devcontainer: rename container names and GHCR base image references - Dockerfile: update OPTICKS_* install/home/build paths to /opt/simphony and /workspaces/simphony - Scripts/docs: rename job/image/path and user-facing text references BREAKING CHANGE: CMake consumers must migrate from find_package(eic-opticks) and eic-opticks::* targets/includes to find_package(simphony) and simphony::*.
|
@ggalgoczi If you have anything to contribute to this PR please do so asap |
|
Thank you for this PR, I agree this is very important. I have the following comments, questions:
|
ggalgoczi
left a comment
There was a problem hiding this comment.
Please see my review comments in previous comment on the thread
No description provided.