Final Projection Review Result - Revision history

Mei at 21:32, 19 March 2018

2018-03-19T21:32:03Z

Mei: /* For CVM-S4.26 */

2018-03-19T21:17:32Z

For CVM-S4.26

Mei: /* For CCA06 */

2018-03-19T21:17:19Z

For CCA06

Mei: /* For CCA06 */

2018-03-19T21:14:53Z

For CCA06

Mei at 21:10, 19 March 2018

2018-03-19T21:10:54Z

Mei: /* Related Entries */

2018-03-19T21:09:25Z

Related Entries

Mei at 21:08, 19 March 2018

2018-03-19T21:08:19Z

Mei: Created page with "For CCA06, There are 3 different versions of data configuration files as noted in *Status of UCVM v17.1 (C) and v17.3 (Python). The main differences are the location o..."

2018-03-19T21:06:35Z

Created page with "For CCA06, There are 3 different versions of data configuration files as noted in *Status of UCVM v17.1 (C) and v17.3 (Python). The main differences are the location o..."

New page

For CCA06,

There are 3 different versions of data configuration files as noted
in *[[Status of UCVM v17.1 (C) and v17.3 (Python)]]. The main differences
are the location of the four corners of the model.

CCA github should be updated with the config file that Scott received
from David for his CyperShake runs

The config file from UCVM github should remain as it is. The CCA data
files under UCVM has been converted into a single file in HDF format and
hence its config is assumed not identical to the one used in CCA github
which is CCA in its native form

For CVM-S4.26,

The model tarball used by UCVM v17.1(C) matches with the fixed tarball
Scott has from David and so nothing needs to change

Similar to CCA06, CVM-S4.26's config file from UCVM v17.3(Python) is not
expected to be the same as the one used in UCVM v17.1(C) because of the data
format has changed and the config file format also has changed

@@ Line 2: / Line 2: @@
 There are 3 different versions of data configuration files as noted
-in *[[CCA06 Projection Review]]. The main differences
+in [[CCA06 Projection Review]]. The main differences
 are the location of the four corners of the model.

← Older revision		Revision as of 21:10, 19 March 2018
Line 24:		Line 24:
	== Related Entries ==		== Related Entries ==
	*[[UCVM Review]]		*[[UCVM Review]]
−	*[[Projection Correction issues]]

← Older revision		Revision as of 21:09, 19 March 2018
Line 24:		Line 24:
	== Related Entries ==		== Related Entries ==
	*[[UCVM Review]]		*[[UCVM Review]]
		+	*[[Projection Correction issues]]

@@ Line 18: / Line 18: @@
 Scott has from David and so nothing needs to change
-Similar to CCA06, CVM-S4.26's config file from UCVM v17.3(Python) is not
+. Similar to CCA06, CVM-S4.26's config file from UCVM v17.3(Python) is not
 expected to be the same as the one used in UCVM v17.1(C) because of the data
 format has changed and the config file format also has changed

@@ Line 5: / Line 5: @@
 are the location of the four corners of the model.
-CCA github should be updated with the config file that Scott received
+. CCA github should be updated with the config file that Scott received
 from David for his CyperShake runs
-The config file from UCVM github should remain as it is. The CCA data
+. The config file from UCVM github should remain as it is. The CCA data
 files under UCVM has been converted into a single file in HDF format and
 hence its config is assumed not identical to the one used in CCA github

@@ Line 1: / Line 1: @@
-For CCA06,
+== For CCA06 ==
 There are 3 different versions of data configuration files as noted
@@ Line 13: / Line 13: @@
 which is CCA in its native form
-For CVM-S4.26,
+== For CVM-S4.26 ==
 The model tarball used by UCVM v17.1(C) matches with the fixed tarball
@@ Line 21: / Line 21: @@
 expected to be the same as the one used in UCVM v17.1(C) because of the data
 format has changed and the config file format also has changed