Skip to content

Conflicts when running multiple MATLAB sessions on the same dataset #11

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dsterry opened this issue Feb 12, 2025 · 1 comment
Open
Assignees

Comments

@dsterry
Copy link
Contributor

dsterry commented Feb 12, 2025

Description: Running automation workflows (gettraces and autotraces) in separate MATLAB instances may not work correctly. For example, autotrace may try to load a .rawtraces file before it has completed saving by gettraces in the other MATLAB session.

Workaround: Run all automation workflows in a single MATLAB session.

Development ideas:

  • autotrace could check multiple times to see if file size is changing before opening
  • gettraces could save the .rawtraces file with a temporary name and then rename when finished. Similar to what FlashGordon already does.
@dsterry dsterry self-assigned this May 17, 2025
@dsterry
Copy link
Contributor Author

dsterry commented May 29, 2025

The specific error is below. The rawtraces file can be read by autotrace before it is finished saving. loadTraces sees a valid file until it reaches the metadata, where the file ends abruptly.

    file: 'C:\code\spartan\Traces\loadTraces.m'
    name: 'readMetadata'
    line: 237

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant