Skip to content

Elements table generator#25

Open
bmaranville wants to merge 1 commit intopython-periodictable:masterfrom
bmaranville:elements-table-generator
Open

Elements table generator#25
bmaranville wants to merge 1 commit intopython-periodictable:masterfrom
bmaranville:elements-table-generator

Conversation

@bmaranville
Copy link
Contributor

Moves the table generator from periodictable/nsf.py to here in standalone util/scattering_table_html.py utility.

Also adds lowercase element symbols as target tags, for compatibility with the old pages (and redirects).

Adds a scroll offset so the target element is properly in view.

@bmaranville bmaranville force-pushed the elements-table-generator branch from 08e0a44 to c3cda75 Compare February 27, 2026 21:39
@pkienzle
Copy link
Contributor

Add periodictable version number to the bottom of the table.

Put the table in the activation calculator html directory and link to it from the help text. I link to a resonances table from the "Source neutrons" help, so we could put it beside that.

Add the table deploy command to the pyodide deploy script.

Move scripts to a helper directory?

I would leave the table generation code in the periodictable repo, but I won't veto moving it.

@bmaranville
Copy link
Contributor Author

If we always deploy this and the activation calculator together, it just beomes one script, which is nice. The plan is to redirect pages like n-lengths/pt.html to scattering_table.html#pt

@pkienzle
Copy link
Contributor

If we link from the help, won't we need a deploy script for the table when setting up the flask version? The flask instructions will need to include this step.

The reason for keeping the html generation with periodictable is if we believe others will want to generate their own tables. If it is only needed for the activation pages then it doesn't matter where it lives.

@bmaranville
Copy link
Contributor Author

The use case for a custom table and the use case for embedding the activation calculator don't overlap, do they? I can't think of why we wouldn't link to a canonical URL for the scattering table instead of a local one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants