report

[CPernet]

have a way to output a report - since it already says N files, X modaliaty, etc ... just have that with % ignore and the date

[bendhouseart]

Current state of the report is as follows:

Found 11 files that are valid_and_ignored
/sub-06/eeg/sub-06_task-matchingpennies_channels.tsv
/sub-06/eeg/sub-06_task-matchingpennies_eeg.vmrk
/sub-06/eeg/sub-06_task-matchingpennies_eeg.vhdr
/sub-06/eeg/sub-06_task-matchingpennies_eeg.eeg
/sub-06/eeg/sub-06_task-matchingpennies_events.tsv
/sub_07/eeg/sub-07_task-matchingpennies_events.tsv
/sub-05/eeg/sub-05_task-matchingpennies_eeg.eeg
/sub-05/eeg/sub-05_task-matchingpennies_channels.tsv
/sub-05/eeg/sub-05_task-matchingpennies_events.tsv
/sub-05/eeg/sub-05_task-matchingpennies_eeg.vmrk
/sub-05/eeg/sub-05_task-matchingpennies_eeg.vhdr


Found 21 files that are valid_bids_files
/CHANGES
/README
/dataset_description.json
/participants.tsv
/sub-06/eeg/sub-06_task-matchingpennies_channels.tsv
/sub-06/eeg/sub-06_task-matchingpennies_eeg.vmrk
/sub-06/eeg/sub-06_task-matchingpennies_eeg.vhdr
/sub-06/eeg/sub-06_task-matchingpennies_eeg.eeg
/sub-06/eeg/sub-06_task-matchingpennies_events.tsv
/sub-17017/anat/sub-17017_T1w.nii.gz
/sub-17017/func/sub-17017_task-rest_bold.nii.gz
/sub-17017/func/sub-17017_task-rest_bold.json
/sub_07/eeg/sub-07_task-matchingpennies_events.tsv
/sub-19738/anat/sub-19738_T1w.nii.gz
/sub-19738/func/sub-19738_task-rest_bold.nii.gz
/sub-19738/func/sub-19738_task-rest_bold.json
/sub-05/eeg/sub-05_task-matchingpennies_eeg.eeg
/sub-05/eeg/sub-05_task-matchingpennies_channels.tsv
/sub-05/eeg/sub-05_task-matchingpennies_events.tsv
/sub-05/eeg/sub-05_task-matchingpennies_eeg.vmrk
/sub-05/eeg/sub-05_task-matchingpennies_eeg.vhdr


Found 10 files that are valid_bids_files_not_ignored
/CHANGES
/README
/dataset_description.json
/participants.tsv
/sub-17017/anat/sub-17017_T1w.nii.gz
/sub-17017/func/sub-17017_task-rest_bold.nii.gz
/sub-17017/func/sub-17017_task-rest_bold.json
/sub-19738/anat/sub-19738_T1w.nii.gz
/sub-19738/func/sub-19738_task-rest_bold.nii.gz
/sub-19738/func/sub-19738_task-rest_bold.json


Found 4 files that are invalid_bids_files_and_ignored
/sub_07/eeg/sub-07_task-matchingpennies_eeg.vmrk
/sub_07/eeg/sub-07_task-matchingpennies_channels.tsv
/sub_07/eeg/sub-07_task-matchingpennies_eeg.vhdr
/sub_07/eeg/sub-07_task-matchingpennies_eeg.eeg


Found 1 files that are invalid
/.bidsignore

It's real sketchy determining if some things are valid BIDS filenames or not, it mostly gets it right, but I think the use of the Python based validator at this point in time is a bit suspect.

It seems like a better approach would be to start with using the JavaScript validator's json output and building around that as datatypes and modalities are already included.

see:

{
  "issues": {...},
  "summary": {
    "sessions": [],
    "subjects": [
      "17017",
      "19738"
    ],
    "subjectMetadata": [
      {
        "participantId": "17017"
      },
      {
        "participantId": "19738"
      }
    ],
    "tasks": [
      "rest"
    ],
    "modalities": [
      "MRI"
    ],
    "secondaryModalities": [
      "MRI_Functional",
      "MRI_Structural"
    ],
    "totalFiles": 12,
    "size": 109563873,
    "dataProcessed": false,
    "pet": null,
    "dataTypes": [
      "T1w",
      "bold"
    ]
  }
}

[CPernet]

sure, wrap around the json from JS sounds easier - the idea is that a txt file is generate on top (and downloadable if used in browser) with just the header lines you have (x file valids, n files invalids, z files valid but ignored, etc)

thx - it will be useful for the repositories and for paper submissions