What my AI said: This is an interesting and frustrating issue!
Most Likely Causes
1. Class Method ShadowingThe @instrRack folders indicate these are MATLAB class definitions. The @ prefix means these are class folders, and instrRack.m inside would be the constructor. MATLAB's class method resolution can be tricky:
- If an instrRack object was created from the "adr" version, calling methods on that object will use methods from that class definition, regardless of your current path
- This can persist across function calls if the object is passed around
2. Persistent import StatementsIf any code (yours or a colleague's) used import statements to bring the "adr" package into scope, these imports can persist in the MATLAB workspace even after clear all. Only clear classes or restarting MATLAB clears them.
3. Hidden Path EntriesCheck for:
- javaaddpath or javaclasspath.txt entries
- Path additions in startup.m files (check both your user folder and the MATLAB installation directory)
- pathdef.m modifications
4. MEX File or P-Code CachingIf there are compiled MEX files or P-coded versions, MATLAB caches these aggressively. They won't show up in typical path searches but will execute preferentially.
Diagnostic Commands to Run
% Find ALL instrRack files
which instrRack -all
% Check for class definitions specifically
which @instrRack/instrRack -all
% See what's actually being called
dbstop if error % Then trigger the error and check the stack
% Check for hidden path issues
restoredefaultpath
savepath % If this fixes it, something was corrupting pathdef.m
Why Restarting Fixed It
The fact that restarting MATLAB multiple times didn't fix it, but restarting the PC did, suggests:
- A locked file handle or shared memory issue
- A system-level environment variable affecting MATLAB's startup
- Antivirus or file monitoring software holding locks
Recommendations
- Use clear classes instead of just restarting MATLAB when you encounter this
- Add to your main script: rehash toolboxcache at the beginning
- Verify no one added the "adr" path: Check your team's shared startup.m or pathdef.m files
- Use absolute path diagnostics: Add this to your main function:
instrRackPath = which('instrRack');
assert(contains(instrRackPath, 'unified\Instruments'), 'Wrong instrRack loaded from: %s', instrRackPath);
Consider using packages (if upgrading is possible) to avoid name collisions entirely
The corporate IT situation with older MATLAB is understood, but this shadowing behavior is exactly why MATLAB improved its package system in later versions!
