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
When exporting the current configuration to a JSON file using the Save to JSON button, the resulting file is a partial ProbeInterface file. Only the currently enabled electrodes are listed in the file, which means that if someone exports a quad-shank 2.0 probe, there are only 384 electrodes exported instead of the expected 5120 electrodes. All electrodes can be exported by leveraging the "device_channel_indices" field, which can be set to -1 for all electrodes that are disabled. This allows for the entire set of electrodes, including locations and shapes, to be exported and thus imported to another ProbeInterface compliant application.
The "probe_planar_contours" is not a required field, but it would be a welcome addition to the file, providing the bounds of the probe that encapsulates the electrodes. Again, this matters most when importing to another ProbeInterface application, allowing the probe contours to be drawn around the electrodes.
To become fully compliant with the format specifications and the schema file the manufacturer should be added under the "annotations" field, and no additional fields are allowed which means that "num_adcs" might need to be removed.
I also noticed that there isn't a Load from JSON button, but this would be good to add if possible.
I'm happy to discuss if there are any particular reasons why the JSON file is the way it is, and I'm also happy to take a crack at implementing some of these features. Thank you!
The text was updated successfully, but these errors were encountered:
Thanks for the update! This looks good, I was able to open it successfully and update the currently enabled electrodes. The planar contours would be a good addition, but are not necessary for the rest of the functionality.
I've attached a sample JSON file that was exported from our system, in case that's helpful for testing. Let me know if there's anything else I can do.
When exporting the current configuration to a JSON file using the
Save to JSON
button, the resulting file is a partial ProbeInterface file. Only the currently enabled electrodes are listed in the file, which means that if someone exports a quad-shank 2.0 probe, there are only 384 electrodes exported instead of the expected 5120 electrodes. All electrodes can be exported by leveraging the "device_channel_indices" field, which can be set to-1
for all electrodes that are disabled. This allows for the entire set of electrodes, including locations and shapes, to be exported and thus imported to another ProbeInterface compliant application.The "probe_planar_contours" is not a required field, but it would be a welcome addition to the file, providing the bounds of the probe that encapsulates the electrodes. Again, this matters most when importing to another ProbeInterface application, allowing the probe contours to be drawn around the electrodes.
To become fully compliant with the format specifications and the schema file the manufacturer should be added under the "annotations" field, and no additional fields are allowed which means that "num_adcs" might need to be removed.
I also noticed that there isn't a
Load from JSON
button, but this would be good to add if possible.I'm happy to discuss if there are any particular reasons why the JSON file is the way it is, and I'm also happy to take a crack at implementing some of these features. Thank you!
The text was updated successfully, but these errors were encountered: