Remove old code in radiative boundary condition in Boundary

Create issue
Issue #1391 closed
Frank Löffler created an issue

I stumbled across code which we should remove. I don't see anything using this particular feature, and never have. It was marked as 'to be deprecated' 10 years ago.

Keyword:

Comments (7)

  1. Erik Schnetter
    • changed status to open
    • removed comment

    Approved.

    Does this invalidate any existing code, or existing test cases? We probably have some pre-MoL code left over.

    Does the documentation also need to be updated?

  2. Frank Löffler reporter
    • removed comment

    I didn't find the string "PREVIOUS_TIME_LEVEL" anywhere in my source checkout (which is larger than the ET), other than in this section of the code. The question here isn't about pre-MoL code. That is fine. The code in question looks for a possibility to declare which variable the previous timelevel of another variable is by table entry and name/index lookup, as opposed to the now used *_p naming scheme. Up to yesterday I didn't even know this possibility existed once. :)

  3. Erik Schnetter
    • removed comment

    Thorn ADM uses this scheme: it defines different variables for current and previous time levels.

    However, thorn ADM also uses the outdated API for thorn Boundary, so it does not use tables yet, and thus doesn't use "previous_time_level" either. Thorn ADM is too old to know about "previous_time_level", so yes, it can be safely removed...

  4. Roland Haas
    • removed comment

    This might be an reason to also retire ADM to CactusArchive since it is not used by anyone (as far as I know) and we were only keeping it around since some tests use it and re-writing the tests is more work than keeping ADM around?

  5. Frank Löffler reporter
    • changed status to resolved
    • removed comment

    Committed as of r319. As to ADM: yes, it should be archived at some point. However, this is not related to this issue, so I am closing nevertheless.

  6. Log in to comment