Note that there are some explanatory texts on larger screens.

plurals
  1. POPreferred (or recommended) way to store large amounts of simulation configurations, runs values and final results
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. CO"database" can have quite a few different meanings... I think the questions here are: 1/ what your data looks like (structures, types etc) 2/ how do you plan on using your data (queries, concurrent access, etc) 3/ are your data critical ? (what happens if they are lost, corrupt, whatever ?) 4/ and of course how much data you will have...
      singulars
    2. CO1. Currently I have simple simulation txt log files, which then I parse and create a simple collections e.g. mobile terminal position at time x is the array (Terminals x TimeSlots) of tuples (x,y). Then usually I save those parsed data to multiple csv files. But in designed app I am considering to pack this data in some classes, which then can simplify the development of visualization and gui part.
      singulars
    3. CO2. There will not be any concurrent access, I suppose that only one person will be using the same data in the same time. My first, draft vision is simple select simulation, show result, play mobility viz etc. but I want to make it flexible for further extensions. 3. I don't think so 4. from tens of MB to some (I hope no more than 3 ;)) GB per simulation run.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload