Skip to content

Latest commit

 

History

History
44 lines (40 loc) · 2.75 KB

upgrade_from_v1.md

File metadata and controls

44 lines (40 loc) · 2.75 KB
Raw

Upgrade from AIDE v1

If you already have an installation of the first version (v1) of AIDE installed, you can upgrade it to the latest version (v2) as described below.

Notes:

  • These instructions do not transfer a v1 project to a new database, they just upgrade an existing v1 project to work with the v2 installation that points to the same database.
  • Once a v1 project has been successfully updated with this script, the original configuration .ini file can be discarded. There is no need to run this script more than one time for a specific v1 project.
  • Do NOT continue to use the v1 software on a project that has been upgraded to v2.

To upgrade a project from v1 to v2, follow these steps:

  1. Create a backup of your v1 settings.ini file somewhere.
  2. Modify the new (v2) config/settings.ini file with the correct parameters. Notes:
    • Set a meaningful directory for the staticfiles_dir parameter under [FileServer]. AIDE v2 can host multiple projects, so it can be generic!
    • Any options specified in the v1 settings.ini file not present in the new version can be ignored.
  3. Move your v1 images to the right destination folder: <staticfiles_dir>/<schema>. For example:
    • If your v1 project's images reside in /datadrive/v1/images (parameter staticfiles_dir under [FileServer] of the v1 settings.ini file),
    • Your v1 project's database schema name is my_great_project (parameter schemaunder [Database] of the v1 settings.ini file),
    • You specify /datadrive/v2/images as the new folder for AIDE v2 (parameter staticfiles_dir under [FileServer] of the v2 settings.ini file),
    • Then you must move your images from /datadrive/v1/images to /datadrive/v2/images/my_great_project.
  4. Clone the AIDE repository into a new folder: git clone https://github.com/microsoft/aerial_wildlife_detection.git
  5. Install missing dependencies in your environment
    conda activate aide
    pip install -r requirements.txt
  1. Set environment variables:
    export PYTHONPATH=.
    export AIDE_CONFIG_PATH=config/settings.ini
  1. Run the following migration script (with the appropriate path at the end):
    python projectCreation/upgrade_v1_project.py --settings_filepath=/path/to/v1/settings.ini

If you did not do step 3, you might be asked if you want AIDE to create a symbolic link to your images. Be aware that although this works as a quick fix, it is not recommended for deployment, as other projects in AIDE v2 may be able to see each other's images this way, due to the recursive nature of the link. 7. Launch AIDE v2:

    ./AIDE.sh

Unlike v1, this script always launches a Celery worker together with the Gunicorn server.