1 Introduction

Between 1966 and 1967, NASA sent five Lunar Orbiter spacecraft to map the Moon and pick safe landing sites for Apollo. Their cameras returned hundreds of frames that are still some of the most beautiful pictures of the lunar surface. The Lunar and Planetary Institute (LPI) keeps them online, frame by frame, with the metadata of every shot.

LUNAR-ORBITER-ATLAS is a local web app, written in Python with Dash and Plotly, that puts those photographs back where they were taken: on an interactive 3D Moon.

👉 https://github.com/EnriquePH/LUNAR-ORBITER-ATLAS

2 Features

• Mission mosaic. Every frame of the selected mission (890 frames over the five missions) is projected onto the part of the Moon it photographed and labelled with its frame ID.
• Picking photos. Click a photo, choose it from the selector, type its ID or press Random to show it in the side panel.
• Close-up navigation. Rotation and zoom slow down near the surface, and the camera can come down to about 17 km above it.
• Frame details. LPI preview, principal point, spacecraft altitude and position, illumination angles (sun azimuth, incidence, emission, phase), camera (80 mm or 610 mm) and ground footprint in km.
• Export. Download the loaded frames of a mission as CSV (metadata and geometry) or GeoJSON (projected footprints as polygons).
• Reference tabs. Short facts about the Moon and the Lunar Orbiter program, summarised from Wikipedia.
• English and Spanish. Switch with the ES | EN control, or open ?lang=en / ?lang=es.

3 How photos are placed

The interesting part is geometry. A photo is not just pasted on the globe: each frame is projected from the spacecraft. Every pixel becomes a ray that starts at the spacecraft position published by the LPI, goes through the camera aimed at the principal point, and lands where it meets the Moon. So oblique and high-altitude shots cover the area they really saw, and pixels that look past the limb are dropped.

The coordinate conversions are public, so they can be reused in other projects: selenographic_to_cartesian and cartesian_to_selenographic in orbiter.globe.

4 Installation

Requires Python ≥ 3.10, on Linux or macOS.

git clone https://github.com/EnriquePH/LUNAR-ORBITER-ATLAS.git
cd LUNAR-ORBITER-ATLAS
make install   # create .venv and install the app
make download  # optional: fetch all 890 photos now (MISSIONS="1 4" to limit)
make run       # start the app

Then open http://127.0.0.1:8050/. Without make:

python3 -m venv .venv
.venv/bin/python -m pip install -e .
.venv/bin/lunar-orbiter

The first time a mission is shown, the app downloads the LPI page and thumbnail of each frame (about 200 per mission) and caches them in data/lpi/, politely: three workers and at most four requests per second. Later runs work from disk.

5 Exported files

• CSV: one row per frame with the LPI metadata (principal point, spacecraft position, illumination angles, preview URL), plus camera, footprint_width_km, footprint_height_km, projected and implied_emission_angle.
• GeoJSON: a FeatureCollection with one polygon per frame, following the outline drawn on the globe. Coordinates are selenographic degrees, east and north positive, not WGS 84.

6 License

The code is distributed under the MIT License. LPI images and metadata belong to their respective owners, and the reference tabs summarise Wikipedia articles under CC BY-SA 4.0.

7 How to cite

ENERGYCODE (2026). Lunar Orbiter Atlas, version 1.0.0.
https://github.com/EnriquePH/LUNAR-ORBITER-ATLAS

For photographs or metadata, also cite the LPI Lunar Orbiter Photo Gallery and the frame record used.

8 Links

• GitHub - LUNAR-ORBITER-ATLAS
• Project page
• Changelog
• LPI - Lunar Orbiter Photo Gallery
• Wikipedia - Lunar Orbiter program

1 Introduction

PARI/GP is a computer algebra system designed for fast computations in number theory: factorizations, algebraic number theory, elliptic curves, modular forms and more. PARI-GP-ENGINE brings it to Quarto, so PARI/GP code can live in a Quarto document, run when the document is rendered, and show its results with proper syntax highlighting:

👉 https://github.com/oeistools/PARI-GP-ENGINE

The repository provides two parts that fit together but can be used apart:

2 Features

• Execution. {gp} cells run in one gp session per document, so state carries from cell to cell, exactly as it would at the gp prompt.
• Highlighting. The full function set of PARI/GP 2.17 is recognized out of the box.
• Figures. Plots exported as SVG become real Quarto figures, with captions and cross-references.
• Errors that behave. A PARI/GP error stops the render and tells you which cell failed, unless you asked for the error to be part of the document.

