Data

Tools

Indexes

Applications

Experiments

Open Source Science

https://github.com/afni/nifti_docs

NIFTI documentation

https://github.com/afni/nifti_docs

Science Score: 26.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • ○
    CITATION.cff file
  • ✓
    codemeta.json file
    Found codemeta.json file
  • ✓
    .zenodo.json file
    Found .zenodo.json file
  • ○
    DOI references
  • ○
    Academic publication links
  • ○
    Academic email domains
  • ○
    Institutional organization owner
  • ○
    JOSS paper metadata
  • ○
    Scientific vocabulary similarity
    Low similarity (9.7%) to scientific vocabulary
Last synced: 10 months ago · JSON representation

Repository

NIFTI documentation

Basic Info
  • Host: GitHub
  • Owner: afni
  • Language: Python
  • Default Branch: main
  • Size: 4.41 MB
Statistics
  • Stars: 0
  • Watchers: 11
  • Forks: 0
  • Open Issues: 0
  • Releases: 0
Created over 1 year ago · Last pushed 11 months ago
Metadata Files
Readme

README.md

README

What is this repository for?

  • This is a repository of Sphinx/RST files for building an HTML tree of NIfTI (Neuroimaging Informatics Technology Initiative) documentation notes.

Getting your Linux computer setup

  • You should have Python 3.[something] as your installed Python

  • Install Python dependencies. This can be done by:

    • installing Conda (e.g., Miniconda)
    • ... and then using the attached environment_sphinxdocs.yml file:

    conda env create -f environment_sphinxdocs.yml

Building Sphinx: converting RST -> HTML

  • In the main directory where you are editing files, type:

make html

  • To view the subsequent HTML tree, type:

firefox _build/html/index.html

  • Note for convenience, we have added a script called "dobuildniftidocsfrom_git.tcsh" that can be run to copy the git tree to a new location and build the current files that are in the "master" branch online.

    • I would recommend then editing files in that new ~/nifti_docs/ directory, and then just running "make html" there to see what your changes look like. When happy with the changes, then copy those into the main git repo, commit and push them. I find that a reasonable work flow.

Owner

  • Name: afni
  • Login: afni
  • Kind: organization

GitHub Events

Total
  • Push event: 14
Last Year
  • Push event: 14