Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reference data set and generator #63

Conversation

d-stahl-ericsson
Copy link
Contributor

Added a reference data set, consisting of events representing 5000 semi-random iterations of a hypothetical pipeline. Documentation and generator script included. This addresses issue #32.

Also updated the validation script to no longer simply loop over schemas and attempt to apply to matching example files. Instead it reads all schemas, then reads all examples from all files, including lists of events (as found in examples/flows), then attempts to validate them all. The script also reports warnings for unchecked examples (due to missing schemas). The reason for implementing this change now is to be able to supportdevelopment development of large reference data sets.

Added obsolete generator script (to be updated) along with dummy events file.
The validation script will no longer simply loop over schemas and attempt
to apply to matching example files. Instead it reads all schemas, then
reads all examples from all files, including lists of events (as found in
examples/flows), then attempts to validate them all.

The script also reports warnings for unchecked examples (due to missing
schemas).

The reason for implementing this change now is to be able to supportdevelopment
development of large reference data sets.
@d-stahl-ericsson d-stahl-ericsson merged commit a8a719f into eiffel-community:topic-drop3 Sep 6, 2016
@d-stahl-ericsson d-stahl-ericsson deleted the topic-drop3-referencedataset2 branch September 30, 2016 06:51
@erobged
Copy link

erobged commented Apr 10, 2017

Hi Daniel ,
I have a comment about the default.md regarding the numbering convention of the events themselves.
For example TCS7 , TCS6 & TCS5 all occur in time before TCS4 , TCS3 & TCS1.
Another example is EDef2 occurs in time before EDef 1.
It appears the correct way to read the links, is from the bottom of the page up to the top. (start at the last event and work backwards).
This creates a bit of conflict with the numbering if the flow of time is taken into consideration.
(e.g EDef2 occurs before EDef1).

Maybe all that is needed to resolve the conflict is to clarify how to read the link flows with respect to time.

@erobged
Copy link

erobged commented Apr 10, 2017

plus it makes it hard to scale the link flow...

@d-stahl-ericsson
Copy link
Contributor Author

Point taken. You should post it as an issue, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants