search

NAVADMC / ADSM

A simulation of disease spread in livestock populations. Includes detection and containment simulation.
Other
10 stars 5 forks source link

Folder Name #985

Closed missyschoenbaum closed 4 years ago

missyschoenbaum commented 4 years ago

This is related to the new portable installation process. When it installs, it asks where you want your folder to go, and then puts everything straight into that folder.

All my documentation is written that ADSM is going to create the "ADSM Workspace" that will be holding all the files, as compared to the folder designated by user is going to hold all files.

Will it be confusing? How hard it is to make things drop into an ADSM Workspace directory within the desired location? Holler if this isn't making sense.

BryanHurst commented 4 years ago

It makes sense.

I don't know how it will feel to the end user.
To me it makes sense that the folder you pick ends up holding all of the files.
The folder you are picking IS the "ADSM Workspace".

If you would prefer a new folder be created in the location the user picks, we can do that.

missyschoenbaum commented 4 years ago

Here's an example of how I explained the managed workspace. https://github.com/NAVADMC/ADSM/wiki/Results-Interpretation

I've probably discussed the ADSM Workspace in many places throughout documents. If we can fit it in this week, let's make a folder.

BryanHurst commented 4 years ago

Yes, we can probably get that in today.

BryanHurst commented 4 years ago

The fix for this will rename any portable installation workspace folders to ADSM Workspace. However, if a user previously picked a custom folder, it will stay as is and not be moved into an ADSM Workspace folder.
All future custom picked folders will be a location that we create a folder called ADSM Workspace.

BryanHurst commented 4 years ago

This was done in cb30aaec167ca529d4c0428c076fee28284154dd

missyschoenbaum commented 4 years ago

The folder worked, but I'm hitting something else. Will make another issue.