The Natural Florida History Museum HAAG project. A ML-backed search engine of ecological data.

• Local Setup

  • Super Quick Start
  • Less Quick Start
  • Least Quick Start

• Seeding Mongo with Raw Data

  • Seeding Mongo with a sample of iDigBio data
  • Seeding Mongo with a sample of GBIF data

• Generate Embeddings

• Jupyter Notebooks

• Accessing the Mongo Database

• Accessing the Postgres Database

• Accessing the Mongo Database

• Database Versioning

• Running and tagging experiments

• Accessing Redis

• Useful Commands

  • Sharing Data

Docker is a prerequisite.

1. Download project: git clone [email protected]:BioCosmos-AI/BioCosmos.git biocosmos

1. Open and run project in dev container with VSCode
2. Set up postgres db with initital data: bin/import_vector_db
3. Run the backend API (from within the dev container): bin/dev
4. Navigate to http://localhost:3000 in your browser

If the Super Quick Start above doesn't work (for example, you're not using a mac), then the following steps capture the essential idea. Modify as necessary for your local computing environment.

1. Open and run project in dev container with VSCode
2. Download the sample vector database:
   • (With Mac's unzip): curl "https://drive.usercontent.google.com/download?id={17QGJ3o7rx88A51KjUije6RX_j4kV0WXr}&confirm=xxx" -o tmp.pgsql.zip && unzip tmp.pgsql.zip
3. Copy that file to the postgres docker container
   • docker ps | grep 'nfhm' | grep 'postgres' to get container name
   • docker cp vector_embedder_data_only.pgsql nfhm_devcontainer-postgres-1:/tmp/import.pgsql (Replace nfhm_devcontainer-postgres-1 and vector_embedder_data_only.pgsql with container and filename, respectively, as appropriate.)
4. Run import.
   • docker exec -it nfhm_devcontainer-postgres-1 bash
   • psql -U postgres -d nfhm -f /tmp/import.pgsq
5. From a new terminal tab in the dev container, run bin/dev
6. Navigate to http://localhost:3000 in your browser

For optimal portability, this app uses Dev Containers to configure and manage the development environment. This means any developer with Docker installed and an appropriate IDE (e.g., VSCode, GitHub Codespaces, a JetBrains IDE if you like debugging) or the Dev Container CLI should be able to get this project running locally in just a few steps.

To run locally:

1. Open the repository in a devcontainer. Here's an example with VSCode using the VSCode Dev Container extension. From the command palette (CMD+P on MacBooks), type Dev Containers: Reopen in Container:

2. (SUBJECT TO CHANGE): run bin/dev to start the python backend.

3. Visit http://localhost:8000/

4. (SUBJECT TO CHANGE) Here is a mock screenshot of how you can expect the website to look:

5. Next you'll need to import data.

   • Import the raw data into Mongo
   • Running the vector embedder job

This project's dev container runs a docker image of jupyter notebooks at http://localhost:8888. The /work/ (fullpath: /home/jovyan/work/) directory of this container is mounted to this repository on your local filesystem at ./NFHM/jupyter-workpad so you can check in your notebooks to version control.

Alternatively, you can use a local installation of Jupyter if you prefer. Regardless, by convention, check your work into the ./jupyter-workpad subdirectory.

We use Mongo to house the raw data we import from iDigBio, GBIF, and any other external sources. We use Redis as our queueing backend. To seed your local environment with a sample of data to work with, you'll need to first follow the instructions above for local setup.

1. From within a dev container: $ bin/ingest_idigbio

2. Navigate in a browser to the Redis server via Redis Insight at http://localhost:8001, or connect to port 6379 via your preferred Redis client.

3. Decide what sample of data you want to query from iDigBio. For this example, we'll limit ourselves to records of the order lepidoptera (butterflies and related winged insects) with associated image data from the Yale Peabody Museum.

4. We'll LPUSH that query onto the idigbio queue from the Redis Insight workbench:

   LPUSH idigbio '{"search_dict":{"order":"lepidoptera","hasImage":true,"data.dwc:institutionCode":"YPM"},"import_all":true}'
   

   • search_dict is the verbatim query passed to the iDigBio API. Consult the wiki and the github wiki for search options.
   • import_all is a optional param (default: False) that'll iteratre through all pages of results and import the raw data into Mongo. Otherwise, only the first page of results are fetched. Consequently, please be mindful when setting this param as there are a lot (~200 GB, not including media data) of records in iDigBio.
   • 

5. Navigate to Mongo Express (or use your preferred Mongo client) at http://localhost:8081 and navigate to the idigbio collection inside the NFHM database to see the imported data.

The basic process of seeding Mongo with raw GBIF data is essentially the same as with iDigBio. However, you'll need make sure you have the GBIF worker up-and-running in your dev container with the correct environment inputs:

• $ bin/ingest_gbif
• From the workbench of Redis Insight, pass a simple search string to the gbif queue:
  • LPUSH gbif "puma concolor"

Once we've imported raw-form data into Mongo, we'll want to generate vector embeddings for the data and store them to Postgres. This is where the web api serves query results from.

The process is very similar to importing data into Mongo. Again, if you've just started up the dev container, make sure to open a new terminal tab (assuming you're using VSCode) so that conda will init. Similarly, we can run a script to activate the embedder, or run it ourselves:

$ bin/ingest_embedder

$ bin/ingest_embed

As this ingestor is running, it is waiting a signal from the Redis queue to begin the embedding process. This will work very similarly to the gbif and idigbio queues above: From the workbench of Redis Insight, pass a simple search string to the embedder queue: LPUSH embedder '{}'

Postgres serves as the primary backend database for vector/embedding storage, as well as other backend storage critical to running and serving the app.

You can directly access the Postgres database from your local machine by connecting to port 5432 on localhost using username postgres and password postgres. For example, with Postico, you would:

This project uses Mongo to store raw data from iDigBio, GBIF, etc. This allows us to more readily run experiments with re-indexing, re-vectorizing/embedding, etc. without having to reach out across the internet to the canonical data sources everytime we want to re-access the same raw data.

Once you have your development environment running, you can access MongoDB locally by going to http://localhost:8081/. Alternatively, you can connect to port 27018 on localhost with your preferred Mongo client (e.g., mongosh). The local database is, unoriginally, named NFHM.

Redis -- as of this writing -- is used as a queueing backend during data ingestion and processing. In the future, we may use redis for other things, too.

To access the local Redis server with Redis Insight during development, navigate to http://localhost:8001/. You should also be able to directly connect your preferred Redis client (e.g., redis-cli) by directly connecting to your local host at the default Redis port 6379.

We expect to do a lot experiments that vary the content of the DB. Consequently, it's imperative to be able to share our exact data with each other. This way we can avoid repeating ourselves with the lengthy process of importing data from external sources and generating embeddings. You can use pg_dump to do so:

docker exec nfhm_devcontainer-postgres-1 bash -c "pg_dump -U postgres nfhm" > <FILE_NAME>.pgsql

And then zip it up and send.