Skip to main content

Search the portfolio

33 matches · showing 7

11 choices. A body of work. A web of ideas.

Skip to case study
Evelyna Bellamy
Auto · Daylight
Time of day

Following your local clock · Daylight

Warm ivory · charcoal · open sky

Local time, no location access. Choose a stop to keep that atmosphere.

Computational astronomy & interactive research

Lunologium

A living atlas of
the Earth–Moon system.

An independent platform connecting celestial calculations, lunar cartography, research, and developer tools through interfaces you can explore.

A slower way
to notice time.
New
First quarter
Full
Last quarter
Illustrative portrait · drag to turn · not today’s illumination
NASA / LROC image source ↓
My role
Creator, Systems Architect, Full-Stack Developer
Project
Independent product / public platform
Focus
Computation → visualization → exploration

01 / A connected platform

One system.
Several ways to understand it.

The calendar is one entrance, not the extent of the work. The platform moves between time, place, explanation, and reuse.

I

Time & motion

Calendar, orbital cycles, libration and eclipse tools.

Change a date
II

Surface & place

Optical cartography, named features and coordinate-based inspection.

Inspect the atlas
III

Research & method

Research literature, computational documentation and the limits of each model.

Explore the research
IV

Data & reuse

Calculation modules, public API documentation, embeds and machine-facing tools.

Follow a calculation

The design challenge

Depth without
an entrance exam.

A phase, a place on the Moon, and an orbital cycle describe different things. The interface needs to connect them without making them interchangeable.

I designed multiple levels of entry: a readable first observation, an instrument to test it, and a method to inspect when you want to go further.

02 / Time becomes tangible

Change the date.
Watch the system respond.

The Moon, calendar, numerical reading, and clock share one selected date. An interaction exposes the relationship more clearly than a still image can.

The orbital clock

One Moon.
Five different cycles.

A month depends on what you measure against: the Sun, the stars, the orbital nodes, or the Moon’s closest approach. Select a cycle to follow its rhythm.

A working excerpt of the product’s clock. Local source, not a screenshot or remote embed.

01 / The orbital clock
Drag to turn the instrument
Five reference frames. No single lunar month.Select a cycle to isolate it
26 Sept 2026 · 12:00 UTC
Jan — Dec 2026

Product clock model · mean cycles, not orbital paths or an eclipse prediction. Radii are schematic; the globe uses fixed study lighting.

02 / A date, in detail
LROC optical mosaic · spherical projection

Calculated here · 12:00 UTC

26 Sept 2026

Full Moon

Illuminated
99.9%
Distance / Greenwich observer
383,967 km

The date also updates the clock above and the calculation trace below. North-up illustration with computed libration; not your local sky orientation.

September 2026Select a day to inspect it

Evidence / Working source excerpt

One date across several instruments

Decision Share the selected day while preserving the distinction between mean orbital cycles and the calculated daily reading.

Inspect the clock and calendar
How to inspect: One date across several instruments
  1. Set the observation date to 2026-01-01. Compare the selected calendar day with the date in the clock and the calculation payload under ‘Under the interface’.
  2. Select Draconic in the clock: its label reports a 27.21222-day mean period. This is a different quantity from the calendar’s illumination reading.
  3. Enlarge the clock, advance one day, then close it. The page retains that date; enlargement does not create a separate instrument state.
Versioned instrument scope and adaptations

Limit Samples are fixed at 12:00 UTC in 2026. Mean cycle angles are not eclipse predictions, and the north-up Moon is not an observer’s local sky view.

01 One date drives several representations. The calendar’s phase symbols lead into a more detailed reading.

02 The renderer uses the product’s calculation modules, with a fixed noon-UTC sample and a clearly named observer.

Image & source record · NASA / LROC

Ernie Wright / NASA Scientific Visualization Studio, CGI Moon Kit · SVS 4720 ↗. LROC WAC color mosaic, NASA / GSFC and Arizona State University. Public domain.

Mapped onto a sphere with illustrative lighting; not a photograph of the selected day or a terrain-height model. All imagery and calculations in these exhibits are served locally.

Versioned source files, adaptations and texture hash ↗

03 / From time to terrain

A world to inspect.
Not just an image to admire.

Select a named feature, center it, and add the coordinate grid. A surface becomes useful when you can connect what you see to where it is.

