Skip to content

Add METISSE for stellar evolution#1254

Open
rieder wants to merge 47 commits into
amusecode:mainfrom
rieder:add/metisse
Open

Add METISSE for stellar evolution#1254
rieder wants to merge 47 commits into
amusecode:mainfrom
rieder:add/metisse

Conversation

@rieder
Copy link
Copy Markdown
Member

@rieder rieder commented Apr 14, 2026

This PR adds METISSE (https://github.com/TeamMETISSE/METISSE) as a community code.
Still needs a way to download default stellar tracks but should otherwise work.

@rieder rieder requested a review from a team as a code owner April 14, 2026 15:13
@rieder rieder moved this from Backlog to Feature Request in Development Board Apr 14, 2026
@rieder rieder self-assigned this Apr 14, 2026
@rieder rieder added the area: community_code Issue concerns a community code and/or its AMUSE bindings label Apr 14, 2026
@LourensVeen LourensVeen moved this from Feature Request to Next up in Development Board Apr 28, 2026
Copy link
Copy Markdown
Member

@LourensVeen LourensVeen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking pretty good, but I have some comments. Also, it doesn't seem like there are any tests? Could we add at least some basic ones that instantiate the code, put some particles in, and do a simple calculation?

@@ -0,0 +1,44 @@
[project]
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There should not be a package here, just a forward in amuse/community/metisse/init.py and interface.py, like for the other codes.

@@ -0,0 +1,185 @@
import logging
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this go with the other examples in src/amuse/examples rather than here?

@@ -0,0 +1,259 @@
"""
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as for the other example

Comment thread src/amuse_metisse/README

Scientific papers written using this module should reference the paper

"Comprehensive analytic formulae for stellar evolution as a function
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have a mechanism for this, right? Should this go into the docstring in interface.py with the other references there?



# Downloading the code
##### Remove if not needed #####
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These ##### comments are intended to be removed once implemented.

@@ -0,0 +1 @@
fortran mpi No newline at end of file
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This needs download, tar, and gunzip for downloading and extracting.

RANLIB = @RANLIB@
DOWNLOAD = @DOWNLOAD@
TAR = @TAR@
UNZIP = @UNZIP@
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't need most of these.



# AMUSE framework libraries
STOPCOND_CFLAGS = @STOPCOND_CFLAGS@
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think adding stopping conditions is a planned extension? Then we could leave the applicable one. But we're probably not using AMUSE_MPI, SIMPLE_HASH, or G6LIB? Then those should be removed to avoid confusion.

# Find AMUSE libraries
AMUSE_LIB_STOPCOND()
AMUSE_LIB_STOPCONDMPI()
AMUSE_LIB_AMUSE_MPI()
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See comment on config.mk.in


##### Wrap these into language macros as needed #####
##### MPI is always needed to build the worker #####
AX_MPI()
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As the comment indicates, this goes in between the AC_LANG_PUSH and AC_LANG_POP macros to indicate that we want to use MPI from Fortran.

@github-project-automation github-project-automation Bot moved this from Next up to Open PRs in Development Board May 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: community_code Issue concerns a community code and/or its AMUSE bindings

Projects

Status: Open PRs

Development

Successfully merging this pull request may close these issues.

2 participants