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
Let us know where something needs a refresh or put your idea here!
We started some discussion in #96 about the availability of example code and specifications. This is important for training LLM models and for providing them as a context. In the Roche admiral experiment it was noted that specs are better to be in json format. Hence we need the following:
create as many specs as possible, perhaps 10 domains from different categories. It is fine to have the original copy as csv, but we should convert it into json and keep in the repo
create more complete code examples similar to CM and VS articles
perhaps enhance the articles of code examples highlighting the importance of variable dependency and how one should come before something else. How the order of pipe elements is important.
talk with admiral team about what we can do preemptively to increase the quality of generated code
The text was updated successfully, but these errors were encountered:
edgar-manukyan
changed the title
Documentation: <Create more examples of domain derivation with specs as json>
Documentation: Create more examples of domain derivation with specs as json
Sep 18, 2024
Please select a category the issue is focused on?
Documentation
Let us know where something needs a refresh or put your idea here!
We started some discussion in #96 about the availability of example code and specifications. This is important for training LLM models and for providing them as a context. In the Roche admiral experiment it was noted that specs are better to be in json format. Hence we need the following:
The text was updated successfully, but these errors were encountered: