When ARES executes a scenario, the following set of files is generated:
SCENARIO.xml file which contains the scenario in XML format. This file contains the scenario structure, configuration, specification and rules built from the user's scenario definition. Although this XML can be edited, it is not recommended as XML is a hard to manipulate format.
magnitudes.csv is a comma-separated values file that consists in a table that reflects the magnitude of each bacterial lineage type defined in current scenario.
SCENARIO.csv file is a comma-separated values file that represents the
count of each element(membranes and objects) in each iteration. Thus, it
contains as many rows as the number or iterations set on running the scenario's
The first row defines the element that is being tracked with the following notation ELEMENT(HIERARCHY). An example would be a column labeled as "A1(B1-H1-P1-ECO)" where we track the count of A1 substance located inside B1 bacterial lineage cells of H1 host that inhabits P1 environment of scenario named ECO.
The second row defines the initial configuration of the scenario previous to its execution.
Following rows represent the scenario configuration in each iteration steps.
A set of csv files derived from SCENARIO.csv which groups element counts by
While SCENARIO.csv tracks the counts of the whole scenario, which can be hard to manipulate specially in complex scenarios, we can also find subsets representing environment level (P-like.csv), reservoir level (RS-like.csv), host level (H-like.csv) and bacterial lineage level (B-like.csv) files.
Marcelino Campos, Carlos Llorens, José M. Sempere, Ricardo Futami, Irene Rodriguez, Purificación Carrasco, Rafael Capilla, Amparo Latorre, Teresa M. Coque, Andres Moya and Fernando Baquero. 2015. A membrane computing simulator of trans-hierarchical antibiotic resistance evolution dynamics in nested ecological compartments (ARES). Biology Direct 2015, 10:41.