You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,6 +17,8 @@ CAD_to_OpenMC uses cadQuery and its links to OCCT
17
17
The code structure relies on a main class *Assembly*, which maintains the geometry in terms of a list of instances of the subclass Entity.
18
18
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.
19
19
20
+
We've written a paper covering this software: [](https://joss.theoj.org/papers/fc9555a355e3d399303a371bfce633f5)
21
+
20
22
# Other options
21
23
22
24
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_
46
48
1. In the directory where you want your environment to reside do: ```python -m venv <name>```
47
49
2. Activate the environment: ```source <name>/bin/activate```
48
50
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```
0 commit comments