-
Notifications
You must be signed in to change notification settings - Fork 9
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
remove dependency to recipe.xml file #62
Comments
Currently, the recipe is parsed into a list of (layer, m-type, e-type)-tuples. What is common practice for this type of data? An .xml-tree (layers > m-types > e-types), just without the extra info? A .json-file ({: { : [, , ...], : ... }}), a .yaml-file?? The word "layer" could be replaced by a more general indication for an anatomical region. |
My two cents are:
or something flat, like CSV:
|
So, it seems that @jdcourcol / @arsenius7 / @liesbethvanherpe and I think that simple CSV is the way to go. |
I'd say a json is a bit more readable though, but csv is also kind of ok |
btw, we should also think about fullmtype vs mtype/submtype. I hope the recipe doesn't specify per mtype (without specifying submtype) ? |
And shouldn't we keep the percentage data, in case we need to something with it in BluePyMM in the future ? |
As long as we don't use percentage, there is no reason to have that. |
the question is, what does it hurt? and we wouldn't have to change the format afterwards. btw, talking about, in case we use json we could also easily add a format version string. |
it hurts as it is useless information for the time being. keep it simple. |
This file is an internal format to BBP. It is also specific to circuit building. It may also contains information that are useless for this tool (such as connectivity).
The current set of tags is also specific to the neo cortical column (blueColumn) for instance, and layers.
The text was updated successfully, but these errors were encountered: