You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, I'm quite unhappy with having to use patternProperties. Imho, IOOperations, Functions, Messages, CollectiveOperations, Files should not be objects with contents name : object but instead should be lists [ { name: ..., content1: ..., ... }, ... ]. In that case, the Schema would look like below:
However, I'm not sure which of entries should be made required. I think at least TimerResoultion should be made required as else all the times are useless. But on the other hand, maybe we are not intersted in times but only in file accesses, ...
Also, a version number as proposed in #19 is not yet included in the schema.
The text was updated successfully, but these errors were encountered:
For a quick check for correctness of the profile summaries, I propose to add a schema definition file to this repo:
profile-summary.1.schema.json: JSON schema matching the current format
However, I'm quite unhappy with having to use
patternProperties
. Imho,IOOperations
,Functions
,Messages
,CollectiveOperations
,Files
should not be objects with contentsname : object
but instead should be lists[ { name: ..., content1: ..., ... }, ... ]
. In that case, the Schema would look like below:profile-summary.2.schema.json: Proposed schema (untested)
However, I'm not sure which of entries should be made required. I think at least
TimerResoultion
should be made required as else all the times are useless. But on the other hand, maybe we are not intersted in times but only in file accesses, ...Also, a version number as proposed in #19 is not yet included in the schema.
The text was updated successfully, but these errors were encountered: