Add headless CARTO and EnSiteX importer integration workflow#92
Draft
KestutisMa wants to merge 54 commits into
Draft
Add headless CARTO and EnSiteX importer integration workflow#92KestutisMa wants to merge 54 commits into
KestutisMa wants to merge 54 commits into
Conversation
…(v 4.1) where they no longer contain the unipole and bipole mapping channel names. Instead these are accessed from the point XML file within importcarto_mem.
…rent syntax for `matches` for Matlab versions <R2022a
… dummy RF data, a workaround for compatibility with EP workbench. Additionally edited getEarliestActivationSite / getLatestActivationSite to work with files exported from EP Workbench.
Data Export Element continues to have more and more overlapping names, so a separate function to standardize. importensitex is an adjusted version of importprecision and works with the new files. It needs a helper function to convert into OpenEP format and this can be written separately.
…de naming - both with two unipoles specificed in the bipole electrode naming and without
… full Precision case, if the SOP for exporting the data has been followed
…d the voltages of unipolar electrograms
…have a robust routine for comma delimited strings - note this seems to be needed for mapping files but not wave files. It is much slower so we still use regexp for wave files.
…value pair to loadenxitex_dxldata.m to prevent waitbar being called (needed for parallel processing in the test case)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a headless CARTO and EnSiteX conversion workflow suitable for TRE/automated use. The workflow converts mapping exports into OpenEP MAT files, validates the source data and imported OpenEP structures, and writes machine-readable status/progress information plus a human-readable log.
Main Changes
convert_mapping_caseas the machine-facing conversion entry point./dev/shmwhen available, with temp-folder fallback and cleanup.bi,uni, andomnidatasets in one MAT file.select_openep_datasetfor selecting a nested OpenEPuserdatastructure by recording mode.userdata, and multi-dataset OpenEP case containers.Output Contract
A successful conversion writes:
case.matcase.status.jsoncase.log.txtDuring conversion it also maintains transient
case.progress.json, which is removed after final status publication. If MATLAB is interrupted, a stale progress file remains as evidence of an incomplete job.Validation
run('run_validation_tests.m').RUN_FULL_CARTO_IMPORT_TESTS=1.RUN_FULL_IMPORTER_SMOKE_TESTS=1.Full-case tests remain opt-in because they require local clinical exports, large temporary storage, and several minutes to run.
Notes
This is intended as a first integration-ready workflow for TRE/headless conversion. It is not ARO-specific code; ARO can be an initial downstream consumer of the generic conversion contract.