Reference¶
-
class
Reference¶
Properties¶
Reference values¶
Design note: intention is that all objects containing an instance of this class also is contained in this object, think of it as pairs.
Question is if more than one instance of each class should be able to share a Reference object.
Right now it is possible to ‘hack’ the construction by creating a Reference object, and for example a TimeGrid.
Then setting the Reference in the TimeGrid.
Afterwards it is possible to create a new TimeGrid and set the already created Reference in the new TimeGrid.
The firstly created TimeGrid now has a Reference object in it with a TimeGrid object in it which is not pointing to itself.
The ‘pair’ structure is then broken.
Twofixes are availible: one seperating the Reference to a copy of itself
(new pointer) and using the copy for the old TimeGrid or save both
TimeGrid objects in the same Reference object.
-
TRef¶
Reference temperature
-
nRef¶
Reference density
-
nueeRef¶
Reference collision frequency
-
deltaRef¶
Reference velocity over speed of light
-
lnLambdaRef¶
Reference coulumb logarithm
Paired Objects¶
-
physicalParams¶
PhysicalParams object which also contains a pointer to this class.
-
momentumGrid¶
MomentumGrid object which also contains a pointer to this class.
-
timeGrid¶
TimeGrid object which also contains a pointer to this class.
Functions¶
-
Reference(TRef, nRef)
Constructor
-
setPhysicalParams(this, phP)¶
Set the PhysicalParams to passed variable
-
setMomentumGrid(this, mg)¶
Set the MomentumGrid to passed variable
-
setTimeGrid(this, tg)¶
Set the TimeGrid to passed variable
-
updateReferenceVals(this, TRef, nRef)¶
Update TRef, nRef and all relevant attributes in TimeGrid, MomentumGrid and PhysicalParams objects in this class.