neqsim-dynamic-process-preparation

Dynamic Process Preparation

Use this skill when an agent must prepare a NeqSim ProcessSystem or multi-area ProcessModel for dynamic calculations. It focuses on model-readiness checks, mechanical-design handoff, equipment holdup and volume initialization, and the transient run sequence.

When to Use

• When a user asks to turn a steady-state NeqSim process into a dynamic-ready process.
• When a ProcessSystem or ProcessModel needs equipment volumes, holdups, or initial liquid levels before transient simulation.
• When an agent needs a documented workflow for run(), storeInitialState(), setTimeStep(...), and runTransient().
• When mechanical design should be estimated with NeqSim classes before dynamic calculations.

Inputs

• process_name: public process or model name used in reports.
• process_kind: ProcessSystem or ProcessModel.
• equipment: dynamic candidate equipment records with name, equipment_type, optional length_m, diameter_m, liquid_level_fraction, and requires_mechanical_design.
• time_step_seconds: proposed transient time step.
• total_time_seconds: optional total transient duration.
• initialization_basis: steady-state case, public design point, or synthetic example basis.

Outputs

• dynamic_ready: boolean indicator for whether the supplied preparation metadata passes basic checks.
• equipment_actions: per-equipment actions such as enable dynamic mode, estimate mechanical design, set vessel geometry, and set initial level.
• estimated_volumes_m3: geometric cylindrical volume estimates for public readiness checks when dimensions are supplied.
• neqsim_sequence: NeqSim API sequence for initialization and transient execution.
• warnings: missing information or setup gaps that should be fixed before transient calculations.

Engineering Method

The Python class DynamicProcessPreparationModel is a public planning and validation helper. It does not run NeqSim itself. It checks that a dynamic-ready NeqSim workflow has the minimum metadata needed to initialize dynamic equipment and points the user to the NeqSim APIs that should do the real work.