| 1 |
+ Updated STC directory to most recent Volute updates (AR) |
| 2 |
+ Process through xslt scripts: |
| 3 |
NOTE: had some issues with web schema (Namespace), downloaded to xsd directory and redirected (as file: URL) in build.properties. |
| 4 |
|
| 5 |
Coords: |
| 6 |
xmi2vo-dml = OK |
| 7 |
validate = FAIL |
| 8 |
* Target role of subsets constraint on 'domain.pixel.PixelFrame' with vodml-ref stc2_coordinates:coordsystem.CoordFrame.coordSpace can not be found |
| 9 |
|
| 10 |
Meas: |
| 11 |
xmi2vo-dml = OK |
| 12 |
validate = FAIL |
| 13 |
* Many of: domain.redshift.RedshiftCoordMeasure has more than one extends relation. |
| 14 |
.RedshiftCoordMeasure |
| 15 |
.RedshiftSimpleCoordMeasure |
| 16 |
.Position |
| 17 |
.Velocity |
| 18 |
.SimplePosition |
| 19 |
.SimplePosition1D |
| 20 |
.SimplePosition2D |
| 21 |
.SimplePosition3D |
| 22 |
.SimpleVelocity |
| 23 |
.SimpleVelocity1D |
| 24 |
.SimpleVelocity2D |
| 25 |
.SimpleVelocity3D |
| 26 |
.SpectralCoordMeasure |
| 27 |
.SpectralSimpleCoordMeasure |
| 28 |
.TimeMeasure |
| 29 |
.TimeSimpleMeasure |
| 30 |
|
| 31 |
* Several constraint targets not found |
| 32 |
o change reference to local/new coords model corrects all but 2 |
| 33 |
|
| 34 |
* Target datatype of subsets constraint on 'domain.space.SimplePosition' with vodml-ref stc2_coordinates:domain.space.SpatialCoord can not be found |
| 35 |
* Target datatype of subsets constraint on 'domain.space.SimpleVelocity' with vodml-ref stc2_coordinates:domain.space.SpatialCoord can not be found |
| 36 |
o object is 'SpatialCoordValue' in current model |
| 37 |
|
| 38 |
|
| 39 |
MCD Modelio Model(s) |
| 40 |
+ coords_V2.0: 01/12/2018 = my equivalent to current AR model |
| 41 |
+ coords_V2.0_alt: 9/25/2017 = my alternate modeling, prior to TS work; OBSOLETE |
| 42 |
+ coords_V2.0_alt2: 10/25/2017 = most migrated from TS work; includes some shortcuts, but does NOT include Frame relation change. |
| 43 |
|
| 44 |
+ meas_V2.0: 01/12/2018 = my equivalent to current AR model |
| 45 |
+ meas_V2.0_alt: 10/12/2017 = no 'shortcuts'; updated subset stereotype content |
| 46 |
+ meas_V2.0_alt2: 10/25/2017 = includes 'shortcuts' for spatial and temporal; updated subset content |
| 47 |
|
| 48 |
|
| 49 |
MCD Task List: |
| 50 |
o double check subset specs in Modelio.. so they process through scripts [DONE] |
| 51 |
o update 'base' Modelio models to current AR model equivalents [DONE] |
| 52 |
o process through xslt scripts [DONE] |
| 53 |
o remove 'alt' versions from volute |
| 54 |
o update example serializations |
| 55 |
o make change request list: from review of serializations and alt2 migrations (from TS work) |
| 56 |
|
| 57 |
+ Review of AR model vs MCD equivalent model |
| 58 |
* AR: STC2.0ModelCoords.xmi r4612 via diagrams |
| 59 |
* MCD: stc_coords_v2.0_uml2p4p1.xmi 20170112 |
| 60 |
|
| 61 |
+ Review of Coords Model: |
| 62 |
coordsystem: |
| 63 |
+ CoordSpace.coordAxis[] .. AR has [1..3]; MCD has [1..*] |
| 64 |
|
| 65 |
coords: |
| 66 |
+ MCD has package named 'coordz'.. Modelio issue with package and model of same name?.. |
| 67 |
NOTE: would like to remove the coords and coordsystem packages.. bring objects to base level. |
| 68 |
|
| 69 |
domain.generic: |
| 70 |
+ MCD does not constrain axis multiplicity to 1. |
| 71 |
|
| 72 |
domain.pixel: |
| 73 |
AR TODO: PixelFrame has composition to PixelSpace.. (with subset).. this relation was removed in this revision |
| 74 |
AR TODO: PixelCoordinate*D => can not rename attribute on subset (pixCmpt == MultiCoordValue.cmpt) |
| 75 |
|
| 76 |
domain.polarization: |
| 77 |
+ cval dtype deltas.. Modelio cannot extend Enum, so layout is different |
| 78 |
AR TODO: remove composite PolarizationCoord object |
| 79 |
|
| 80 |
domain.redshift: |
| 81 |
AR TODO: remove composite RedshiftCoord object |
| 82 |
|
| 83 |
domain.spatial: |
| 84 |
+ AR has specialized Frames ( GalacticFrame, EclipticFrame, EquatorialFrame ) |
| 85 |
with specialized StdRefFrame enums corresponding to these. |
| 86 |
( leans StdRefFrame toward being a semanticConcept rather than an enum.. ) |
| 87 |
AR TODO: remove epoch from Frame (redundant with that in spatial CoordValue types ) |
| 88 |
|
| 89 |
domain.spectral: |
| 90 |
AR TODO: remove composite spectralCoord object |
| 91 |
|
| 92 |
domain.time: |
| 93 |
AR TODO: remove composite TimeStamp object; revert TimeStampValue to TimeStamp |
| 94 |
|
| 95 |
|
| 96 |
Measurement Model: |
| 97 |
AR: better if doc/diagram/meas only has 'measurement' model diagrams.. remove proxy diagrams of coord objects. |
| 98 |
AR: We had discussed creating a parent 'CoordMeasure' type from which we extend |
| 99 |
a) Polarization |
| 100 |
b) the currrent CoordMeasure.. renamed == parent to all the value+error measures |
| 101 |
c) potentially a 'Virtual' type which would handle functionally generated values |
| 102 |
|
| 103 |
uncertainty |
| 104 |
AR TODO: migrate CoordMeasure,[Resolution,Error] to base package |
| 105 |
<CoordMeasure> |
| 106 |
MCD TODO: add 'Resolution' [DEFER] |
| 107 |
|
| 108 |
stcTypes |
| 109 |
Contains "Uncertainty" class hierarchy.. |
| 110 |
I have at base level, if anything, this should be the 'uncertainty' package. |
| 111 |
|
| 112 |
domain.generic:OK |
| 113 |
|
| 114 |
domain.pixel: OK |
| 115 |
+ MCD - there is no pixel 'measure' |
| 116 |
|
| 117 |
domain.polarization: |
| 118 |
AR TODO: remove PolarizationCM and PolSimpleCoord.. PolarizatonCoord composite type to be removed |
| 119 |
PolCoord -> Polarization |
| 120 |
|
| 121 |
domain.redshift: |
| 122 |
AR TODO: remove RedshiftCM and RedshiftSimpleCoordMeasure.. RedshiftCoord composite type to be removed |
| 123 |
|
| 124 |
domain.spatial: |
| 125 |
AR TODO: PositionCM -> Position |
| 126 |
SimplePosition -> SkyPosition (The shortcuts are 'specific'; I'd like the name to be also.) |
| 127 |
SkyPosition.coord::SpatialCoord -> SpaceCoord (does not match coords model type) |
| 128 |
|
| 129 |
domain.spectral: |
| 130 |
AR TODO: remove SpectralCM and SpectralSimpleCoordMeasure.. SpectralCoord composite type to be removed |
| 131 |
|
| 132 |
domain.time: |
| 133 |
AR TODO: TimeCM -> TimeMeasure (or TimeCoordMeasure to match spectral, redshift, generic domains) |
| 134 |
TimeMeasure + TimeSimpleMeasure |
| 135 |
o I have "GenTimeMeasure" with GenTimeMeasure.coord::TimeOffset |
| 136 |
"StdTimeMeasure" with StdTimeMeasure.coord::TimeStamp << JD,MJD,ISOtime |
| 137 |
|
| 138 |
|
| 139 |
COMMENTS |
| 140 |
I'd like to move the time domain to the representation we have migrated to during the TS serializations. |
| 141 |
Coords: |
| 142 |
<TimeStamp> == 'specialized' time types (JD,MJD,ISOtime) extend 'BasicCoordValue' like 'SpaceCoord' does. |
| 143 |
<JDTime> == extension of TimeStamp.. cval::RealQuantity |
| 144 |
JD,MJD == extensions of JDTime |
| 145 |
ISOtime == extension of TimeStamp.. cval::datetime |
| 146 |
NOTE: removes need for DateTimeQuantity |
| 147 |
|
| 148 |
Meas: |
| 149 |
<TimeMeasure> == head of Time Measurement types |
| 150 |
GenTimeMeasure == subset coord::TimeOffset << serves TimeOffset |
| 151 |
StdTimeMeasure == subset coord::TimeStamp << serves JD, MJD, ISO which are very specialized/defined |
Parent Directory
| 
Revision Log