B2025-015 RO Editor - PROMS will get stuck in a loop (hang) while placing RO.FST information in the plant database (loading RO's) when Unit Values contain brackets. Example is Point Beach data. #523

2025-02-20T10:03:06-05:00

mschill commented

2025-02-20 10:03:06 -05:00

B2025-015 RO Editor - PROMS will get stuck in a loop (hang) while placing RO.FST information in the plant database (loading RO's) when Unit Values contain brackets. Example is Point Beach data.

Some of Point Beach RO's have curly braces in the RO return value for the units in P/C. Found this on some (5-7) Annunciator RO values. The definition of the return value (multiple return values) uses curly braces so PROMS cannot distinguish between brackets being part of a unit value or part of the format for multiple return values.

Equipment Designation, Main Steam (MS), Annunciators have examples of return values with curly braces. Look at the Referenced Object Definition on the Annunciators tree node for the definition of the return value.

B2025-015 RO Editor - PROMS will get stuck in a loop (hang) while placing RO.FST information in the plant database (loading RO's) when Unit Values contain brackets. Example is Point Beach data. Some of Point Beach RO's have curly braces in the RO return value for the units in P/C. Found this on some (5-7) Annunciator RO values. The definition of the return value (multiple return values) uses curly braces so PROMS cannot distinguish between brackets being part of a unit value or part of the format for multiple return values. Equipment Designation, Main Steam (MS), Annunciators have examples of return values with curly braces. Look at the Referenced Object Definition on the Annunciators tree node for the definition of the return value.

B2025-015_GIT_testing.docx

511 KiB

mschill added 1 commit 2025-02-20 10:03:06 -05:00

B2025-015 RO Editor - PROMS will get stuck in a loop (hang) while placing RO.FST information in the plant database (loading RO's) when Unit Values contain brackets. Example is Point Beach data. 9980504c47

Some of Point Beach RO's have curly braces in the RO return value for the units in P/C.  Found this on some (5-7) Annunciator RO values.  The definition of the return value (multiple return values) uses curly braces so PROMS cannot distinguish between brackets being part of a unit value or part of the format for multiple return values.

Equipment Designation, Main Steam (MS), Annunciators have examples of return values with curly braces.  Look at the Referenced Object Definition on the Annunciators tree node for the definition of the return value.

djankowski was assigned by mschill

2025-02-20 10:03:16 -05:00

jjenko was assigned by mschill

2025-02-20 10:03:16 -05:00

mvickers was assigned by mschill

2025-02-20 10:03:16 -05:00

mschill requested review from jjenko 2025-02-20 10:03:19 -05:00

jjenko approved these changes 2025-02-20 10:08:38 -05:00

jjenko left a comment

changes look good

jjenko merged commit 18734e0f85 into Development

2025-02-20 10:08:52 -05:00

jjenko referenced this issue from a commit

2025-02-20 10:08:54 -05:00

Merge pull request 'B2025-015 RO Editor - PROMS will get stuck in a loop (hang) while placing RO.FST information in the plant database (loading RO's) when Unit Values contain brackets. Example is Point Beach data.' (#523) from B2025-015 into Development

mvickers commented

2025-02-20 15:30:29 -05:00

Tested with version 2.2.2502.2010 and sql version 2502.1911. Works as expected. Used the Modified WEP backup and the ROEPU ro folder.

Sign in to join this conversation.

3 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Volian/SourceCode#523