3 Installation

quarto add oeistools/PARI-GP-ENGINE

Requirements:

• Quarto ≥ 1.9, since engine extensions do not exist in earlier versions.
• PARI/GP ≥ 2.13, with the gp executable on your PATH. CI tests 2.13.3, 2.15.5 and 2.17.3.
• Linux and macOS are tested in CI; Windows is implemented but not tested.

4 Usage

Set engine: pari-gp in the front matter, then write {gp} cells:

---
title: "Mersenne factors"
engine: pari-gp
format: html
---

```{gp}
M = 2^101 - 1
factor(M)
```

5 A taste

Factoring for the first prime after :

p = nextprime(10^40)
factor(p - 1)

10000000000000000000000000000000000000121
[                      2 3]
[                      5 1]
[                     11 1]
[                     17 1]
[                  12973 1]
[             1821309023 1]
[56581485446137975519811 1]

The class number and regulator of :

K = bnfinit(x^3 - 2, 1);
[K.no, K.reg]

[1, 1.3473773483293841009181878914456530463]

And because the session persists, its fundamental units are still one cell away:

K.fu

[Mod(x - 1, x^3 - 2)]

6 License

PARI-GP-ENGINE is distributed under the MIT License. PARI/GP itself is GPL software by the PARI Group; since gp runs as an external program, its GPL does not reach the extension code.

7 Links

• GitHub - PARI-GP-ENGINE
• Documentation
• Get started
• Gallery
• PARI/GP home page

1 Introduction

The Online Encyclopedia of Integer Sequences (OEIS) is one of the most valuable mathematical resources on the web. OEIS.m is a multipurpose Wolfram Language package that brings OEIS data directly into Mathematica:

👉 https://github.com/EnriquePH/OEIS-Mathematica

This is version 3.1.0 of the package, a streamlined rewrite that queries the official OEIS JSON API instead of scraping HTML pages. It works on Wolfram Language 11, 13 and 14, keeps the public functions of the earlier package, and is now distributed as an installable Wolfram Language paclet.

2 Features

• Access to OEIS sequence metadata through the official JSON API
• Compatible with Wolfram Language 11, 13 and 14 (paclet installation needs 12.1+)
• Lightweight and easier to maintain than the previous HTML-based implementation
• Support for common package operations such as validation, import and export
• OEISbFile computes b-file terms beyond what OEIS has published, using a locally defined id[n_] := ..., as documented on the OEIS wiki page for this package

3 Installation

As a paclet (recommended, WL 12.1+):

PacletInstall["https://github.com/EnriquePH/OEIS-Mathematica/releases/latest/download/OEIS-3.1.0.paclet"]
Needs["OEIS`"]

Or, working from a local clone without installing anything:

PacletDirectoryLoad["/path/to/OEIS-Mathematica"]
Needs["OEIS`"]

Legacy Get, for older Wolfram Language versions or a single-file drop-in:

Get["/path/to/OEIS-Mathematica/OEIS.m"]

4 Quick start

Load the package in a Wolfram notebook with:

