Skip to content

Commit ea97bb6

Browse files
authored
Merge pull request #153 from openmsr/main
syncing some minor changes to readme
2 parents 8a05e02 + 835eeb2 commit ea97bb6

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

README.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,8 @@ CAD_to_OpenMC uses cadQuery and its links to OCCT
1717
The code structure relies on a main class *Assembly*, which maintains the geometry in terms of a list of instances of the subclass Entity.
1818
A geometry is imported from a (set of) .step files into the entity-list. This list is passed on to a mesher-class which generates a meshed geometry.
1919

20+
We've written a paper covering this software: [![status](https://joss.theoj.org/papers/fc9555a355e3d399303a371bfce633f5/status.svg)](https://joss.theoj.org/papers/fc9555a355e3d399303a371bfce633f5)
21+
2022
# Other options
2123

2224
CAD_to_OpenMC is certainly not the only package that tries to solve this problem. Other options include:
@@ -46,7 +48,7 @@ _replace \<name\> with an arbitrary name for your virtual environment_
4648
1. In the directory where you want your environment to reside do: ```python -m venv <name>```
4749
2. Activate the environment: ```source <name>/bin/activate```
4850
3. Build and install moab (if not already installed). The moab team relies on conda for standard installation but are working on a pip-based solution. Once that is done moab would simply be added to the requirements-file instead.
49-
1. Clone the moab code-repository: e.g. ```git clone git@bitbucket.org:fathomteam/moab.git```
51+
1. Clone the moab code-repository: e.g. ```git clone https://bitbucket.org/fathomteam/moab.git```
5052
2. Configure and build the code:
5153
```bash
5254
mkdir build;

0 commit comments

Comments
 (0)