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
One of the inputs to this package is a "feature vector" file generated by the package IPFX using its "run_feature_vector_extraction" script. The types of data generated from IPFX must match the key values listed in the spca_params.json input.
As of IPFX v 1.0 the names of the datasets have changed from what is listed in drcme/config/default_spca_params.json. Below are the discrepancies
:
Shown in yellow are the dataset keys with the same name while blue indicates a discrepancy in the name. I think I've got them matched up correctly and after getting confirmation I can submit a pull request with the names changed to match the ipfx output.
The text was updated successfully, but these errors were encountered:
Thanks for identifying the issue. It looks correct apart from inst_freq - that should match up with the old spiking_inst_freq. The data set inst_freq_norm is actually calculated by DRCME rather than IPFX (since it's directly calculated from inst_freq in the H5 file). And subthresh_depol_norm doesn't have a pre-existing entry in that default parameters file.
One of the inputs to this package is a "feature vector" file generated by the package IPFX using its "run_feature_vector_extraction" script. The types of data generated from IPFX must match the key values listed in the spca_params.json input.
As of IPFX v 1.0 the names of the datasets have changed from what is listed in drcme/config/default_spca_params.json. Below are the discrepancies
![Capture](https://user-images.githubusercontent.com/62612214/95505607-9f693900-097c-11eb-884b-8678f163d1a3.PNG)
:
Shown in yellow are the dataset keys with the same name while blue indicates a discrepancy in the name. I think I've got them matched up correctly and after getting confirmation I can submit a pull request with the names changed to match the ipfx output.
The text was updated successfully, but these errors were encountered: