run_phase3_multiple {ERPM}R Documentation

Phase 3 wrapper for multiple observation

Description

Phase 3 wrapper for multiple observation

Usage

run_phase3_multiple(
  partitions,
  estimates.phase2,
  z.obs,
  presence.tables,
  nodes,
  effects,
  objects,
  burnin,
  thining,
  a.scaling,
  length.p3,
  neighborhood,
  numgroups.allowed,
  numgroups.simulated,
  sizes.allowed,
  sizes.simulated,
  fixed.estimates,
  parallel = FALSE,
  cpus = 1,
  verbose = FALSE
)

Arguments

partitions

observed partitions

estimates.phase2

vector containing parameter values after phase 2

z.obs

observed statistics

presence.tables

data frame to indicate which times nodes are present in the partition

nodes

node set (data frame)

effects

effects/sufficient statistics (list with a vector "names", and a vector "objects")

objects

objects used for statistics calculation (list with a vector "name", and a vector "object")

burnin

integer for the number of burn-in steps before sampling

thining

integer for the number of thining steps between sampling

a.scaling

multiplicative factor for out-of-diagonal elements of the covariance matrix

length.p3

number of samples in phase 3

neighborhood

vector for the probability of choosing a particular transition in the chain

numgroups.allowed

vector containing the number of groups allowed in the partition (now, it only works with vectors like num_min:num_max)

numgroups.simulated

vector containing the number of groups simulated

sizes.allowed

vector of group sizes allowed in sampling (now, it only works for vectors like size_min:size_max)

sizes.simulated

vector of group sizes allowed in the Markov chain but not necessraily sampled (now, it only works for vectors like size_min:size_max)

fixed.estimates

if some parameters are fixed, list with as many elements as effects, these elements equal a fixed value if needed, or NULL if they should be estimated

parallel

boolean to indicate whether the code should be run in parallel

cpus

number of cpus if parallel = TRUE

verbose

logical: should intermediate results during the estimation be printed or not? Defaults to FALSE.

Value

a list


[Package ERPM version 0.2.0 Index]