Contribute to Chip Atlas

Published visuals must be actual die micrographs or verified GDS files. Do not publish circuit graphs, pad plots, package photos, slides or traced-layer browsers. Add a source-URL review decision to 05_Chip_Visualizations/data/physical_visual_review.json and preserve credits and licenses. Historical drawing workflows below are private research only.

Keep claims traceable. Each annotation needs an original URL, image dimensions, approximate coordinates, description, and evidence class. Inspect the image before assigning a region.

Use visible label for text actually shown in the source, author identification for a reported interpretation, and inferred for an uncertain role or location. A physical feature can be visible while its function remains unknown.

Keep module and engine specifications separate from die specifications. Record units, direction, gross versus net rate, conditions, and power boundary. Leave missing values empty.

Edit the annotation data and catalog, then run the builders and checks listed in the README. Useful contributions include corrected chip identities, better original source links, verified operating specifications, and public layouts with clear redistribution licenses.

Do not commit local caches, papers, images, access tokens, or proprietary mask files. Label synthetic fixtures and keep them separate from catalog chip records.

Industry records and exact parts

Add source-backed commercial chip/model-family records in 02_Chip_Catalog/industry/. Keep identity, vendor, domain, category, record type, evidence URL, and review date. Use parts for source-listed exact codes beneath a named chip or family. Each part needs part_number, source_url, and code_kind: use ordering_part_number for a full manufacturer ordering code or vendor_model_number for a model identifier. Add model_number to an ordering-code record only when the source explicitly maps that code to the model. Keep unverified package and status null. Do not generate suffix combinations from an incomplete table.

Use reference_only when no visual is verified. Unannotated photographs use source_image; component-region annotations need their own evidence. A photograph is not GDSII geometry. Run the atlas builder, data validator, documentation builder, and site builder after changes. The coverage report and exact-part export are generated from those records.

Keep per-image creator, source-file page, license, dimensions, and any display changes. New interactive regions must follow inspected source evidence and remain within the image. Image-derived annotations follow the source image’s license where required. Link separately published interactive maps through interactive_maps with an attributed title, HTTPS URL, and specimen/revision limits; a link does not grant permission to copy map geometry.

Use published_coordinate only for positions explicitly listed in a source table. Retain signed values, units, symbols, the original coordinate strings, document identity, and a page locator for each pad. Keep unspecified pad reference points, rotations, and die-edge offsets null. Draw symbolic markers when these details are unknown. Edit 05_Chip_Visualizations/data/pad_map_sources.json, rebuild with python3 04_Collection_Tools/build_pad_maps.py, then run its --check mode and python3 05_Chip_Visualizations/tests/check_pad_maps.py before rebuilding the atlas.