adding simulatable neuron class and registering function

[AurelienJaquier]

• adding a new class: SimulatableNeuron
• adding a new nexus function to register SimulatableNeuron into the nexus database

Since we are going to move away from nexus, I took some liberties:

• No file attached to simulatableneuron resource. Metadata conform to the schema, we don't need a json file since everything is in the metadata, and we don't duplicate any morph/mech/hoc. Download button on the platform will have to get mech/morph/hoc from ids.
• No eModel or eType or iteration_tag in the metadata, to conform to future new standards in schemas.
• No file and no eModel, etc. means that we won't be able to fetch the resource the way we were doing in BluePyEModel. So I did not create any get_sumlatable_neuron in the NexusAccessPoint. We will have to figure this out when we create the new entitycore access point.
• Since we don't have eModel, etc., we cannot automatically replace the resource when we upload it a second time. We will have to be aware of that.
• I did not implement from_circuit and synaptomes, that have been added in the schema by Christoph. Since this is just to upload our models for now it is ok. We will have to think later if we should add those fields in BPEM also.

This has not been tested yet. We are waiting on being able to use nexus again.

[darshanmandge]

Thanks @AurelienJaquier! Do you also want to link the SimulatableNeuron class to the EModelWorkflow in this PR or do you plan to do it in another one?

[AurelienJaquier]

Thanks @AurelienJaquier! Do you also want to link the SimulatableNeuron class to the EModelWorkflow in this PR or do you plan to do it in another one?

Done in latest commit

[darshanmandge]

I assume this is a list because you want to add all the related resource IDs of SimulatableNeuron to one list without any order or names. Do you not want to distinguish between different IDs of different resource types: morphology, mechanisms, etc.?

[AurelienJaquier]

It is a list because a workflow can produce multiple emodels (using multiple seeds)

[AurelienJaquier]

mechanisms id, morphology id are listed in simulatable neuron class. They are also present in emodel configuration

[darshanmandge]

It is a list because a workflow can produce multiple emodels (using multiple seeds)

Oh, alright. So, to access the best one e.g. similar to one generate hoc function, do you plan to create a function for SimulatebleNeuron?

[AurelienJaquier]

No. We don't do that in generate hoc function