03 / The optical atlas
N / LUNAR NORTH
LROC optical mosaic · spherical projection

Selected surface feature / Crater

Copernicus

9.62° N · 20.08° W

A terraced impact crater within Oceanus Procellarum, with a conspicuous ray system.

Catalogue diameter 93 km

Six entries from the product catalogue, not a complete IAU database. Markers are symbolic, not feature outlines. Fixed study light; no elevation, temperature or gravity raster.

Evidence / Working source excerpt

A named feature has a location

Decision Connect a catalogue choice to coordinates and a centered optical view so the reader can locate the feature being discussed.

Inspect the optical atlas
How to inspect: A named feature has a location
  1. Select Tycho in the feature catalogue. Check the displayed 43.31° S, 11.36° W coordinates, then choose ‘Center selected feature’.
  2. Turn on ‘Coordinate grid’, then select Plato and center it. Compare the changed label and location; the grid supplies orientation rather than a measurement of relief.
Catalogue selection and image record

Limit Six catalogue entries sit over an optical mosaic. Markers are symbolic; neither their shapes nor the fixed lighting represent measured elevation, temperature, or gravity.

The same product renderer, in a different mode. Location, catalogue selection and optical imagery meet in one inspectable view. Image source ↑

Explore the full atlas

04 / Under the interface

Follow the reading
back to its method.

The calculation is not trapped inside the picture. Select a value to see how the platform turns a method into an interface—and data another tool can use.

01 / Calculation

A named method.

Illumination(Body.Moon, time)

Astronomy Engine 2.1.19, through the platform’s ephemeris module.

02 / Interface

99.9%

A fraction becomes a readable percentage and controls the rendered terminator.

03 / Reusable data

{
  "timestamp": "2026-09-26T12:00:00.000Z",
  "illuminationFraction": 0.999,
  "isWaxing": true
}

Local result excerpt; not a request to the public API.

Evidence / Working source excerpt

A displayed value has a method

Decision Keep the calculation name, readable value, and result payload together so the assumptions remain available at the point of inspection.

Inspect the calculation trace
How to inspect: A displayed value has a method
  1. Select Distance. Compare the kilometre value with distanceKm in the payload and inspect the observer fields: latitude 51.4769, longitude -0.0005, elevation 46 metres.
  2. Return to the calendar and change the day. Revisit the trace: its timestamp follows the selected date while the Greenwich observer stays fixed.
  3. Select Illumination. Compare the displayed percentage with illuminationFraction in the payload; the interface rounds the percentage to one decimal place.
Source versions and calculation boundaries

Limit The payload is a local result excerpt, not a public API response. This demonstrates traceability within the implementation, not an independent validation of astronomical accuracy.

A system decision

Shared calculation.
Purposeful views.

The clock compares mean cycles; the selected-day view calculates an ephemeris. Naming that distinction avoids making a beautiful diagram look more precise than its model.

An editorial decision

Observation is not
interpretation.

Calculated readings, research material, and reflective almanac notes have different evidential roles. The product gives them separate labels and places, rather than blending them into a single claim.

Read the methodology

05 / Project record

Keep the work.
Keep its context.

The interactive exhibits are bounded, locally hosted source excerpts. The earlier captures remain available as a historical record—not the main way to experience the work.

Historical interface captures Five views / 25 Sept 2026
Lunar calendar
Selected-day reading
Observation and almanac notes
Computational methodology
Lunar surface atlas
Original capture states and hashes
Implementation, provenance & scope

These exhibits use versioned copies of Lunologium’s clock model, ephemeris module, projection geometry, and WebGL renderer. Controls and composition are adapted for this case study. They do not depend on the live site staying online.

The 2026 date range samples each day at 12:00 UTC. The ephemeris fixes the observer at Greenwich (51.4769° N, 0.0005° W, elevation 46 m). Distance is observer-relative; the Moon illustration is lunar-north-up, not a view from that local horizon. Mean clock cycles are not eclipse predictions.

The atlas exposes six product catalogue entries and the optical mosaic. It does not present conceptual temperature or gravity illustrations as measured rasters. Role credit follows the existing portfolio record; no independent user, accuracy, or business-outcome claims are added.

Versioned instrument record ↗

An inviting surface. A substantial system underneath.

Complexity worth exploring.
Not hiding.