Skip to content
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

Add Wiki Entry Regarding Mac OS Compatibility #64

Open
TheElectricDream opened this issue Mar 4, 2024 · 3 comments
Open

Add Wiki Entry Regarding Mac OS Compatibility #64

TheElectricDream opened this issue Mar 4, 2024 · 3 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@TheElectricDream
Copy link
Collaborator

Title is self-explanatory

@TheElectricDream TheElectricDream added the documentation Improvements or additions to documentation label Mar 4, 2024
@TheElectricDream TheElectricDream self-assigned this Mar 4, 2024
@adamvigneron
Copy link

First, the easy one -- Mac OS paths use the forward slash, Windows paths use the backward slash.

Affected files:
Setup_Environment.m
GUI_v4_0_Main.mlapp

One possible fix is to replace all path-related uses of backslash with the filesep command:
filesep in MATLAB

Also possible to build paths using the fullfile command:
fullfile in MATLAB

...according to this thread, we could just YOLO and only use forward slashes:
forward slash thread

@adamvigneron
Copy link

adamvigneron commented Mar 4, 2024

Second, as the NVIDIA add-on isn't currently supported for Mac OS, experiments are not possible AND simulations need a few more things commented out:

HardwareBoard lines in GUI_v4_0_Main.mlapp
the project *.slx file, blocks corresponding to experiment logic and the NVIDIA interface.

Commented lines in the GUI:
1973: setParam(activeConfigObj,'HardwareBoard','None');
1999: setParam(activeConfigObj,'HardwareBoard','NVIDIA Jetson');

Commented Simulink blocks:
> Check Connection
> PhaseSpace Camera Code > Use Hardware to Obtain States
> Send Data to TX2
> Thruster Control Code > UDP Send

@adamvigneron
Copy link

adamvigneron commented Mar 5, 2024

@TheElectricDream , let's see how we can do this in an efficient manner.

Per the comments above, I've made changes to three files:
SetupEnvironment.m
GUI_v4_0_Main.mlapp
BetaMacs.slx (my project copy of the template)

I've pushed the changes to my SPOT fork:
adamvigneron@2eeefe4

where it's possible to see the plaintext M-file changes but not possible to see the binary changes. Luckily, the binary files can be compared to their Template_Files/ equivalents using MATLAB functionality for File Compare.

How do you want to go about capturing this in the wiki?
How do you want to go about capturing this in the codebase?

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

No branches or pull requests

2 participants