<<OEIS`

Example:

OEISImport["A000045", "Description"]

5 Documentation and tutorial

A full walkthrough with real, verified output is available at EnriquePH.github.io/OEIS-Mathematica and as a Function Index. The runnable, plain-script source for that tutorial is test/OEISTutorial.wl.

There is also a real Wolfram Notebook version, with the same live-executed output, plus a guide page and one reference page per function:

• Documentation/English/Tutorials/OEIS.nb
• Documentation/English/Guides/OEIS.nb
• Documentation/English/ReferencePages/Symbols/

The original package page, with its own usage examples, is on the OEIS wiki: User:Enrique Pérez Herrero/OEIS Package.

6 Testing

wolframscript -file Tests/RunTests.wls            # everything, incl. live OEIS API calls
wolframscript -file Tests/RunTests.wls --offline   # ID validation / URL building only

CI (.github/workflows/mathics-offline.yml) runs the ID-validation/URL-building subset on every push and pull request using Mathics3, a free, open-source Wolfram Language implementation, so it needs no Wolfram Engine license. It runs Tests/OfflineTests.mathics.wls, a hand-ported mirror of Tests/OfflineTests.wlt (Mathics3 doesn’t implement VerificationTest/TestReport or the live JSON API path, so the real .wlt suite and anything network-dependent still needs a licensed wolframscript, e.g. locally or in your own CI with WOLFRAMSCRIPT_ENTITLEMENTID configured).

7 License

The package is distributed under the GNU General Public License v3.0.

8 How to cite

If you use this package in a project or publication, please cite it using the metadata in CITATION.cff, which includes the archived Zenodo DOI: 10.5281/zenodo.21539225.

9 Links

• GitHub - OEIS-Mathematica
• Documentation and tutorial
• Function Index
• OEIS wiki page for this package
• CHANGELOG
• CONTRIBUTING
• Code of Conduct
• CITATION.cff
• DOI on Zenodo

1 Descripción

Explocal es una aplicación informática que calcula las principales características teóricas de una mezcla explosiva (calor y temperatura de explosión, velocidad y presión de detonación, balance de oxígeno, composición de los productos de explosión…) siguiendo el método simplificado de la norma española UNE 31-002. Se desarrolló en C++ (Borland C++ 3.1 + Object Windows 1.0) para Windows 3.1 en 1996, como Proyecto Fin de Carrera de Enrique Pérez Herrero (E.T.S.I. de Minas de Madrid, especialidad Laboreo y Explosivos).

El repositorio conserva el código y los datos originales de 1996 tal cual, y reconstruye la memoria completa del proyecto (texto, fórmulas, figuras, tablas y anexos con el código fuente) como libro digital, publicado en GitHub Pages.

2 Historia del proyecto

• 1996 — Proyecto Fin de Carrera original: memoria en papel/Word y aplicación EXPLOCAL.EXE en C++ para Windows 3.1.
• 2015-2016 — Primer intento de modernización: exploración de los ficheros *.DAT con R/ggplot, sin llegar a reimplementar el motor de cálculo.
• 2026 — Reconstrucción completa: la memoria original se transcribe y corrige como libro Markdown/Quarto, publicado en GitHub Pages; en paralelo se reimplementa el motor de cálculo en Python. El código C++ de 1996 se conserva sin modificar como referencia histórica.

3 Estructura del repositorio

• code/ — código fuente C++ original de 1996 (Borland C++ 3.1 + Object Windows 1.0), datos, recursos y el ejecutable EXPLOCAL.EXE compilado. Referencia histórica.
• site/ — la memoria (PFC) reconstruida como libro Markdown/Quarto: capítulos numerados, índices de figuras/tablas y los anexos originales. Se publica como web en GitHub Pages y también se compila a PDF/DOCX/LaTeX con pandoc.
• docs/ — documentos originales sin procesar (.DOC/LaTeX/Word de 1994-2015) de los que parte la reconstrucción de site/.
• catalog.json — índice machine-readable de todos los capítulos y anexos del libro (título, ruta y URL de cada uno) más los formatos disponibles (HTML/PDF/DOCX/LaTeX).

4 Estado actual

• ✅ Memoria completa reconstruida, corregida y publicada como libro web (HTML), y disponible en PDF/DOCX/LaTeX.
• ✅ Código y datos originales de 1996 preservados íntegros en code/.
• 🚧 Reimplementación en Python del motor de cálculo: en desarrollo.

5 Licencia

MIT © 1996 Enrique Pérez Herrero.

6 Cómo citar

Pérez Herrero, Enrique (1996). Proyecto de una aplicación informática
para el cálculo de las principales características teóricas de los
explosivos (Explocal). Proyecto Fin de Carrera, E.T.S.I. de Minas de
Madrid. https://enriqueph.github.io/EXPLOCAL/
DOI: 10.5281/zenodo.21306995

7 Enlaces

• GitHub - Explocal
• Libro / memoria del proyecto
• DOI en Zenodo

1 Volcanic Eruptions in the Holocene Period

1.1 Package installation

library(devtools)
devtools::install_github("EnriquePH/marketconf")

1.2 Examples

library(marketconf)
library(knitr)
kable(US_confidence_indices()[c(1, 3, 4)])

library(ggplot2)

index_symbol <- "USVI"
index_df <- get_index(index_symbol)

ggplot(index_df, aes(x = Date, y = USVI.Value, color = Investor)) +
  geom_line() +
  ggtitle(get_index_description(index_symbol))

1.3 License

The markerconf package is licensed under the MIT License (MIT), but the Stock Market Confidence Indexes are produced and copyrighted by the International Center of Finance at the Yale School of Management. Please refer to the TERMS OF USE on Yale University’s web page for further information.

1.4 Links

• Github marketconf R package