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
At chartering time, feedback was given it is important to define the following is out of scope:
This Community Group does not attempt to mandate a specific neural network or Machine Learning model schema or format. Other groups are expected to address these requirements of this evolving area.
Given model formats are still evolving rapidly and there exists multiple such formats (and versions of each) that are in production use, defining a new model or graph format in this group is unlikely to contribute toward a solution (mandatory xkcd).
The current market accepted solution is to use model converters, also available as open source.
To conclude, the group chose option 1 initially. After revisiting related discussion in #3 I'm not seeing adequate support to change this at this time.
The issue is open to capture any further comments on the topic.
Hearing no further comments, I conclude the group is not interested in opening discussion on a new model or graph format at this time. This group position is consistent with the charter so no changes there.
Uh oh!
There was an error while loading. Please reload this page.
As I find it a separate topic to #3, would like to continue conversations about graph format itself (not operators and not api) here.
So far we have 3 major discussions:
For the reasons I gave in these (and other) posts:
I opt for option 3 - JSON format.
Simple example with one hidden layer, 8 inputs and 9 outputs:
Same NN as above, but with weights data provided:
Some "dummy" advanced example for JSON format:
The text was updated successfully, but these errors were encountered: