JAS-mine maintains and develops the JAS simulation platform, a discrete-event tool-kit for agent-based and dynamic microsimulation modelling. This repository contains the core libraries. See www.jas-mine.net for more details.
2
stars
5
forks
source link
MultiRun copies input.mv.db but accesses only original, global file #33
When running two multiruns simultaneously (via LABSim) both runs successfully copy all files including input.mv.db to a unique [yyyyMMddHHmmss]/input folder. After initialisation is completed (27s recorded below), the multirun appears to still be accessing and locking the input.mv.db file at the root working directory level, and not allowing other runs to access this.
Is this a necessary part of the multirun, or is it possible to direct a single run to use its own input database (or not locking the database) without interfering with other runs?
When running two multiruns simultaneously (via LABSim) both runs successfully copy all files including
input.mv.db
to a unique[yyyyMMddHHmmss]/input
folder. After initialisation is completed (27s recorded below), the multirun appears to still be accessing and locking theinput.mv.db
file at the root working directory level, and not allowing other runs to access this.Is this a necessary part of the multirun, or is it possible to direct a single run to use its own input database (or not locking the database) without interfering with other runs?