Is a LANDIS-II replicate already complete for these inputs?

TRUE when Landis-log.txt reports a completed run and log/input_hash.json records the input hash of dep_files et al. Besides the current landis_input_hash(), the hash landisutils 0.0.149 and earlier would have written is accepted, sorted in this process's locale or under C.UTF-8 (ICU). A replicate finished by an earlier version is therefore not re-simulated after an upgrade, whichever of those locales wrote it.

Usage

landis_rep_is_current(
  rep_dir,
  dep_files,
  base_seed,
  rep_index,
  scenario_file,
  force = FALSE
)

Arguments

rep_dir

Character(1). The replicate directory.

dep_files

Character. The dependency files staged into the replicate.

base_seed

Integer. The base random seed.

rep_index

Integer. The replicate index.

scenario_file

Character(1). The scenario file name.

force

Logical(1). TRUE never counts a replicate as current.

Value

Logical(1).

Details

Up to 0.0.168, landis_dep_files() also staged other scenarios' files, and the hash covered them. When dep_files carries those files as its "foreign" attribute, as landis_dep_files() returns it, that hash is accepted too. It is rebuilt from dep_files and the copies in rep_dir of files named in the attribute, with the MD5 of the copy rather than of the source, each keyed by a path it could have been staged from: one in the attribute, or the same name in another directory beside the replicate's scenario directory. A change to dep_files still makes the replicate stale; a change to another scenario's file, which this replicate does not read, does not. A copy whose name no file in the attribute has is not considered.