search

ucsb-coast-lab / moos-ivp-ucsb

A collection of MOOS applications and IvP behaviors developed by the COAST Lab at UCSB
6 stars 1 forks source link

Major modification: changed directory structure to allow build.sh to work #18

Closed quietlychris closed 5 years ago

quietlychris commented 5 years ago

Re-downloaded moos-ivp-extend tree and moved (while trying to conserve metadata) all prior moos-ivp-ucsb files, such that this git repository can be downloaded into the same directory as the user's moos-ivp directory, and then could add it's bin/ directory to the PATH and run without needing to copy process files, missions, etc. into the moos-ivp main tree. Still having build issues with some of the prior src/ behavior directories, mostly with being unable to locate dependencies, but all SAMS files can compile and run from this tree using the launch.sh script

Also added a .gitignore file, and the farm_w_sams_executive Python mission analysis script now has waypoints for both ~horizontal and ~vertical farm orientations.

quietlychris commented 5 years ago

I'm merging these changes, then will clone the repository into my home directory (same top-level directory as my main moos-ivp) after renaming the original local branch. If the build and mission runs successfully, everything should be fine. If not, I'll revert master to it's previous form, track down what the problem is, and try it again.

quietlychris commented 5 years ago

Okay, looks like everything should be working; the cloned repository builds as planned, and when its bin folder is added to the PATH in .bashrc, the mission executes properly using both binaries from the main moos-ivp and moos-ivp-ucsb locations.

This means it should now be fairly easy for anyone to clone this repository, write or edit behaviors, and make pull requests or commits without too much shuttling back and forth between directories or using complex git files.