Skip to content

[DEFECT] Unpickling pickledROMs fails when running in parallel #2497

@j-bryan

Description

@j-bryan

Thank you for the defect report

Defect Description

An error is thrown when trying to use RAVEN's parallel processing capabilities when the workflow uses a pickled ROM. This was first observed when trying to run the HERON/tests/workshop/simple test in parallel (add <parallel/> node to <Case> in HERON input file). The following error is thrown:

AttributeError: Can't get attribute 'maxCyclesSpecpickledROM' on <module 'ravenframework.utils.InputData' from '/Users/bryaja/projects/raven/ravenframework/utils/InputData.py'>

This behavior was observed on both my local computer and the Bitterroot cluster. I believe this error stems from the same issue mentioned in #2482.

Steps to Reproduce

The provided minimum example demonstrates a similar error. Removing the <internalParallel> node from the example results in the model running successfully.

Expected Behavior

No error thrown

Screenshots and Input Files

No response

OS

MacOS

OS Version

15.4.1

Dependency Manager

CONDA

For Change Control Board: Issue Review

  • Is it tagged with a type: defect or task?
  • Is it tagged with a priority: critical, normal or minor?
  • If it will impact requirements or requirements tests, is it tagged with requirements?
  • If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
  • Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure

  • If the issue is a defect, is the defect fixed?
  • If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
  • If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
  • If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
  • If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions