search

idaholab / TMAP8

Tritium Migration Analysis Program, Version 8
https://mooseframework.inl.gov/TMAP8/
GNU Lesser General Public License v2.1
14 stars 17 forks source link

Add divertor monoblock simulation from Shimada2024 #147

Closed simopier closed 2 months ago

simopier commented 2 months ago

This PR adds an example case to model divertor monoblocks in TMAP8. The example is taken from the following publication:

M. Shimada, P.-C. A. Simon, C. T. Icenhour, and G. Singh, “Toward a high-fidelity tritium transport modeling for retention and permeation experiments,” Fusion Engineering and Design, Volume 203, 2024, 114438, ISSN 0920-3796, https://doi.org/10.1016/j.fusengdes.2024.114438.

(Ref. #144)

moosebuild commented 2 months ago

Job Documentation on e20adb7 wanted to post the following:

View the site here

This comment will be updated on new commits.

moosebuild commented 2 months ago

Job Coverage on e20adb7 wanted to post the following:

Coverage

Coverage did not change

Full coverage report

This comment will be updated on new commits.

simopier commented 2 months ago

I'm getting the following error in documentation: 

RENDER ERROR: Shortcut link key 'K' not found.

And I can't figure out how to fix it. Any suggestions @cticenhour @chaibhave ?

cticenhour commented 2 months ago

Without peeking at the changes, this error is usually triggered by an error using linking syntax. Check for [K] syntax in your code that isn't as you intended. MooseDocs thinks that you're trying to autolink using a designated shortcuts dictionary, but can't find the shortcut for "K".

simopier commented 2 months ago

Without peeking at the changes, this error is usually triggered by an error using linking syntax. Check for [K] syntax in your code that isn't as you intended. MooseDocs thinks that you're trying to autolink using a designated shortcuts dictionary, but can't find the shortcut for "K".

This was a lot simpler than I thought. ^^ I was looking for a format compatibility error or a faulty VSCode json setting. But no, it was just that the unit of temperature was noted [K] instead of (K)... Well, it's fixed now.