1. 10 Aug, 2018 1 commit
    • Stefan Schuhbaeck's avatar
      json v0.4: add fixedSeed and simulationSeed to AttributesSimulation · 82ba9393
      Stefan Schuhbaeck authored
      * add new seed handling: By default new scenario files will be created
        with a random seed, which is written in the attribute fixedSeed.
        If the Boolean switch useFixedSeed  is set, this defined seed will
        be used within one simulation. At the start of each simulation this
        seed, or if useFixedSeed is false a newly generated one, will be used
        and persisted in the attribute simulationSeed. All generated data
        of this simulation will be written to the defined output directory
        with a copy of the current scenario file. All data generated in this
        simulation run can be reproduced with specified simulationSeed.
      * new features for VaderConsole(migrate): The migrate subcommand will
        now accept a list of files or Directories (or a mix of them) to
        perform a migration or a revert. If a path is specified the
        default behavior will only migrate the selected directory without
        traversing to the directory tree. If the --recursive or -r flag is
        set, the hole sub tree of all given directories will be converted.
        Directories or directory trees will be ignored if the directory
        contains one of the following marker files:
      * remove hard coded sc  enario files encoded as strings to allow
        testResource migration with the VadereConsole
      * ignore scenario.legacy files within testResources
      * add test for MigrationAssistant v0.3 to v0.4
  2. 08 Aug, 2018 3 commits
    • Stefan Schuhbaeck's avatar
      add simulation seed and fixed seed to scenario file. · 35205f58
      Stefan Schuhbaeck authored
      * Add UseFixedSeed (bool switch) and fixedSeed Attribute values
        This allows to rerun the simulation with different but fixed seeds
        for random numbers.
      * Add simulationSeed to save currently used seed while simulation is
        running. This is useful to determine the seed used for processor
        outputs in the output directory.
      * Add Test for new version and refactor code duplicates
      * Change Hash calculation to exclude UseFixedSeed, fixedSeed and
        simulationSeed to highlight (green) output to selected scenario
        within the gui.
    • Stefan Schuhbaeck's avatar
      add test data and new version files · 6f4d4ae2
      Stefan Schuhbaeck authored
    • Stefan Schuhbaeck's avatar
      test · 0a0584d8
      Stefan Schuhbaeck authored
  3. 03 Aug, 2018 5 commits
    • Stefan Schuhbaeck's avatar
    • Marion Goedel's avatar
    • Marion Goedel's avatar
      Added a new outputprocessor, namely "NumberOverlapsProcessor" that is... · 6b8a40a2
      Marion Goedel authored
      Added a new outputprocessor, namely "NumberOverlapsProcessor" that is dependent of the PedestrianOverlapProcessor. It saves the number of overlaps that occurred during the simulation run.
    • Stefan Schuhbaeck's avatar
      move migration logic back to MigrationAssistant, add MigrationUtil · 8375f258
      Stefan Schuhbaeck authored
      Features (MigrationUtil):
      * create new Transformation and Identity files: This will use the
      current identity    Transformation as starting point for the new
      version. The new version string is automatically included in the new
      files. The files will be created based   on the defined naming
      convention and saved in VadereSimulator/resources
      * automate scenario migration without gui: The MigrationUtil will
      migrate   all scenario files within the specified directory and all
      child directories.
      To exclude specific sub-trees or only specific
      directories the igonoreDirs List can be expanded.
        To exclude sub-trees or specific directories without code change add
        one of the following marker-files to the directory.
        * DO_NOT_MIGRATE or .DO_NOT_MIGRATE: Ignore current directory but
          continue with existing child directories.
        * DO_NOT_MIGRATE_TREE or .DO_NOT_MIGRATE_TREE: Ignore the directories
          and the complete sub-tree.
        Use the marker files from the Tools directory. These files have a
        comment to explain for what they are used for.
        The content of the file is not used, only the file name is needed.
        These files must be added to the git cache to work.
       * automate migration revert: This will use the revert function of the
         MigrationAssistant to revert a migration if the <file-name>.legacy
         files still exist. For this to work the legacy file must be in the
         same directory as the scenario-file
    • Stefan Schuhbaeck's avatar
      add migration revert option to console, move migration logic from console code · bbe6bc97
      Stefan Schuhbaeck authored
      * add helper methods to crate backup files with suffix
      * add migration revert function to MigrationAssistant
      * move migration logic from VadereConsole back to MigrationAssistant
      * add Test for MigrationSubCommand
  4. 02 Aug, 2018 5 commits
  5. 01 Aug, 2018 10 commits
  6. 30 Jul, 2018 2 commits
  7. 27 Jul, 2018 3 commits
  8. 25 Jul, 2018 6 commits
  9. 24 Jul, 2018 5 commits