Dear all,
I attach the document comparing the APEL schema with the UR
specification. You can find how APEL describes both individual and
aggregated records and the extra fields it uses.
Regards,
Cristina <
Hello Cristina: Many thanks for you contribution. Could you please also clarify following properties being used in APEL schemas. 1). LcgRecord's "BaseCpuTime" and "BaseCpuTimeSeconds" property In OGF UR version 1.0, the @urf:usageType attribute is used to distinguish "user" and "system" usage. So what these two LcgRecord properties to be mapped, user or system? 2). Same as "SumCpu" and "NormSumCpu" properties in Lcg Anonymous and user aggregate schemas. 3). You also represented 7 extension properties in LcgRecord schemas. If you have to map them as extension properties being defined in OGF UR extension framework, what you would like to express them. You may specify your options or simply confirm/correct following mappings: -------------------------------------------------------------------------------------- | LcgRecord Property | UR Property (XPath Expr.) | |------------------------------------------------------------------------------------| |ExecutingSite | //urf:Resource[@urf:description='ExecutingSite' | |------------------------------------------------------------------------------------| |SpecInt2000 | //urf:Resource[@urf:description='SpecInt2000' | |------------------------------------------------------------------------------------| |SpecFloat2000 | //urf:Resource[@urf:description='SpecFloat2000' | |------------------------------------------------------------------------------------| |EventDate | //urf:TimeInstant[@urf:type='EventDateTime' | |------------------------------------------------------------------------------------| |EventTime | //urf:TimeInstant[@urf:type='EventDateTime' | |------------------------------------------------------------------------------------| 4). Finally I presume the "MeasurementDate" and "MeasurementTime" should be mapping to /urf:RecordIdentity/@urf:createTime attribute as the creation timestamp of a row or a usage record. Could you please also confirm it as well. X. Chen BITLab School of Engineering and Design Brunel University, Uxbridge Middlesex, UB8 3PH London
Hi Xiaoyu, Here are the answers to your questions. 1 and 2) The Cpu time recorded by APEL is user+system. 3 and 4) The mappings you suggest seem to be the best choice, so consider them confirmed. Kind regards, Cristina -----Original Message----- From: Xiaoyu Chen [mailto:Xiaoyu.Chen@brunel.ac.uk] Sent: 20 March 2009 16:40 To: Del Cano Novales, C (Cristina) Cc: ur-wg@ogf.org Subject: APEL vs UR comparison Hello Cristina: Many thanks for you contribution. Could you please also clarify following properties being used in APEL schemas. 1). LcgRecord's "BaseCpuTime" and "BaseCpuTimeSeconds" property In OGF UR version 1.0, the @urf:usageType attribute is used to distinguish "user" and "system" usage. So what these two LcgRecord properties to be mapped, user or system? 2). Same as "SumCpu" and "NormSumCpu" properties in Lcg Anonymous and user aggregate schemas. 3). You also represented 7 extension properties in LcgRecord schemas. If you have to map them as extension properties being defined in OGF UR extension framework, what you would like to express them. You may specify your options or simply confirm/correct following mappings: ------------------------------------------------------------------------ -------------- | LcgRecord Property | UR Property (XPath Expr.) | |----------------------------------------------------------------------- -------------| |ExecutingSite | //urf:Resource[@urf:description='ExecutingSite' | |----------------------------------------------------------------------- -------------| |SpecInt2000 | //urf:Resource[@urf:description='SpecInt2000' | |----------------------------------------------------------------------- -------------| |SpecFloat2000 | //urf:Resource[@urf:description='SpecFloat2000' | |----------------------------------------------------------------------- -------------| |EventDate | //urf:TimeInstant[@urf:type='EventDateTime' | |----------------------------------------------------------------------- -------------| |EventTime | //urf:TimeInstant[@urf:type='EventDateTime' | |----------------------------------------------------------------------- -------------| 4). Finally I presume the "MeasurementDate" and "MeasurementTime" should be mapping to /urf:RecordIdentity/@urf:createTime attribute as the creation timestamp of a row or a usage record. Could you please also confirm it as well. X. Chen BITLab School of Engineering and Design Brunel University, Uxbridge Middlesex, UB8 3PH London -- Scanned by iCritical.
Dear Cristina, I have a question regarding the mapping you provided: why you map the ProjectName as the ur:JobName? Shouldn't they be 2 different things? Regards, Andrea Del Cano Novales, C (Cristina) wrote:
Dear all,
I attach the document comparing the APEL schema with the UR specification. You can find how APEL describes both individual and aggregated records and the extra fields it uses.
Regards,
Cristina <
> ***Cristina del Cano Novales*
Scientific Technology Computing / e-Science
Science and Technology Facilities Council
Rutherford Appleton Laboratory
Harwell Science and Innovation Campus
Didcot OX11 0XQ
Tel: 0044(0)1235 445778
e-mail: ___cristina.del-cano-novales@stfc.ac.uk_ mailto:cristina.del-cano-novales@stfc.ac.uk
------------------------------------------------------------------------
Scanned by iCritical. ------------------------------------------------------------------------
-- ur-wg mailing list ur-wg@ogf.org http://www.ogf.org/mailman/listinfo/ur-wg
participants (3)
-
Andrea Cristofori
-
Del Cano Novales, C (Cristina)
-
Xiaoyu Chen