Weight Event

[cookeac]

Discussed during the meeting on 22 November 2019.

Proposed properties:

• weight The weight of the animal using the Units specified (kilograms if unspecified). Number.
• method The method used to observe the weight. See the list below. (Loadcell if not specified). Optional
• units The units for the weight using UN/CEFACT abbreviations. Kilograms (KGM) if not specified. Enumeration. Optional
• resolution The selected resolution (minimum detectable change) of the device. For instance, 0.5, 2, 5, 10kg. Number. Optional
• device Identify the device used. Optional

1. I propose that we define an enumeration of common UN/CEFACT mass units so people know what may be specified for units.

2. We should define an enumeration for method including:

   • Loadcell - weighed using a loadcell or loadbars
   • Girth - measured using a girth tape
   • Assessed - visual assessment by a person
   • Walkover - using walkover weighing or a similar real-time averaging technique
   • Predicted - predicted weight on a date using a growth algorithm or similar
   • Imaged - predicted using infra-red, camera, or 3D imaging
   • GroupAverage - an average applied when a pen of animals are weighed together.

3. I propose we define an object for device that:

   • Derives from icarResourceReferenceType, so that it can have a link to the device resource. Optional
   • deviceType is a device type registered with the database proposed by the Sensor Working Group. This could be a UUID but we prefer a meaningful string.
   • serial is an Optional unique serial number of the device itself (or a network ID, if networked?)

If this is agreed I will define and submit a PR for:

• icarWeightEventResource.json
• uncefactMassUnitsType.json
• icarWeightMethodType.json
• icarWeightEventCollection.json (a paged collection of weights)

[erwinspeybroeck]

Andrew,

I have no remarks

Kind regards,

Erwin

Van: Andrew Cooke notifications@github.com Verzonden: vrijdag 6 december 2019 23:27 Aan: adewg/ICAR ICAR@noreply.github.com CC: Subscribed subscribed@noreply.github.com Onderwerp: [adewg/ICAR] Weight Event (#53)

Discussed during the meeting on 22 November 2019.

Proposed properties:

• weight The weight of the animal using the Units specified (kilograms if unspecified). Number.

• method The method used to observe the weight. See the list below. (Loadcell if not specified). Optional

• units The units for the weight using UN/CEFACT abbreviations. Kilograms (KGM) if not specified. Enumeration. Optional

• resolution The selected resolution (minimum detectable change) of the device. For instance, 0.5, 2, 5, 10kg. Number. Optional

• device Identify the device used. Optional

  1. I propose that we define an enumeration of common UN/CEFACT mass units so people know what may be specified for units.
  2. We should define an enumeration for method including:

• Loadcell - weighed using a loadcell or loadbars

• Girth - measured using a girth tape

• Assessed - visual assessment by a person

• Walkover - using walkover weighing or a similar real-time averaging technique

• Predicted - predicted weight on a date using a growth algorithm or similar

• Imaged - predicted using infra-red, camera, or 3D imaging

• GroupAverage - an average applied when a pen of animals are weighed together.

  1. I propose we define an object for device that:

• Derives from icarResourceReferenceType, so that it can have a link to the device resource. Optional

• deviceType is a device type registered with the database proposed by the Sensor Working Group. This could be a UUID but we prefer a meaningful string.

• serial is an Optional unique serial number of the device itself (or a network ID, if networked?)

If this is agreed I will define and submit a PR for:

• icarWeightEventResource.json
• uncefactMassUnitsType.json
• icarWeightMethodType.json
• icarWeightEventCollection.json (a paged collection of weights)

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/adewg/ICAR/issues/53?email_source=notifications&email_token=ALJHIXBXNJUKMAROPBTW2ZTQXLGSDA5CNFSM4JXCSZT2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H6YSHKA, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALJHIXHRTNW2UL3UEBATGOLQXLGSDANCNFSM4JXCSZTQ.

This message is subject to the following E-mail Disclaimer. (http://www.crv4all.com/disclaimer-email/) CRV Holding B.V. seats according to the articles of association in Arnhem, Dutch trade number 09125050.

[ahokkonen]

Will "uncefactMassUnitsType" type be used only for defining unit for cow weight value or it will be reused also for other weight/mass -based values, milk for example?

[cookeac]

Feedback from Australian/NZ discussions, some 10+ organisations were:

1. Add "FrontEndCorrelated" to methods to capture automated weighing stations with feed bins that capture front end weights and correlate these to predict total animal weight. new
2. Add Operator attribute to capture person responsible for manual weighing. Discussed and accepted at last meeting.
3. Add TimeOffFeed attribute (hours) to capture time between animals moved from pasture or feed access to weighing (time to "empty out", hopefully standardising by reducing gut fill). 0 where animals are weighed in a feed environment. Discussed and accepted at last meeting.
4. Add ContemporaryGroup (or ManagementGroup) to allow an operator to distinguish groups of animals at manual weighing that have been somehow treated differently in such a way that they must be in a different contemporary group for animal model statistical analysis. In theory this could be established from other information such as feed and location records, but in extensive systems these cannot currently be readily automated. To be discussed further.

[cookeac]

Implemented in #76