- ver. ≥
0.4.23
:
cadCAD.configuration.Experiment
(Alpha) is in development and needed to be released to support the implementation of web applications and proprietary feature extensions. It is intended to represent a unique identifier of an experiment of one or more configured System Models. For this reason,append_configs
is a method ofcadCAD.configuration.Experiment
. As of now it does not support multi - system model simulation because configurations are still appended globally despiteappend_config
being a method of Experiment.
- ver. ≥
0.4.22
:from cadCAD.configuration import Experiment exp = Experiment() exp.append_configs(...)
- ver.
0.3.1
: Deprecatedfrom cadCAD.configuration import append_configs append_configs(...)
- Bug Fix: Multiprocessing error for Windows
- Local Execution Mode (Default): Implicit parallelization of Monte-Carlo / Stochastic simulations (Automatically
selects Multi-Threaded Mode if simulations are configured for more than a single run)
- Backwards Compatibility:
cadCAD.engine.ExecutionMode
accepts legacy execution modes from ver.0.3.1
- Backwards Compatibility:
-
ver. ≥
0.4.22
:from cadCAD.engine import ExecutionMode, ExecutionContext exec_mode = ExecutionMode() local_ctx = ExecutionContext(context=exec_mode.local_mode)
-
ver.
0.3.1
:Multi-Threaded:
from cadCAD.engine import ExecutionMode, ExecutionContext exec_mode = ExecutionMode() single_ctx = ExecutionContext(context=exec_mode.multi_proc)
Single-Thread:
from cadCAD.engine import ExecutionMode, ExecutionContext exec_mode = ExecutionMode() multi_ctx = ExecutionContext(context=exec_mode.single_proc)
- Single Result Dataset
as a 2 dimensional
list
- Returns a single dataset instead of multiple datasets per Monte Carlo simulation as in
0.3.1
:- New System Metrics as dataset attributes:
- Simulation (Alpha) is a unique identifier being developed to represent Experiments as stated above and
will be renamed accordingly
- Subset is a unique identifier of Monte-Carlo simulations produced by parameter sweeps
- Simulation (Alpha) is a unique identifier being developed to represent Experiments as stated above and
will be renamed accordingly
- New System Metrics as dataset attributes:
- Note: Returning a single dataset was originally specified during the project’s inception instead of multiple per simulation
- Returns a single dataset instead of multiple datasets per Monte Carlo simulation as in
-
ver. ≥
0.4.22
:import pandas as pd from tabulate import tabulate from cadCAD.engine import ExecutionMode, ExecutionContext, Executor import system_model_A, system_model_B from cadCAD import configs exec_mode = ExecutionMode() local_ctx = ExecutionContext(context=exec_mode.local_mode) simulation = Executor(exec_context=local_ctx, configs=configs) raw_result, sys_model, _ = simulation.execute() result = pd.DataFrame(raw_result) print(tabulate(result, headers='keys', tablefmt='psql'))
Results:
+----+------------+-----------+----+---------------------+------------+--------+-----+---------+----------+ | | s1 | s2 | s3 | timestamp | simulation | subset | run | substep | timestep | |----+------------+-----------+----+---------------------+------------+--------+-----+---------+----------| | 0 | 0.0 | 0.0 | 1 | 2018-10-01 15:16:24 | 0 | 0 | 1 | 0 | 0 | | 1 | 1.0 | 4 | 5 | 2018-10-01 15:16:25 | 0 | 0 | 1 | 1 | 1 | | 2 | 2.0 | 6 | 5 | 2018-10-01 15:16:25 | 0 | 0 | 1 | 2 | 1 | | 3 | 3.0 | [ 30 300] | 5 | 2018-10-01 15:16:25 | 0 | 0 | 1 | 3 | 1 | | 4 | 0 | 0 | 1 | 2018-10-01 15:16:24 | 1 | 0 | 1 | 0 | 0 | | 5 | 1 | 0 | 5 | 2018-10-01 15:16:25 | 1 | 0 | 1 | 1 | 1 | | 6 | a | 0 | 5 | 2018-10-01 15:16:25 | 1 | 0 | 1 | 2 | 1 | | 7 | ['c', 'd'] | [ 30 300] | 5 | 2018-10-01 15:16:25 | 1 | 0 | 1 | 3 | 1 | +----+------------+-----------+----+---------------------+------------+--------+-----+---------+----------+
-
ver.
0.3.1
:import pandas as pd from tabulate import tabulate from cadCAD.engine import ExecutionMode, ExecutionContext, Executor import system_model_A, system_model_B from cadCAD import configs exec_mode = ExecutionMode() multi_ctx = ExecutionContext(context=exec_mode.multi_proc) simulation = Executor(exec_context=multi_ctx, configs=configs) i = 0 config_names = ['sys_model_A', 'sys_model_B'] for raw_result, _ in simulation.execute(): result = pd.DataFrame(raw_result) print() print(f"{config_names[i]} Result: System Events DataFrame:") print(tabulate(result, headers='keys', tablefmt='psql')) print() i += 1
Results:
+----+------------+-----------+----+---------------------+-----+---------+----------+ | | s1 | s2 | s3 | timestamp | run | substep | timestep | |----+------------+-----------+----+---------------------+-----+---------+----------| | 0 | 0.0 | 0.0 | 1 | 2018-10-01 15:16:24 | 1 | 0 | 0 | | 1 | 1.0 | 4 | 5 | 2018-10-01 15:16:25 | 1 | 1 | 1 | | 2 | 2.0 | 6 | 5 | 2018-10-01 15:16:25 | 1 | 2 | 1 | | 3 | 3.0 | [ 30 300] | 5 | 2018-10-01 15:16:25 | 1 | 3 | 1 | | 4 | 0 | 0 | 1 | 2018-10-01 15:16:24 | 1 | 0 | 0 | | 5 | 1 | 0 | 5 | 2018-10-01 15:16:25 | 1 | 1 | 1 | | 6 | a | 0 | 5 | 2018-10-01 15:16:25 | 1 | 2 | 1 | | 7 | ['c', 'd'] | [ 30 300] | 5 | 2018-10-01 15:16:25 | 1 | 3 | 1 | +----+------------+-----------+----+---------------------+-----+---------+----------+
-
Flattened Configuration List: The
cadCAD.configs
(System Model Configuration)list
has been temporarily flattened to contain single runcadCAD.configuration.Configuration
objects to both fault-tolerant simulation and elastic workloads. This functionality will be restored in a subsequent release by a class that returnscadCAD.configs
's original representation in ver.0.3.1
.- The conversion utilities have been provided to restore its original representation of configurations with
runs >= 1
- System Configuration Conversions
- Configuration as List of Configuration Objects (as in ver.
0.3.1
) - New: System Configuration as a Pandas DataFrame
- New: System Configuration as List of Dictionaries
- Configuration as List of Configuration Objects (as in ver.
- System Configuration Conversions
- The conversion utilities have been provided to restore its original representation of configurations with
runs >= 1
-
Notes:
configs
is temporarily returned in a flattened format and reformatted into its intended formatConfiguration
objects at0x10790e470
and0x1143dd630
are reconstituted into objects at0x10790e7b8
and0x116268908
respectively.
-
ver. ≥
0.4.22
:from pprint import pprint from documentation.examples import sys_model_A, sys_model_B from cadCAD.configuration.utils import configs_as_objs, configs_as_dataframe, configs_as_dicts from cadCAD import configs flattened_configs = configs print('Flattened Format: Temporary') pprint(flattened_configs) print() print('Intended Format:') intended_configs = configs_as_objs(flattened_configs) pprint(intended_configs) print()
Result:
Flattened Format: Temporary [<cadCAD.configuration.Configuration object at 0x10790e470>, <cadCAD.configuration.Configuration object at 0x10790e7b8>, <cadCAD.configuration.Configuration object at 0x1143dd630>, <cadCAD.configuration.Configuration object at 0x116268908>] Intended Format: [<cadCAD.configuration.Configuration object at 0x10790e7b8>, <cadCAD.configuration.Configuration object at 0x116268908>]
- Enables the development of feature enhancements that involve the use of additional parameters without requiring users
to modify their update parameters spaces when upgrading to newer versions. For this reason state / policy update
examples in documentation include an additional
**kwargs
parameter.
-
ver. ≥
0.4.22
:def state_update(_params, substep, sH, s, _input, **kwargs): ... return 'state_variable_name', new_value def policy(_params, substep, sH, s, **kwargs): ... return {'signal_1': value_1, ..., 'signal_N': value_N}
-
ver.
0.3.1
:def state_update(_params, substep, sH, s, _input): ... return 'state_variable_name', new_value def policy(_params, substep, sH, s): ... return {'signal_1': value_1, ..., 'signal_N': value_N}
- Packaging: Add Nix derivation and shell for local development and distribution of cadCAD package using Nix. Nix is a powerful package manager for Linux and other Unix systems that makes package management reliable and reproducible, allowing you to share your development and build environments across different machines.