Multiple questions regarding logog capabilities

15 views
Skip to first unread message

John McGinley

unread,
Oct 1, 2018, 4:42:21 PM10/1/18
to Logog
I am working on the development of an agent-based simulation system.  I have some pretty specific requirements regarding logging/data output and am evaluating logog for this purpose.  I'll just list them off below in a numbered list so that answers can refer to the number.  The main question for each is: Can logog do this?


1.  I need to assign different categories of output data to different outputs.  For example:

a.      I need “debugging” data to a file (ex: exp1_debug.txt).  This data would be logged each time a particular function is called, line of code is hit, etc.  Each line of this would have stuff like system time, simulation time, code line, and  whatever info (variable values, etc)


b.      I need “data” of one type to go to another file (ex: exp1_agent_locations.csv).  This data would be generated at each time step and would include stuff like sim time, time step, agent states (location, direction, velocity, other) – one line per active agent per time step.


c.      I need data of another type to go to a different file (ex: exp1_node_capacities.csv) .  Also generated at each time step and would include stuff about the environment (vs. agents) like sim time, time step, navigation node states (capacity, occupancy, number of visits, number of exits, other) – one line per environment feature per time step.


2.      I need to be able to “toggle” at run time (during execution)a particular state.  Sometimes we need to generate a “verbose” output file that contains even more data than described above.  These files grow ridiculously large in a very short time, so it’s not something that we would activate at the beginning of a run.  We would activate/deactivate with a key-combination.


3.      I would like to (I could find a workaround if logog can’t do this) be able to define the logging levels at launch time (beginning of execution) using a command parameter, init file, etc.  (We use input files to define the parameters for the simulations.  I would like to be able to define the logging levels within the input files vs. at compile time.)


4.      I’m trying very hard to not have global file variables (any hints on how to avoid this with logog?)



Thanks,

John

Reply all
Reply to author
Forward
0 new messages