BEAMnrc and DOSXYZnrc #1168
Replies: 4 comments 3 replies
-
|
Set |
Beta Was this translation helpful? Give feedback.
-
|
Yes I deleted the file and put iwatch output to none and when I did a new
execute on BEAMnrc and the number of history was 60000000 it took three
hours to finish and now I did a run on DOSXZYnrc but the same thing it
stopped and no message appeared even though when I used isource=1 it only
took six minutes to finish and get the 3ddose file but when I used
isource=9 it stopped at the same picture above I know on Windows does this
take a long time
…On Thu, Aug 15, 2024, 6:41 PM Reid Townson ***@***.***> wrote:
Set IWATCH output to None. You've selected in the inputs to store a file
that tracks every interaction history, which will get very large quite
quickly (the .egsgph file). You can safely delete this file. The simulation
may be crashing because of the size of this file.
—
Reply to this email directly, view it on GitHub
<#1168 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BJLSEJV3B4UKSM2O6WY75YTZRTD3RAVCNFSM6AAAAABMQETG6SVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMZUHE2DCNQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
In DOSXYZnrc, if you surround the phantom with vacuum it can cause a crash like this. Check the value of "medsur", or the medium surrounding the phantom. You probably want to make sure it's a "1", instead of a "0", if the first material in your list of materials in the .egsphant file is air. See page 29 of the DOSXYZnrc manual for details. You need to make this change in the input file, not using the GUI, if you're using an .egsphant file (because the GUI doesn't know the materials that are in the phantom). |
Beta Was this translation helpful? Give feedback.
-
|
thanks for the reply, yes the medium of the region outside Phantom is Vacuum I will
change to AIR700ICRu.No the first medium is water
…On Thu, Aug 15, 2024, 9:25 PM Reid Townson ***@***.***> wrote:
In DOSXYZnrc, if you surround the phantom with a vacuum it can cause a crash
like this. Check the value of "medsur", or the medium surrounding the
phantom. You probably want to make sure it's a "1", instead of a "0", if
the first material in your list of materials in the .egsphant file is air.
See page 29 of the DOSXYZnrc manual for details. You need to make this
change in the input file, not using the GUI, if you're using an .egsphant
file (because the GUI doesn't know the materials that are in the phantom).
—
Reply to this email directly, view it on GitHub
<#1168 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BJLSEJS353KJEQVYW5HSRHDZRTXC5AVCNFSM6AAAAABMQETG6SVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMZVGEZDQNQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
In DOSXYZnrc the option to edit EGSnrc parameters does not appear at the bottom. What is the reason? note that this option exists in BEAMnrc. can help me, please |
Beta Was this translation helpful? Give feedback.
-
|
It looks like the bottom of the window is cut off. There are 3 buttons at the bottom of the window, and one of them allows you to edit the EGSnrc transport parameters. The GUI windows don't resize well on small screens, unfortunately, but you could try playing with resolution or hooking up a monitor. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much |
Beta Was this translation helpful? Give feedback.
-
I tried using the output for BEAM_firsttrial in DOSXYZnrc by source 9, but after running the stop, as shown in the picture below, it did not show the message finished run or job failed. in BEAM_firsttrial Some files appeared in the folder after being run in dosxyznrc, and the size of this folder was 12 GB. Please, can anyone help me?
Beta Was this translation helpful? Give feedback.
All reactions