Public-safe support

IT Help

Setup, publishing and research guides, written to be followed once from the top. Everything here is public guidance: no operator consoles, no infrastructure, no credential procedures.

Start here

A first working setup, in three steps. Each step stands on its own if you already have the ones before it.

  1. Set up Python, Jupyter and VS Code

    One environment workflow for Windows, macOS and Linux, with the two steps that actually differ called out.

  2. Choose a dependency profile

    Section 3 of the Script Library guide walks the choice between the core and full profiles, and the TensorFlow case.

  3. Install CodeSentinel and verify it

    Install from PyPI, from source, from a release artifact or from an offline wheelhouse, then confirm which package is active.

Set up and run

  • Virtual Environments, Jupyter and VS Code Beginner

    Create a project-local environment, register a Jupyter kernel, and point VS Code at it. One workflow, three operating systems.

  • Data Science Script Library Intermediate

    A catalog of data, notebook, documentation, plotting, machine-learning and repository-maintenance scripts, with worked examples and a guided dependency-profile choice.

  • CodeSentinel: Getting Started Beginner

    What the public repository contains, how it differs from the PyPI package, and which commands are safe to run first.

  • CodeSentinel: Installation Beginner

    Four ways to install, including offline, and how to verify the active package and its command surface afterwards.

Write and publish

  • Julia and Pluto Reference Intermediate

    Write, format and explain a Pluto notebook: Julia syntax, notebook Markdown, and the mathematics and interactivity that connect them.

  • Accessibility and Dyslexia-Friendly Publishing Everyone

    Structure a page so a dyslexic or tired reader can follow it the first time: layout, lists, links, notation, and a checklist to run before publishing.

Authorized security research

Both guides assume you have authorization for the system or exposure you are examining, and both keep their methods inside that boundary.

  • Dark-Web Forensics Investigation Guide Advanced

    Preserve evidence lawfully, analyse it within a stated scope, and report it defensibly, with a beginner primer on Tor for readers new to the ground.

  • Dorkit Defensive Research Guide Intermediate

    Review what public search reveals about your own systems, classify the exposure signals, and route each finding back to its source for remediation.

Class resources

  • UNC Data Science Notes Everyone

    Accessibility-first public class notes and practical resources from the UNC data science notes repository.

  • Notes support and corrections Everyone

    How to request a correction, ask for clarification, or suggest a topic the notes should cover.

All guides

Every IT Help guide, what it covers, and who it is written for.
Guide What it covers Written for
Virtual Environments, Jupyter and VS Code Project-local environment, Jupyter kernel, VS Code interpreter Beginner
Data Science Script Library Script catalog, worked examples, dependency profiles Intermediate
CodeSentinel: Getting Started Repository orientation and safe first commands Beginner
CodeSentinel: Installation PyPI, source, release artifact and offline installs, then verification Beginner
Julia and Pluto Reference Julia syntax, notebook Markdown, mathematics and interactivity Intermediate
Accessibility and Dyslexia-Friendly Publishing Readable structure, notation, and a pre-publishing checklist Everyone
Dark-Web Forensics Investigation Guide Evidence preservation, bounded analysis, defensible reporting Advanced
Dorkit Defensive Research Guide Public exposure review, signal classification, remediation routing Intermediate
UNC Data Science Notes Public class notes and practical resources Everyone
Notes support and corrections Corrections, clarifications and topic requests Everyone

Getting help

Two causes account for most setup failures, and both are covered above.

  • Installation errors

    Usually an interpreter mismatch, a stale virtual environment, or two Pythons on the same path. The environment guide shows how to confirm which interpreter is actually running.

  • Dependency confusion

    Pin and isolate dependencies in a project-local environment before re-running any setup step. The Script Library guide covers profile selection in section 3.

For anything in the class notes, including corrections and new topics, use the notes support page and include reproducible steps, your environment details, and the exact error output.