pyDAC 3.1.0

pyDAC can now simulate beds other than a packed bed: register your own bed architecture at
run time, as you already can for an isotherm or a kinetic law. This release also fixes a set
of input, plotting and terminal issues. The packed bed is unchanged: its computed results
(trajectories, KPIs, NSGA-II fronts) are bit-identical to 3.0.1.

New

• pydac.register_bed_architecture(name, entry) registers a bed architecture (a monolith, a
  structured packing, ...). Its BedArchitectureEntry gives the design, the structure, and
  the pressure-drop, dispersion and thermal closures of the bed. pyDAC checks every value the
  closures return before the column uses it. The user guide shows a complete registration and
  what each closure has to give for a monolith:
  Extending pyDAC: a bed architecture.
• The saved simulation context (schema 3) keeps the two wall coefficients apart: the
  bed-side coefficient h_w and the lumped 1D coefficient. Contexts saved by 3.0.x read in
  the new rows.

Fixed

• external_htc_W_m2K = 0 is accepted: an adiabatic outer wall.
• The outlet species figures of a step run show the stream that leaves the outlet, the
  value the KPIs use, instead of the last cell center.
• Terminal settings: an object value (--set 'sorbent={"density_kg_m3": 800}') changes only
  the fields it gives; species keys match whatever their case; an empty block such as
  grid={} is refused instead of passing silently (a block replaced as one may still be
  empty).
• NSGA-II refuses a cycle without a desorption step, and warns when a campaign starts
  without any product constraint.
• An older frozen case written before one of its fields existed is refused with how to
  bring it up to date.
• Terminal messages print a path inside the working folder relative to it; a path
  elsewhere stays absolute.
• One qualification lock for Linux and Windows; CI runs on Node 24 actions.

The full list is in the
changelog.

Upgrade

python -m pip install --upgrade pydac3
pydac get-started NEW_FOLDER

The tutorials changed (wording in 01 and 05, printed paths in all seven): get a fresh copy
with pydac get-started into a new folder. Runs written by 3.0.x can be read and reported with 3.1.0; as for any version
change, a run written by 3.0.x is not continued by 3.1.0.