Update Probe Interface compatibility

[bparks13]

Skip the probe contour if it does not exist in the file, as it is not a required element in the ProbeInterface specification.

Add warnings to alert the user about any specific issues found when parsing the file.

• Fixes Update Probe Interface compatibility #129

[cjsha]

The onebox -> onix-source compatibility seems good to me

[cjsha]

bonsai -> onix-source compatibility seems good

[cjsha]

onix-source -> bonsai compatibility seems good

[cjsha]

so far so good for np1

[cjsha]

Also, there are just a lot of potential ways for the probeinterface file to not correspond to a neuropixels which prompt the user with a warning and i'm not immediately sure how to generate a bunch of probeinterface files to check this logic efficiently

[bparks13]

Also, there are just a lot of potential ways for the probeinterface file to not correspond to a neuropixels which prompt the user with a warning and i'm not immediately sure how to generate a bunch of probeinterface files to check this logic efficiently

@cjsha

I'm not sure if this is the best way to do it, but I would go through and remove or change the necessary elements by hand to trigger the different conditions (i.e., remove the specification field, or change the value in the JSON file), or by loading files that were saved by other devices (such as the Rhs2116 GUI in Bonsai) that had the wrong number of channels.

[cjsha]

[cjsha]

[cjsha]

[cjsha]

[cjsha]

overall i did the following tests:

	onix-source	bonsai
onix-source	n/a	np1 & np2
bonsai	np1 & np2	n/a
onebox	np1	didn't try it
neuropix-pxi	np2	didn't try it

probeinterface file was generated by the software in the column and loaded by the software in the row. np1 & np2 indicate which probe was used to perform the probeinterface compatibility test.

onebox and neuropix-pxi don't get their own columns bc they don't have the option to load probeinterface json files.