Hi,
You are correct.
You need to build a so called HismoModelHistory that will be formed by
versions corresponding to your snapshot models. Take a look at
MooseSampleData>>initialize for an example of how to initialize this.
Doru
On Sun, Jun 23, 2013 at 6:17 AM, badja <alan.mcnamara(a)badja.com> wrote:
Doru,
I'm starting to understand.
"Let's take an example. Imagine you have a history of 5 models (instances
of
MooseModel) holding FAMIX objects."
Ah ha. I've been looking at a history and all the versions and snapshots
being within a /*single*/ MooseModel. But you are suggesting I should have
a MooseModel for my data at each point in time, then model the time
relationships between them using the Hismo history classes.
Can I confirm that then the HismoAbtractVersion (as subclassed) and
HismoAbstractHistory (as subclassed) instances therefore sit *outside* the
MooseModel instances.
The MooseModel instances (in your example 5 instances) would consist of
FAMIX class instances, and would not include any Hismo class instances.
The
history instances (e.g. HismoClassHistory) would point to version instances
(HismoClassVersion) which in turn would point to FAMIX class instances
(FAMIXClass) - and only these FAMIX instances will be in the (5)
MooseModels.
Is this correct?
--
View this message in context:
http://forum.world.st/What-is-the-relevence-of-referenceVersion-in-Hismo-tp…
Sent from the Moose mailing list archive at
Nabble.com.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Every thing has its own flow"