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
Coupled TRACE/PARCS models require a specially-formatted file called maptab, created during the development of the models, which contains data to specify the mapping of the PARCS mesh to the TRACE mesh. At the beginning of a TRACE/PARCS run, SNAP reads in the maptab and creates an altered copy in the run directory. This altered copy erroneously has all of the hydraulic component and heat structure IDs replaced with '1'. This bug causes the TRACE run to fail during initialization.
The text was updated successfully, but these errors were encountered:
SNAP attempts to parse the PARCS / TRACE Maptab file into the TRACE model PARCS Mapping component. This currently behaves correctly in the samples we have on site. Would it be possible to get access to the TRACE input, PARCS input and MAPTAB file in question?
Pretty sure the model that triggered this bug has proprietary information in it. I'll see what I can do in terms of providing an example case and get back to you.
@mrose-nrc Mike, the ISL/SNAP devs will be getting their official clearances in a month or two (optimism!) at which point you can share such models with them “in place” on the fileserver.
Chester,
Thanks for letting me know.
* Mike
From: Chester Gingrich ***@***.***>
Sent: Monday, 24 July, 2023 8:27
To: NRC-Research/SNAP-issues ***@***.***>
Cc: Michael Rose ***@***.***>; Author ***@***.***>
Subject: [External_Sender] Re: [NRC-Research/SNAP-issues] SNAP 4.0.4: For coupled TRACE/PARCS runs, SNAP outputs erroneous maptab file (Issue #38)
Testing to see what replying to this does from NRC outlook email.
Mike, the ISL/SNAP devs will be getting their official clearances in a month or two (optimism!) at which point you can share such models with them “in place” on the fileserver.
--------------------
Chester Gingrich
SNAP Project Manager (COR)
Sr. Reactor Systems Engineer
RES/DSA/CRAB
Office: (301) 415-2173
MS: TWFN-9 D25
From: Michael Rose ***@***.***>
Sent: Friday, July 21, 2023 1:21 PM
To: NRC-Research/SNAP-issues ***@***.***>
Cc: Subscribed ***@***.***>
Subject: [External_Sender] Re: [NRC-Research/SNAP-issues] SNAP 4.0.4: For coupled TRACE/PARCS runs, SNAP outputs erroneous maptab file (Issue #38)
Pretty sure the model that triggered this bug has proprietary information in it. I'll see what I can do in terms of providing an example case and get back to you.
—
Reply to this email directly, view it on GitHub<#38 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANNVX2HTK6RNOKFO4G5V2P3XRK3BTANCNFSM6AAAAAASEXQRIQ>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
—
Reply to this email directly, view it on GitHub<#38 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AVCESVJ6EP3TCJQI3DWM4PLXRZS25ANCNFSM6AAAAAASEXQRIQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
Coupled TRACE/PARCS models require a specially-formatted file called maptab, created during the development of the models, which contains data to specify the mapping of the PARCS mesh to the TRACE mesh. At the beginning of a TRACE/PARCS run, SNAP reads in the maptab and creates an altered copy in the run directory. This altered copy erroneously has all of the hydraulic component and heat structure IDs replaced with '1'. This bug causes the TRACE run to fail during initialization.
The text was updated successfully, but these errors were encountered: