Output from SAVE XSPEC command is faulty in fork-based runs (trac #399)

[cloudy-bot]

reported by: peter

When using the SAVE XSPEC command in a fork-based grid run, the resulting FITS file will contain many blocks of only zeros. This is because the results are not communicated between the various forked instances of the code. MPI-based and sequential runs are fine. MPI-based runs use MPI_Reduce() to communicate the results. There is no equivalent for fork-based runs.

Migrated from https://www.nublado.org/ticket/399

{
    "status": "closed",
    "changetime": "2019-02-04T12:09:37Z",
    "_ts": "1549282177514312",
    "description": "When using the SAVE XSPEC command in a fork-based grid run, the resulting FITS file will contain many blocks of only zeros. This is because the results are not communicated between the various forked instances of the code. MPI-based and sequential runs are fine. MPI-based runs use MPI_Reduce() to communicate the results. There is no equivalent for fork-based runs.",
    "reporter": "peter",
    "cc": "",
    "resolution": "fixed",
    "time": "2017-08-25T07:48:06Z",
    "component": "output",
    "summary": "Output from SAVE XSPEC command is faulty in fork-based runs",
    "priority": "major",
    "keywords": "",
    "version": "trunk",
    "milestone": "c17.01",
    "owner": "peter",
    "type": "defect - wrong answer"
}

[cloudy-bot]

• @peter-van-hoof-noaccount commented:

Fixed in r11804 on the trunk and r11805 on c17_branch.

• @peter-van-hoof-noaccount changed resolution from "" to "fixed"
• @peter-van-hoof-noaccount changed status from "new" to "closed"

[cloudy-bot]

• @CloudyLex commented:

Milestone renamed

• @CloudyLex changed milestone from "c17.01 release" to "C17.01 release"

[cloudy-bot]

• @CloudyLex commented:

Milestone renamed

• @CloudyLex changed milestone from "C17.01 release" to "C17.01"

[cloudy-bot]

• @peter-van-hoof-noaccount commented:

Milestone renamed

• @peter-van-hoof-noaccount changed milestone from "C17.01" to "c17.01"