Skip to content

end-to-end-jupyterhub.md

Latest commit

 

History

History
95 lines (55 loc) · 2.91 KB

end-to-end-jupyterhub.md

File metadata and controls

95 lines (55 loc) · 2.91 KB

End-to-end JupyterHub tutorial

In this tutorial, you will open JupyterHub and run a notebook that calls deployed CogStack CE services.

By the end, you will have completed an end-to-end user flow:

  1. Open JupyterHub
  2. Log in
  3. Open the bundled tutorial notebook
  4. Run cells that call MedCAT and AnonCAT service APIs
  5. Inspect the outputs

!!! tip The following tutorial will use your CogStack CE installation and let you run real code against your environment.

To see a non-interactive version of the tutorial notebook, refer to [the MedCAT Service Tutorial notebook](../../platform/cogstack-ai/medcat-service-tutorial.ipynb).

Before you start

Make sure your CogStack CE release is installed and local port-forwarding is running.

If needed, re-run:

helm get notes <release> | bash

Replace <release> with your Helm release name (for example, cogstack).

Step 1: Open JupyterHub

Open:

This should show the JupyterHub login page.

Step 2: Log in

The community chart uses a dummy authenticator (for local/non-production use).

Log in with:

  • Username: admin
  • Password: SuperSecret

After login, JupyterLab opens for your user.

Step 3: Open the bundled notebook

The chart includes an example notebook:

  • medcat-service-tutorial.ipynb

You can open it directly:

Or navigate to it in JupyterLab and click to open it.

Step 4: Run the notebook cells

Run each cell in order from top to bottom.

The notebook demonstrates service calls to:

  • medcat-service at /api/process for named entity extraction
  • anoncat-service at /api/process for de-identification

It uses environment variables for service URLs where available, so the default CogStack CE setup should work without edits.

Step 5: Verify the end-to-end outputs

As you run cells, confirm that:

  • MedCAT returns annotation output for the sample text
  • AnonCAT returns de-identified output
  • The JSON responses are displayed in the notebook

If those outputs appear, you have validated the full end-to-end flow from JupyterHub to deployed CogStack CE services.

Troubleshooting

  • If JupyterHub does not load, ensure port-forwarding is running.

  • If notebook requests fail, verify the cluster services are up and re-run:

    • helm get notes <release> | bash

  • For production deployments, replace dummy authentication with secure auth configuration.

Next Steps