📥 Inbound Notifications 669

Time â–¾ Id From To Type Content
2026-04-05 07:02:29 urn:uuid:bb1bef9a-efd2-48ac-8cf2-b1c6629b7af9 https://datalake.inria.fr https://inria.hal.science ["Offer","coar-notify:ReviewAction"]
{
    "@context": [
        "https://www.w3.org/ns/activitystreams",
        "https://purl.org/coar/notify"
    ],
    "id": "urn:uuid:bb1bef9a-efd2-48ac-8cf2-b1c6629b7af9",
    "type": [
        "Offer",
        "coar-notify:ReviewAction"
    ],
    "actor": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "name": "Inria DataLake"
    },
    "origin": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "inbox": "https://prod-datadcis-api.inria.fr/coar/inbox"
    },
    "target": {
        "id": "https://inria.hal.science",
        "type": "Service",
        "inbox": "https://inbox.hal.science"
    },
    "object": {
        "id": "https://hal.science/hal-04951649v1",
        "ietf:cite-as": null,
        "sorg:citation": {
            "@context": "https://doi.org/10.5063/schema/codemeta-2.0",
            "type": "SoftwareSourceCode",
            "name": "Columbus",
            "codeRepository": null,
            "referencePublication": null
        },
        "mentionType": "software",
        "mentionContext": [
            "For the quantification, cells were acquired with a 40x objective and analyzed using Columbus software (Perkin Elmer)."
        ]
    }
}
2026-04-05 07:02:29 urn:uuid:977c8509-c9d9-4a82-bff8-a3870efcf7f3 https://datalake.inria.fr https://inria.hal.science ["Offer","coar-notify:ReviewAction"]
{
    "@context": [
        "https://www.w3.org/ns/activitystreams",
        "https://purl.org/coar/notify"
    ],
    "id": "urn:uuid:977c8509-c9d9-4a82-bff8-a3870efcf7f3",
    "type": [
        "Offer",
        "coar-notify:ReviewAction"
    ],
    "actor": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "name": "Inria DataLake"
    },
    "origin": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "inbox": "https://prod-datadcis-api.inria.fr/coar/inbox"
    },
    "target": {
        "id": "https://inria.hal.science",
        "type": "Service",
        "inbox": "https://inbox.hal.science"
    },
    "object": {
        "id": "https://hal.science/hal-04951649v1",
        "ietf:cite-as": null,
        "sorg:citation": {
            "@context": "https://doi.org/10.5063/schema/codemeta-2.0",
            "type": "SoftwareSourceCode",
            "name": "script from",
            "codeRepository": null,
            "referencePublication": null
        },
        "mentionType": "software",
        "mentionContext": [
            "Each sample was then demultiplexed using a specific python script from the FourCSeq R package    thus assigning each read to a specific viewpoint based to its primer sequence into separate fastQ files."
        ]
    }
}
2026-04-05 07:02:29 urn:uuid:4e0da13f-818b-46c1-a972-5868b6f062b7 https://datalake.inria.fr https://inria.hal.science ["Offer","coar-notify:ReviewAction"]
{
    "@context": [
        "https://www.w3.org/ns/activitystreams",
        "https://purl.org/coar/notify"
    ],
    "id": "urn:uuid:4e0da13f-818b-46c1-a972-5868b6f062b7",
    "type": [
        "Offer",
        "coar-notify:ReviewAction"
    ],
    "actor": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "name": "Inria DataLake"
    },
    "origin": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "inbox": "https://prod-datadcis-api.inria.fr/coar/inbox"
    },
    "target": {
        "id": "https://inria.hal.science",
        "type": "Service",
        "inbox": "https://inbox.hal.science"
    },
    "object": {
        "id": "https://hal.science/hal-04951649v1",
        "ietf:cite-as": null,
        "sorg:citation": {
            "@context": "https://doi.org/10.5063/schema/codemeta-2.0",
            "type": "SoftwareSourceCode",
            "name": "R script",
            "codeRepository": null,
            "referencePublication": null
        },
        "mentionType": "software",
        "mentionContext": [
            "A custom R script (https://github.com/bbcf/  bbcfutils/blob/master/R/smoothData.R)    was used to build the coverage file in bedGraph format, to normalize using the average coverage and to exclude the nearest region from each viewpoint (viewpoint-containing restriction fragment and the two adjacent restriction fragments)."
        ]
    }
}
2026-04-05 07:02:29 urn:uuid:38b41d16-a2a2-4d48-aaab-c1ea41e051f5 https://datalake.inria.fr https://inria.hal.science ["Offer","coar-notify:ReviewAction"]
{
    "@context": [
        "https://www.w3.org/ns/activitystreams",
        "https://purl.org/coar/notify"
    ],
    "id": "urn:uuid:38b41d16-a2a2-4d48-aaab-c1ea41e051f5",
    "type": [
        "Offer",
        "coar-notify:ReviewAction"
    ],
    "actor": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "name": "Inria DataLake"
    },
    "origin": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "inbox": "https://prod-datadcis-api.inria.fr/coar/inbox"
    },
    "target": {
        "id": "https://inria.hal.science",
        "type": "Service",
        "inbox": "https://inbox.hal.science"
    },
    "object": {
        "id": "https://hal.science/hal-04951649v1",
        "ietf:cite-as": null,
        "sorg:citation": {
            "@context": "https://doi.org/10.5063/schema/codemeta-2.0",
            "type": "SoftwareSourceCode",
            "name": "Tiling Affymetrix Software (TAS)",
            "codeRepository": null,
            "referencePublication": null
        },
        "mentionType": "software",
        "mentionContext": [
            "Scanned array data were normalized using Tiling Affymetrix Software (TAS) (quantile normalization, scale set to 500) and analyzed as described in       and converted to.wig files using R/Bioconductor software, when necessary, for visualization using the Integrated Genome Browser (bioviz.org)."
        ]
    }
}
2026-04-05 07:02:29 urn:uuid:1c6f8a1a-0bf5-4505-9651-1dfec090a97f https://datalake.inria.fr https://inria.hal.science ["Offer","coar-notify:ReviewAction"]
{
    "@context": [
        "https://www.w3.org/ns/activitystreams",
        "https://purl.org/coar/notify"
    ],
    "id": "urn:uuid:1c6f8a1a-0bf5-4505-9651-1dfec090a97f",
    "type": [
        "Offer",
        "coar-notify:ReviewAction"
    ],
    "actor": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "name": "Inria DataLake"
    },
    "origin": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "inbox": "https://prod-datadcis-api.inria.fr/coar/inbox"
    },
    "target": {
        "id": "https://inria.hal.science",
        "type": "Service",
        "inbox": "https://inbox.hal.science"
    },
    "object": {
        "id": "https://hal.science/hal-04951649v1",
        "ietf:cite-as": null,
        "sorg:citation": {
            "@context": "https://doi.org/10.5063/schema/codemeta-2.0",
            "type": "SoftwareSourceCode",
            "name": "Samtools",
            "codeRepository": null,
            "referencePublication": null
        },
        "mentionType": "software",
        "mentionContext": [
            "Samtools was used for sorting and indexing, and reads mapped to the mouse genome were used as a normalization factor, as in    and using the following formula."
        ]
    }
}
2026-04-05 07:02:29 urn:uuid:15e6675d-662c-4028-bc02-17e0dfb91128 https://datalake.inria.fr https://inria.hal.science ["Offer","coar-notify:ReviewAction"]
{
    "@context": [
        "https://www.w3.org/ns/activitystreams",
        "https://purl.org/coar/notify"
    ],
    "id": "urn:uuid:15e6675d-662c-4028-bc02-17e0dfb91128",
    "type": [
        "Offer",
        "coar-notify:ReviewAction"
    ],
    "actor": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "name": "Inria DataLake"
    },
    "origin": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "inbox": "https://prod-datadcis-api.inria.fr/coar/inbox"
    },
    "target": {
        "id": "https://inria.hal.science",
        "type": "Service",
        "inbox": "https://inbox.hal.science"
    },
    "object": {
        "id": "https://hal.science/hal-04951649v1",
        "ietf:cite-as": null,
        "sorg:citation": {
            "@context": "https://doi.org/10.5063/schema/codemeta-2.0",
            "type": "SoftwareSourceCode",
            "name": "Image Lab Touch",
            "codeRepository": null,
            "referencePublication": null
        },
        "mentionType": "software",
        "mentionContext": [
            "Pictures of the membranes were acquired with the ChemiDoc\u2122 Touch Imaging System and were visualized using Image Lab Touch software."
        ]
    }
}
2026-04-05 07:02:29 urn:uuid:11793604-a477-435e-be0a-15e9a8dfd06d https://datalake.inria.fr https://inria.hal.science ["Offer","coar-notify:ReviewAction"]
{
    "@context": [
        "https://www.w3.org/ns/activitystreams",
        "https://purl.org/coar/notify"
    ],
    "id": "urn:uuid:11793604-a477-435e-be0a-15e9a8dfd06d",
    "type": [
        "Offer",
        "coar-notify:ReviewAction"
    ],
    "actor": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "name": "Inria DataLake"
    },
    "origin": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "inbox": "https://prod-datadcis-api.inria.fr/coar/inbox"
    },
    "target": {
        "id": "https://inria.hal.science",
        "type": "Service",
        "inbox": "https://inbox.hal.science"
    },
    "object": {
        "id": "https://hal.science/hal-04951649v1",
        "ietf:cite-as": null,
        "sorg:citation": {
            "@context": "https://doi.org/10.5063/schema/codemeta-2.0",
            "type": "SoftwareSourceCode",
            "name": "R/Bioconductor",
            "codeRepository": null,
            "referencePublication": null
        },
        "mentionType": "software",
        "mentionContext": [
            "Scanned array data were normalized using Tiling Affymetrix Software (TAS) (quantile normalization, scale set to 500) and analyzed as described in       and converted to.wig files using R/Bioconductor software, when necessary, for visualization using the Integrated Genome Browser (bioviz.org)."
        ]
    }
}
2026-04-05 07:02:28 urn:uuid:f576fa8c-caf8-40b3-9846-4394e573f9f8 https://datalake.inria.fr https://inria.hal.science ["Offer","coar-notify:ReviewAction"]
{
    "@context": [
        "https://www.w3.org/ns/activitystreams",
        "https://purl.org/coar/notify"
    ],
    "id": "urn:uuid:f576fa8c-caf8-40b3-9846-4394e573f9f8",
    "type": [
        "Offer",
        "coar-notify:ReviewAction"
    ],
    "actor": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "name": "Inria DataLake"
    },
    "origin": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "inbox": "https://prod-datadcis-api.inria.fr/coar/inbox"
    },
    "target": {
        "id": "https://inria.hal.science",
        "type": "Service",
        "inbox": "https://inbox.hal.science"
    },
    "object": {
        "id": "https://hal.science/hal-04951649v1",
        "ietf:cite-as": null,
        "sorg:citation": {
            "@context": "https://doi.org/10.5063/schema/codemeta-2.0",
            "type": "SoftwareSourceCode",
            "name": "bedGraphToBigWig",
            "codeRepository": null,
            "referencePublication": null
        },
        "mentionType": "software",
        "mentionContext": [
            "Then the bedGraph file was converted in a BigWig file using bedGraphToBigWig program from UCSC."
        ]
    }
}
2026-04-05 07:02:24 urn:uuid:570cb3f8-0c26-4802-b445-e5c75297b176 https://datalake.inria.fr https://inria.hal.science ["Offer","coar-notify:ReviewAction"]
{
    "@context": [
        "https://www.w3.org/ns/activitystreams",
        "https://purl.org/coar/notify"
    ],
    "id": "urn:uuid:570cb3f8-0c26-4802-b445-e5c75297b176",
    "type": [
        "Offer",
        "coar-notify:ReviewAction"
    ],
    "actor": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "name": "Inria DataLake"
    },
    "origin": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "inbox": "https://prod-datadcis-api.inria.fr/coar/inbox"
    },
    "target": {
        "id": "https://inria.hal.science",
        "type": "Service",
        "inbox": "https://inbox.hal.science"
    },
    "object": {
        "id": "https://hal.science/hal-04473243v1",
        "ietf:cite-as": null,
        "sorg:citation": {
            "@context": "https://doi.org/10.5063/schema/codemeta-2.0",
            "type": "SoftwareSourceCode",
            "name": "Original",
            "codeRepository": null,
            "referencePublication": null
        },
        "mentionType": "software",
        "mentionContext": [
            "set Test set \u03b8 PQ SQ RQ PQ SQ RQ U-Net Original 0.9 34.8 80.5 43.3 8.1 78.2 10.4 HED Original 0.3 23.2 76.5 30.3 14.0 74.8 18.8 HED* Original 0.7 27.6 77.6 35.6 16.2 76.1 21.3 BDCN Original 0.9 27.7 80.6 34.4 10.2 80.4 12.7 BDCN* Original 0.8 27.6 82.1 33.7 8.9 82.8 10.7 U-Net Proposed 0.5 46.8 87.5 53.5 41.2 85.4 48.2 HED Proposed 0.5 52.2 86.8 60.2 42.7 85.2 50.1 HED* Proposed 0.5 32.4 87.0 37.3 44.5 85.2 52.3 BDCN Proposed 0.5 51.4 86.5 59.5 43.4 85.2 50.9 BDCN* Proposed 0.5 55.7 87.0 64.0 41.4 86.1 48.1 https://doi.org/10.1371/journal.pone.0298217.t003",
            "The training configuration from [5] is indicated as \"Original\" while our proposed method is indicated as \"Proposed\".",
            "The training configuration from [5] is indicated as \"Original\", while our proposed method is indicated as \"Proposed\".",
            "set Test set \u03b8 PQ SQ RQ PQ SQ RQ U-Net Original 0.9 34.8 80.5 43.3 8.1 78.2 10.4 HED Original 0.3 23.2 76.5 30.3 14.0 74.8 18.8 HED* Original 0.7 27.6 77.6 35.6 16.2 76.1 21.3 BDCN Original 0.9 27.7 80.6 34.4 10.2 80.4 12.7 BDCN* Original 0.8 27.6 82.1 33.7 8.9 82.8 10.7 U-Net Proposed 0.5 46.8 87.5 53.5 41.2 85.4 48.2 HED Proposed 0.5 52.2 86.8 60.2 42.7 85.2 50.1 HED* Proposed 0.5 32.4 87.0 37.3 44.5 85.2 52.3 BDCN Proposed 0.5 51.4 86.5 59.5 43.4 85.2 50.9 BDCN* Proposed 0.5 55.7 87.0 64.0 41.4 86.1 48.1 https://doi.org/10.1371/journal.pone.0298217.t003",
            "set Test set \u03b8 PQ SQ RQ PQ SQ RQ U-Net Original 0.9 34.8 80.5 43.3 8.1 78.2 10.4 HED Original 0.3 23.2 76.5 30.3 14.0 74.8 18.8 HED* Original 0.7 27.6 77.6 35.6 16.2 76.1 21.3 BDCN Original 0.9 27.7 80.6 34.4 10.2 80.4 12.7 BDCN* Original 0.8 27.6 82.1 33.7 8.9 82.8 10.7 U-Net Proposed 0.5 46.8 87.5 53.5 41.2 85.4 48.2 HED Proposed 0.5 52.2 86.8 60.2 42.7 85.2 50.1 HED* Proposed 0.5 32.4 87.0 37.3 44.5 85.2 52.3 BDCN Proposed 0.5 51.4 86.5 59.5 43.4 85.2 50.9 BDCN* Proposed 0.5 55.7 87.0 64.0 41.4 86.1 48.1 https://doi.org/10.1371/journal.pone.0298217.t003",
            "set Test set \u03b8 PQ SQ RQ PQ SQ RQ U-Net Original 0.9 34.8 80.5 43.3 8.1 78.2 10.4 HED Original 0.3 23.2 76.5 30.3 14.0 74.8 18.8 HED* Original 0.7 27.6 77.6 35.6 16.2 76.1 21.3 BDCN Original 0.9 27.7 80.6 34.4 10.2 80.4 12.7 BDCN* Original 0.8 27.6 82.1 33.7 8.9 82.8 10.7 U-Net Proposed 0.5 46.8 87.5 53.5 41.2 85.4 48.2 HED Proposed 0.5 52.2 86.8 60.2 42.7 85.2 50.1 HED* Proposed 0.5 32.4 87.0 37.3 44.5 85.2 52.3 BDCN Proposed 0.5 51.4 86.5 59.5 43.4 85.2 50.9 BDCN* Proposed 0.5 55.7 87.0 64.0 41.4 86.1 48.1 https://doi.org/10.1371/journal.pone.0298217.t003",
            "set Test set \u03c3 \u03b4 PQ SQ RQ PQ SQ RQ U-Net Proposed 50.0 8.0 59.8 87.7 68.2 46.7 86.9 53.7 HED Proposed 400.0 10.0 47.5 86.8 54.7 41.0 85.2 48.1 HED* Proposed 400.0 10.0 51.5 87.5 58.9 43.9 86.2 50.9 BDCN Proposed 400.0 10.0 48.9 86.9 56.3 41.3 85.8 48.1 BDCN* Proposed 400.0 10.0 54.7 88.6 61.7 46.4 87.1 53.3 U-Net Original 50.0 0.0 56.6 87.7 64.5 18.3 85.2 21.4 HED Original 200.0 10.0 50.5 87.2 57.9 35.6 84.6 42.0 HED* Original 300.0 8.0 52.8 87.6 60.3 38.4 85.5 44.9 BDCN Original 300.0 8.0 52.5 87.8 59.8 34.9 85.8 40.6 BDCN* Original 300.0 7.0 53.0 88.1 60.1 37.8 86.4 43.8 https://doi.org/10.1371/journal.pone.0298217.t004",
            "set Test set \u03c3 \u03b4 PQ SQ RQ PQ SQ RQ U-Net Proposed 50.0 8.0 59.8 87.7 68.2 46.7 86.9 53.7 HED Proposed 400.0 10.0 47.5 86.8 54.7 41.0 85.2 48.1 HED* Proposed 400.0 10.0 51.5 87.5 58.9 43.9 86.2 50.9 BDCN Proposed 400.0 10.0 48.9 86.9 56.3 41.3 85.8 48.1 BDCN* Proposed 400.0 10.0 54.7 88.6 61.7 46.4 87.1 53.3 U-Net Original 50.0 0.0 56.6 87.7 64.5 18.3 85.2 21.4 HED Original 200.0 10.0 50.5 87.2 57.9 35.6 84.6 42.0 HED* Original 300.0 8.0 52.8 87.6 60.3 38.4 85.5 44.9 BDCN Original 300.0 8.0 52.5 87.8 59.8 34.9 85.8 40.6 BDCN* Original 300.0 7.0 53.0 88.1 60.1 37.8 86.4 43.8 https://doi.org/10.1371/journal.pone.0298217.t004",
            "set Test set \u03c3 \u03b4 PQ SQ RQ PQ SQ RQ U-Net Proposed 50.0 8.0 59.8 87.7 68.2 46.7 86.9 53.7 HED Proposed 400.0 10.0 47.5 86.8 54.7 41.0 85.2 48.1 HED* Proposed 400.0 10.0 51.5 87.5 58.9 43.9 86.2 50.9 BDCN Proposed 400.0 10.0 48.9 86.9 56.3 41.3 85.8 48.1 BDCN* Proposed 400.0 10.0 54.7 88.6 61.7 46.4 87.1 53.3 U-Net Original 50.0 0.0 56.6 87.7 64.5 18.3 85.2 21.4 HED Original 200.0 10.0 50.5 87.2 57.9 35.6 84.6 42.0 HED* Original 300.0 8.0 52.8 87.6 60.3 38.4 85.5 44.9 BDCN Original 300.0 8.0 52.5 87.8 59.8 34.9 85.8 40.6 BDCN* Original 300.0 7.0 53.0 88.1 60.1 37.8 86.4 43.8 https://doi.org/10.1371/journal.pone.0298217.t004",
            "set Test set \u03c3 \u03b4 PQ SQ RQ PQ SQ RQ U-Net Proposed 50.0 8.0 59.8 87.7 68.2 46.7 86.9 53.7 HED Proposed 400.0 10.0 47.5 86.8 54.7 41.0 85.2 48.1 HED* Proposed 400.0 10.0 51.5 87.5 58.9 43.9 86.2 50.9 BDCN Proposed 400.0 10.0 48.9 86.9 56.3 41.3 85.8 48.1 BDCN* Proposed 400.0 10.0 54.7 88.6 61.7 46.4 87.1 53.3 U-Net Original 50.0 0.0 56.6 87.7 64.5 18.3 85.2 21.4 HED Original 200.0 10.0 50.5 87.2 57.9 35.6 84.6 42.0 HED* Original 300.0 8.0 52.8 87.6 60.3 38.4 85.5 44.9 BDCN Original 300.0 8.0 52.5 87.8 59.8 34.9 85.8 40.6 BDCN* Original 300.0 7.0 53.0 88.1 60.1 37.8 86.4 43.8 https://doi.org/10.1371/journal.pone.0298217.t004",
            "set Test set \u03c3 \u03b4 PQ SQ RQ PQ SQ RQ U-Net Proposed 50.0 8.0 59.8 87.7 68.2 46.7 86.9 53.7 HED Proposed 400.0 10.0 47.5 86.8 54.7 41.0 85.2 48.1 HED* Proposed 400.0 10.0 51.5 87.5 58.9 43.9 86.2 50.9 BDCN Proposed 400.0 10.0 48.9 86.9 56.3 41.3 85.8 48.1 BDCN* Proposed 400.0 10.0 54.7 88.6 61.7 46.4 87.1 53.3 U-Net Original 50.0 0.0 56.6 87.7 64.5 18.3 85.2 21.4 HED Original 200.0 10.0 50.5 87.2 57.9 35.6 84.6 42.0 HED* Original 300.0 8.0 52.8 87.6 60.3 38.4 85.5 44.9 BDCN Original 300.0 8.0 52.5 87.8 59.8 34.9 85.8 40.6 BDCN* Original 300.0 7.0 53.0 88.1 60.1 37.8 86.4 43.8 https://doi.org/10.1371/journal.pone.0298217.t004"
        ]
    }
}
2026-04-05 07:02:23 urn:uuid:f1211178-ddac-44ef-9976-c5c8b7d6e721 https://datalake.inria.fr https://inria.hal.science ["Offer","coar-notify:ReviewAction"]
{
    "@context": [
        "https://www.w3.org/ns/activitystreams",
        "https://purl.org/coar/notify"
    ],
    "id": "urn:uuid:f1211178-ddac-44ef-9976-c5c8b7d6e721",
    "type": [
        "Offer",
        "coar-notify:ReviewAction"
    ],
    "actor": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "name": "Inria DataLake"
    },
    "origin": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "inbox": "https://prod-datadcis-api.inria.fr/coar/inbox"
    },
    "target": {
        "id": "https://inria.hal.science",
        "type": "Service",
        "inbox": "https://inbox.hal.science"
    },
    "object": {
        "id": "https://hal.science/hal-02122167v1",
        "ietf:cite-as": null,
        "sorg:citation": {
            "@context": "https://doi.org/10.5063/schema/codemeta-2.0",
            "type": "SoftwareSourceCode",
            "name": "RevD",
            "codeRepository": null,
            "referencePublication": null
        },
        "mentionType": "software",
        "mentionContext": [
            "The Gaussian 09, RevD.01 software package     , was used for all calculations."
        ]
    }
}
2026-04-05 07:02:23 urn:uuid:03cd74bd-b7bb-4e31-8382-7d23c09a0e88 https://datalake.inria.fr https://inria.hal.science ["Offer","coar-notify:ReviewAction"]
{
    "@context": [
        "https://www.w3.org/ns/activitystreams",
        "https://purl.org/coar/notify"
    ],
    "id": "urn:uuid:03cd74bd-b7bb-4e31-8382-7d23c09a0e88",
    "type": [
        "Offer",
        "coar-notify:ReviewAction"
    ],
    "actor": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "name": "Inria DataLake"
    },
    "origin": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "inbox": "https://prod-datadcis-api.inria.fr/coar/inbox"
    },
    "target": {
        "id": "https://inria.hal.science",
        "type": "Service",
        "inbox": "https://inbox.hal.science"
    },
    "object": {
        "id": "https://hal.science/hal-02122167v1",
        "ietf:cite-as": null,
        "sorg:citation": {
            "@context": "https://doi.org/10.5063/schema/codemeta-2.0",
            "type": "SoftwareSourceCode",
            "name": "GaussView",
            "codeRepository": null,
            "referencePublication": null
        },
        "mentionType": "software",
        "mentionContext": [
            "The molecular surface plots were visualized by GaussView 6.0 program      and The AVOGADRO 1.2.0 molecular viewer     ."
        ]
    }
}
2026-04-05 07:02:20 urn:uuid:542d710f-af42-40bc-ba14-164c1d253c02 https://datalake.inria.fr https://inria.hal.science ["Offer","coar-notify:ReviewAction"]
{
    "@context": [
        "https://www.w3.org/ns/activitystreams",
        "https://purl.org/coar/notify"
    ],
    "id": "urn:uuid:542d710f-af42-40bc-ba14-164c1d253c02",
    "type": [
        "Offer",
        "coar-notify:ReviewAction"
    ],
    "actor": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "name": "Inria DataLake"
    },
    "origin": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "inbox": "https://prod-datadcis-api.inria.fr/coar/inbox"
    },
    "target": {
        "id": "https://inria.hal.science",
        "type": "Service",
        "inbox": "https://inbox.hal.science"
    },
    "object": {
        "id": "https://hal.science/hal-00397953v1",
        "ietf:cite-as": null,
        "sorg:citation": {
            "@context": "https://doi.org/10.5063/schema/codemeta-2.0",
            "type": "SoftwareSourceCode",
            "name": "AVIA",
            "codeRepository": null,
            "referencePublication": null
        },
        "mentionType": "software",
        "mentionContext": [
            "For video observations completed in Meudon or OHP, images were analyzed by completing Gaussian photometry with the AVIA software package                    ."
        ]
    }
}
2026-04-05 07:02:16 urn:uuid:fcf04b23-505b-4363-83f4-d7675a3518ce https://datalake.inria.fr https://inria.hal.science ["Offer","coar-notify:ReviewAction"]
{
    "@context": [
        "https://www.w3.org/ns/activitystreams",
        "https://purl.org/coar/notify"
    ],
    "id": "urn:uuid:fcf04b23-505b-4363-83f4-d7675a3518ce",
    "type": [
        "Offer",
        "coar-notify:ReviewAction"
    ],
    "actor": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "name": "Inria DataLake"
    },
    "origin": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "inbox": "https://prod-datadcis-api.inria.fr/coar/inbox"
    },
    "target": {
        "id": "https://inria.hal.science",
        "type": "Service",
        "inbox": "https://inbox.hal.science"
    },
    "object": {
        "id": "https://hal.science/hal-04739698v1",
        "ietf:cite-as": null,
        "sorg:citation": {
            "@context": "https://doi.org/10.5063/schema/codemeta-2.0",
            "type": "SoftwareSourceCode",
            "name": "OASIS3 MCT Fortran",
            "codeRepository": null,
            "referencePublication": null
        },
        "mentionType": "software",
        "mentionContext": [
            "As a consequence, it is not necessary to transform data in order to use it in the OASIS3 MCT Fortran library."
        ]
    }
}
2026-04-05 07:02:16 urn:uuid:e97fc708-d458-4813-b6e6-e4e34ce1396b https://datalake.inria.fr https://inria.hal.science ["Offer","coar-notify:ReviewAction"]
{
    "@context": [
        "https://www.w3.org/ns/activitystreams",
        "https://purl.org/coar/notify"
    ],
    "id": "urn:uuid:e97fc708-d458-4813-b6e6-e4e34ce1396b",
    "type": [
        "Offer",
        "coar-notify:ReviewAction"
    ],
    "actor": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "name": "Inria DataLake"
    },
    "origin": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "inbox": "https://prod-datadcis-api.inria.fr/coar/inbox"
    },
    "target": {
        "id": "https://inria.hal.science",
        "type": "Service",
        "inbox": "https://inbox.hal.science"
    },
    "object": {
        "id": "https://hal.science/hal-04739698v1",
        "ietf:cite-as": null,
        "sorg:citation": {
            "@context": "https://doi.org/10.5063/schema/codemeta-2.0",
            "type": "SoftwareSourceCode",
            "name": "National Center for Atmospheric Research Community Earth System Model (NCAR CESM",
            "codeRepository": null,
            "referencePublication": null
        },
        "mentionType": "software",
        "mentionContext": [
            "MCT has proven parallel performance and is, most notably, the underlying coupling software used in National Center for Atmospheric Research Community Earth System Model (NCAR CESM)."
        ]
    }
}
2026-04-05 07:02:16 urn:uuid:924e21bb-f731-40d8-a68c-8ab0f4ba0259 https://datalake.inria.fr https://inria.hal.science ["Offer","coar-notify:ReviewAction"]
{
    "@context": [
        "https://www.w3.org/ns/activitystreams",
        "https://purl.org/coar/notify"
    ],
    "id": "urn:uuid:924e21bb-f731-40d8-a68c-8ab0f4ba0259",
    "type": [
        "Offer",
        "coar-notify:ReviewAction"
    ],
    "actor": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "name": "Inria DataLake"
    },
    "origin": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "inbox": "https://prod-datadcis-api.inria.fr/coar/inbox"
    },
    "target": {
        "id": "https://inria.hal.science",
        "type": "Service",
        "inbox": "https://inbox.hal.science"
    },
    "object": {
        "id": "https://hal.science/hal-04739698v1",
        "ietf:cite-as": null,
        "sorg:citation": {
            "@context": "https://doi.org/10.5063/schema/codemeta-2.0",
            "type": "SoftwareSourceCode",
            "name": "ESMF",
            "codeRepository": null,
            "referencePublication": null
        },
        "mentionType": "software",
        "mentionContext": [
            "The MAPPING file must follow the SCRIPR format (see section 5.4) but can be generated by another library, for example ESMF or XIOS (see details in section 6.3.3).",
            "The regrid environment directory provides a practical example on how to calculate the regridding weight-and-address files with the SCRIP library but also with ESMF and XIOS, see section 6.3.3",
            "OASIS3-MCT supports different interpolation algorithms as described in chapter 4. Remapping files can be computed online using the SCRIP options, or offline using either the SCRIP, ESMF or XIOS (see examples/regrid environment, section 6.3.3) and read in during the run using the MAPPING transformation.",
            "The regrid environment directory offers a scripting environment to calculate the regridding weights and the regridding error for specific couple of grids and specific regridding algorithms with either the SCRIP library, ESMF or XIOS."
        ]
    }
}
2026-04-05 07:02:16 urn:uuid:805d12f0-1f77-4726-991e-d7b79a276bc8 https://datalake.inria.fr https://inria.hal.science ["Offer","coar-notify:ReviewAction"]
{
    "@context": [
        "https://www.w3.org/ns/activitystreams",
        "https://purl.org/coar/notify"
    ],
    "id": "urn:uuid:805d12f0-1f77-4726-991e-d7b79a276bc8",
    "type": [
        "Offer",
        "coar-notify:ReviewAction"
    ],
    "actor": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "name": "Inria DataLake"
    },
    "origin": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "inbox": "https://prod-datadcis-api.inria.fr/coar/inbox"
    },
    "target": {
        "id": "https://inria.hal.science",
        "type": "Service",
        "inbox": "https://inbox.hal.science"
    },
    "object": {
        "id": "https://hal.science/hal-04739698v1",
        "ietf:cite-as": null,
        "sorg:citation": {
            "@context": "https://doi.org/10.5063/schema/codemeta-2.0",
            "type": "SoftwareSourceCode",
            "name": "OASIS3-MCT",
            "codeRepository": null,
            "referencePublication": null
        },
        "mentionType": "software",
        "mentionContext": [
            "The OASIS3-MCT software comes without any warranties (implied or expressed) and is not guaranteed to work for you or on your computer.",
            "Since the OASIS3-MCT 4.0 release, OASIS3-MCT includes a mixed MPI+OpenMP parallel version of the SCRIP library for the calculation of the remapping weights (see section 4.3).",
            "The developers of the OASIS3-MCT software are researchers attempting to build a modular and userfriendly coupler accessible to the climate modelling community.",
            "8 keywords are used by OASIS3-MCT and 5 of these are optional :",
            "The information is written by OASIS3-MCT for each component and (optionnally) for each process.",
            "To interface a component code with OASIS3-MCT and use the module mod oasis (see section 2.2.1), it is required to include OASIS3-MCT modules from $ARCHDIR/include and link with appropriate libraries in $ARCHDIR/lib during the compilation and linking.",
            "\u2022 blank lines are supported, but only since OASIS3-MCT 4.0 version.",
            "This software and ancillary information called OASIS3-MCT is free software.",
            "This is equivalent to the bfb option in previous OASIS3-MCT versions.",
            "This is illustrated on figure 2.1 and how to use the OASIS3-MCT library accordingly is detailed on figure 2.2.",
            "(Note that north thresh was set to 1.45 in previous versions prior to OASIS3-MCT 4.0.)",
            "Instrumenting those toy models gives a practical experience of using the OASIS3-MCT library.",
            "6.4.1 Debug files If you experience problems while running your coupled model with OASIS3-MCT, you can obtain more information on what is happening by increasing the $NLOGPRT value in your namcouple, see section 3.2 for details.",
            "Specifically, CERFACS and the various individuals involved in development and maintenance of the OASIS3-MCT software are not responsible for any damage that may result from correct or incorrect use of this software.",
            "The processes not implied in the coupling do not have to call this routine (for backward compatibility with OASIS3-MCT 2.0, they may still call it describing a null partition, i.e. with ig paral(:)=0).",
            "Processes not implied in the coupling do not have to call this routine at all (for backward compatibility with OASIS3-MCT 2.0, they may still call it with any name and il part id).",
            "In examples/tutoria communication and examples/regrid environment one finds practical examples of how to use the OASIS3-MCT library (see sections 6.3.1 and 6.3.3).",
            "If OASIS3-MCT is modified to produce derivative works, such modified software should be clearly marked, so as not to confuse it with the OASIS3-MCT version available from CERFACS.",
            "\u2022 9-python fortran C-multi intracomm: illustrates the set-up of an intracommunicator between a Fortran, a C and a python components using OASIS3-MCT; a bcast is then realised to share some data.",
            "The directory oasis3-mct/examples/tutorial communication contains the files of a tutorial to learn how to instrument codes with calls to the OASIS3-MCT library in order to couple them together.",
            "For double precision coupling fields, there is no need to promote REAL variables to DOUBLE PRECISION at compilation; this is done automatically within the OASIS3-MCT library.",
            "OASIS3-MCT supports coupling exchanges between parallel components and sub-components deployed in diverse configurations; the different possibilities and how to use the OASIS3-MCT library accordingly are described in section 2.1.",
            "The coupling fields must be sent and received in the same order as they are defined in the corresponding single entry of the namcouple (not relevant in further versions of OASIS3-MCT).",
            "It provides the comprehensive sequence of all operations related to the coupling (field send and receive through MPI, field output on disk, field interpolation and mapping, field reading on disk, restart writing, initialisation and termination phase of the OASIS3-MCT setup) so that any simulation slow down in link with the use of the OASIS3-MCT library can be identified.",
            "# SCRIPR (for GAUSWGT or GAUSWGTNF) $CMETH $CGRS $CFTYP $REST $NBIN $NV $VAR where all entries are as for DISTWGT, except that: * $CMETH = GAUSWGT or GAUSWGTNF * $VAR defines the weight given to a neighbour source grid point as proportional to exp(-1/2\u2022 d 2 /\u03c3 2 ) where d is the distance between the source and target grid points, and \u03c3 2 = $V AR \u2022 D 2 where D 2 is, for each target grid point, the square of average distance between its source grid points (calculated automatically by OASIS3-MCT)."
        ]
    }
}
2026-04-05 07:02:16 urn:uuid:787e9fdb-0144-4706-9a86-ffe980544636 https://datalake.inria.fr https://inria.hal.science ["Offer","coar-notify:ReviewAction"]
{
    "@context": [
        "https://www.w3.org/ns/activitystreams",
        "https://purl.org/coar/notify"
    ],
    "id": "urn:uuid:787e9fdb-0144-4706-9a86-ffe980544636",
    "type": [
        "Offer",
        "coar-notify:ReviewAction"
    ],
    "actor": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "name": "Inria DataLake"
    },
    "origin": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "inbox": "https://prod-datadcis-api.inria.fr/coar/inbox"
    },
    "target": {
        "id": "https://inria.hal.science",
        "type": "Service",
        "inbox": "https://inbox.hal.science"
    },
    "object": {
        "id": "https://hal.science/hal-04739698v1",
        "ietf:cite-as": null,
        "sorg:citation": {
            "@context": "https://doi.org/10.5063/schema/codemeta-2.0",
            "type": "SoftwareSourceCode",
            "name": "OASIS",
            "codeRepository": null,
            "referencePublication": null
        },
        "mentionType": "software",
        "mentionContext": [
            "OASIS3-MCT sustained development is ensured by a collaboration between CERFACS and the Centre National de la Recherche Scientifique (CNRS) and its maintainance and user support is regularly reinforced with additional resources coming from European and national projects.",
            "OASIS3-MCT is a portable set of Fortran 77, Fortran 90 and C routines.",
            "OASIS3-MCT supports coupling of 2D logically-rectangular fields but 3D fields and 1D fields expressed on unstructured grids are also supported using a one dimension degeneration of the structures.",
            "OASIS3-MCT also supports file I/O using NetCDF and has python and C language bindings.",
            "OASIS3-MCT supports different interpolation algorithms as described in chapter 4. Remapping files can be computed online using the SCRIP options, or offline using either the SCRIP, ESMF or XIOS (see examples/regrid environment, section 6.3.3) and read in during the run using the MAPPING transformation.",
            "OASIS3-MCT sources are available from CERFACS git server.",
            "OASIS3-MCT directory structure is the following one:",
            "OASIS3-MCT supports coupling exchanges between parallel components and sub-components deployed in diverse configurations; the different possibilities and how to use the OASIS3-MCT library accordingly are described in section 2.1.",
            "OASIS3-MCT creates this local communicator local comm based on the value of the comp name argument in the oasis init comp call.",
            "OASIS3-MCT is distributed with C bindings and can be called from models written in C and in C++.",
            "OASIS3 MCT couples models which communicate using MPI.",
            "OASIS3-MCT supports both mapping and communication of data through MCT.",
            "OASIS3-MCT also imposes a few other constraints on the usage.",
            "OASIS3-MCT does not support dynamically varying grids nor dynamically varying decompositions at the present time.",
            "OASIS3-MCT is designed primarily to support large memory parallel applications that require efficient and scalable coupling and mapping capabilities.",
            "OASIS3-MCT does not have a distinct feature to support scalar coupling.",
            "OASIS3-MCT will calculate the remapping weights and addresses (if they are not already provided) but will not, at run time, calculate the two gradients and the cross-gradient of the source field (as was the case with OASIS3.3).",
            "OASIS3-MCT must be compiled with the CPP key TREAT OVERLAY which will ensure that these rules are respected.",
            "OASIS3-MCT auxiliary data files OASIS3-MCT uses auxiliary data files, e.g.",
            "OASIS3-MCT has historically created static libraries for use in Fortran source codes.",
            "OASIS, OASIS3-MCT 5.0 has been possible thanks the folllowing fundings:",
            "OASIS3-MCT is a coupling library to be linked to the component models and that carries out the coupling field transformations (e.g.",
            "* OASIS WaitGroup (=14) if the field was not sent because it is part of a group.",
            "* OASIS Ok (=0) otherwise and no error occurred.",
            "\u2022 OASIS3-MCT developments are now continuously tested and validated on different computers with a test suite under Buildbot, which is a software written in Python to automate compile and test cycles required in software project (see https://inle.cerfacs.fr/projects/oasis3-mct/wiki/Buildbot",
            "\u2022 OASIS3-MCT is (only) a coupling library Much of the underlying implementation of OASIS3 was refactored to leverage the Model Coupling Toolkit (MCT).",
            "If OASIS3-MCT is modified to produce derivative works, such modified software should be clearly marked, so as not to confuse it with the OASIS3-MCT version available from CERFACS.",
            "In OASIS3-MCT, several namcouple inputs have been deprecated but, for backwards compatibility, they are still allowed.",
            "In OASIS3-MCT, the grid data (longitudes, latitudes, etc.) must be described by arrays dimensioned (nbr pts,1), where nbr pts is the total number of grid points.",
            "The OASIS3-MCT coupling library uses NetCDF and therefore can also be used to perform I/O actions from/to disk files.",
            "The OASIS3-MCT Application Programming Interface (API) includes different classes of modules or routines that are described in detail in sections 2.2, 2.3 and 2.4 for Fortran, C and python codes respectively.",
            "All OASIS3-MCT API routines are also described in details in sections 2.2, 2.3 and 2.4.",
            "The OASIS CHECK ERR macro aborts OASIS3-MCT with a meaningful message in the debug files in case of failure.",
            "See OASIS3 MCT User Guide section 2.2.7 for details.",
            "The OASIS3-MCT configuration file namcouple contains, below pre-defined keywords, all user-defined information necessary to configure a particular coupled run.",
            "With OASIS3-MCT, it is currently possible to (the text between [ and ] refers to figure 2.1) :",
            "With OASIS3-MCT, all processes exchanging coupling data have to describe, in a global index space, the local partitioning of the different grids onto which the data is expressed (see 2.2.4 for the grid definition).",
            "When OASIS3-MCT aborts, it returns rcode if it is present, else it returns 1",
            "With OASIS3-MCT, the sequence (SEQ) index in the namcouple file now provides the coupling layer with an ability to detect a deadlock before it happens and exit.",
            "With OASIS3-MCT, the grid data files grids.nc,",
            "Since OASIS3-MCT 3.0 release, coupling exchanges between components and sub-components deployed in a much larger diversity of configurations than before are supported.",
            "Since OASIS3-MCT 2.0, MAPPING can be used for higher order remapping.",
            "Since OASIS3-MCT 4.0 release, a hybrid MPI+OpenMP parallel version of the SCRIP library is available.",
            "To use OASIS3-MCT for coupling codes, one has to follow these steps:",
            "To use OASIS3-MCT library, a user needs to add in his code:",
            "Inside OASIS3-MCT, the fields are stored and a single mapping and send instruction is executed for all fields.",
            "Inside OASIS3-MCT, the fields are stored and a single mapping and receive instruction is executed for all fields.",
            "Inside OASIS3-MCT, the fields are stored and a single mapping and send or receive instruction is executed for all fields.",
            "If the OASIS API is used to define the mask and fractions, this can be done via the optional argument companion indicating the grid prefix of the companion grid (see section 2.2.4).",
            "OASIS, OASIS3-MCT 5.0 has been possible thanks the folllowing fundings:",
            "As with OASIS3.3, the \"put\" calls are non-blocking but the \"get\" calls are blocking.",
            "1. Obtain OASIS3-MCT source code (see chapter 1.2). 2. Get familiar with OASIS3-MCT, either by following the Short Private Online Course (SPOC, see https://cerfacs.fr/online-training/) or by going through the tutorial steps.",
            "Using the OASIS3-MCT coupling library, the user has the flexibility to reproduce different coupling algorithms defining LAG values for the different coupling fields .",
            "Compiling OASIS3-MCT libraries can be done from the oasis3-MCT/util/make dir directory with the makefile TopMakefileOasis3.",
            "6. Compile OASIS3-MCT, the component models and start the coupled experiment.",
            "Of course, OASIS3 MCT and the model code then have to be recompiled.",
            "removes all OASIS3-MCT compiled sources and librairies.",
            "Note that by OASIS3-MCT conventions for the mask, a gridcell with mask=0 (active) should have a fractions greater than 0 and a gridcell with mask=1 (inactive) should have a fractions equal to 0. The fraction field is written to the masks.nc",
            "\u2022 To use the OASIS3-MCT C bindings, the statement for the cases in which the ig size and name arguments are not relevant for the partition definition, the placeholders OASIS No Gsize and OASIS No Name can be used instead Here an example for the OASIS Part Apple strategy int part_params[OASIS_Apple_Params]; part_params[OASIS_Strategy] = OASIS_Apple; part_params[OASIS_Offset] = offset; part_params[OASIS_Length] = local_size; int part_id; OASIS_CHECK_ERR(oasis_c_def_partition(&part_id, OASIS_Apple_Params, part_params, OASIS_No_Gsize, OASIS_No_Name));",
            "In practice, OASIS3 MCT will internally handle the error, write an error message in its debug log files and to the screen, and abort before the exception is raised.",
            "Note that by OASIS3-MCT conventions for the mask, a gridcell with mask=0 (active) should have fractions greater than 0 and a gridcell with mask=1 (inactive) should have fractions equal to 0.",
            "Note that by OASIS3-MCT convention for the mask, a gridcell with mask=0 (active) should have a fractions greater than 0 and a gridcell with mask=1 (inactive) should have a fractions equal to 0. The fraction array name must be composed of the grid prefix and the suffix .frc.",
            "Finally, the OASIS3-MCT library should be compiled with the same compilers and system software as any coupled model component using it.",
            "The following OASIS3-MCT CPP keys can be specified in CPPDEF in make.your",
            "With MAPPING, OASIS3-MCT has the ability to read a predefined set of weights and addresses (mapping file) specified in the namcouple to perform the interpolation/remapping.",
            "The different OASIS3.3",
            "Therefore, the OASIS3-MCT makefile TopMakefileOasis3 supports compilation of both static and shared libraries.",
            "\u2022 IGNORED: with OASIS3-MCT, this setting is equivalent to and converted to EXPORTED \u2022 IGNOUT: with OASIS3-MCT, this setting is equivalent to and converted to EXPOUT \u2022 INPUT: read in from the input file by the target component below the oasis get call at appropriate times corresponding to the input period indicated by the user in the namcouple.",
            "The root of the OASIS3-MCT tree can be anywhere, but it must be defined by the variable COUPLE.",
            "Be careful about OASIS3-MCT historical convention (!): 0 = not masked (i.e.",
            "\u2022 Note that from OASIS3-MCT 4.0 onwards, the number of weights in the remapping file and the number of fields in the coupling restart file (when such a file is needed) must strictly match the number of source fields passed to the oasis put .",
            "After compilation OASIS3-MCT is a coupling library to be linked to the component models, and which main function is to interpolate and exchange the coupling fields to form a coupled system.",
            "Also, the current OASIS3-MCT internal debug level ($NLOGPRT value in the namcouple), can be retrieved as a property of a component, namely debug level, and can be changed by directly modifying this property, as in pyoasis/examples/7-multiple-puts/python.",
            "(as in true), then OASIS3-MCT will initialise with zero any variable that normally requires a restart (for instance, variables with LAG > 0) if the restart file does not exist.",
            "\u2022 The behaviour of OASIS3-MCT was changed in the case a component model tries to send with oasis put a field declared with a oasis def var but not defined in the configuration file namcouple; this will now lead to an abort.",
            "Note that previous OASIS3 A, B, G, L, Y, or Z grids are all particular cases of LR grids.",
            "B.5 Changes between OASIS3-MCT 1.0 and OASIS3.3",
            "-$NNOREST : if true, OASIS3-MCT will initialise any variable that normally requires a coupling restart file with zeros if that file does not exist.",
            "kinout [INTEGER; IN]: OASIS In or PRISM In (i.e.",
            "Most of the work that OASIS3-MCT does related to decomposition rearrangement for communication or mapping per se is MPI-based.",
            "The main evolution of OASIS3-MCT 3.0 with respect to OASIS3-MCT 2.0 is the support of coupling exchanges between parallel components deployed in much more diverse configurations than before, for example, within one same executable between components running concurrently on separate sets of tasks or between components running sequentially on overlapping sets of tasks.",
            "On this basis, prepare OASIS3-MCT configuring file namcouple.",
            "As described elsewhere, OASIS3-MCT leverages the MCT 2.11 coupling infrastructure developed at Argonne National Laboratory.",
            "(Note: this was done in OASIS3-MCT 2.0.) \u2022 Coupling field CF standard names",
            "The third number (new in OASIS3-MCT 5.0) can be set to 1 to activate a load balancing diagnostic.",
            "To facilitates this work, OASIS3-MCT can output the full timeline of all coupling related events, for any of the allocated resources.",
            "But even in this case, all OASIS3-MCT interface routines, besides the grid definition (see section 2.2.4) and the \"put\" and \" get\" call per se (see section 2.2.7), are collective and must be called by all processes.",
            "Figure 2.2: The sequence of OASIS3-MCT calls that have to be implemented in the codes so to allow the configuration of components described on figure 2.1.",
            "\u2022 $NCDFTYP: Optional (new in OASIS3-MCT 5.0); on the line below this keyword is a character string that indicates the NetCDF file type for all (i.e.",
            "\u2022 $NUNITNO: Optional (new in OASIS3-MCT 4.0); on the line below this keyword are two integers that indicate the minimum and maximum unit numbers to be used for input and output files in the coupling layer.",
            "\u2022 $NMAPDEC: Optional (new in OASIS3-MCT 4.0); on the line below this keyword is a character string that indicates the mapping decomposition value to be used during local mapping.",
            "\u2022 $NMATXRD: Optional (new in OASIS3-MCT 4.0); on the line below this keyword is a character string that indicates the method used to read remapping weights.",
            "\u2022 $NNOREST: Optional (new in OASIS3-MCT 4.0); on the line below this keyword is a character string that can override the requirement that restart files must exist if they are needed.",
            "(Note: this has changed with OASIS3-MCT 3.0.)",
            "\u2022 $NWGTOPT : Optional (new in OASIS3-MCT 4.0); on the line below this keyword is a character string that indicates how to handle bad remapping weights.",
            "This CPP key was introduced in OASIS3.3.",
            "Grid data files are required by OASIS3-MCT for specific operations, see sections 4 and 5.1.",
            "OASIS3-MCT auxiliary data files OASIS3-MCT uses auxiliary data files, e.g.",
            "Today, different versions of the OASIS3-MCT coupler are used by at least 65 modelling groups all around the world to couple more than 80 applications on different computing platformsfoot_0 .",
            "It is therefore very likely that OASIS3-MCT will provide an efficient and easy-to-use coupling solution for many climate modelling groups in the few years to come.",
            "The OASIS CHECK ERR macro aborts OASIS3-MCT with a meaningful message in the debug files in case of failure.",
            "Be careful to use the historical OASIS3-MCT convention: 0 = not masked (i.e.",
            "The last version of the coupler, OASIS3-MCT 5.0, comes with the following novelties:",
            "For more detail on how to use the OASIS3-MCT API in the codes, see chapter 2. 4. Define all coupling and I/O parameters and the transformations required to adapt each coupling field from the source model grid to the target model grid.",
            "Interfacing a component code with OASIS3-MCT At run-time, OASIS3-MCT performs parallel exchange of coupling data between parallel components and sub-components and allows regridding (also called remapping or interpolation), time integration or accumulation and other transformations of these coupling fields.",
            "Since the OASIS3-MCT 4.0 release, OASIS3-MCT includes a mixed MPI+OpenMP parallel version of the SCRIP library for the calculation of the remapping weights (see section 4.3).",
            "The other new features offered by OASIS3-MCT 4.0 are the following:",
            "This field does not play a role in OASIS3-MCT implementation and is never needed.",
            "Users are discouraged from calling OASIS3-MCT oasis put and oasis get from a threaded region.",
            "\u2022 many bug fixes B.4 Changes between OASIS3-MCT 2.0 and OASIS3-MCT 1.0",
            "The main changes and bug fixes new in OASIS3-MCT 2.0 are the following:",
            "To follow day to day evolution of the OASIS3-MCT sources, it is also possible to have your e-mail added to the list of addresses to which the log files of the SVN checkins are automatically sent; contact oasishelp@cerfacs.fr",
            "\u2022 The namcouple configuration file of OASIS3-MCT is fully backward compatible with OASIS3.3.",
            "Its interface mimics the corresponding OASIS3 MCT functio oasis abort.",
            "A list of coupled models realised with OASIS3-MCT can be found at https://oasis.cerfacs.fr/en/oasis-coupled-models/",
            "B.5 Changes between OASIS3-MCT 1.0 and OASIS3.3",
            "For CONSERV/SECOND, 3 weights are needed; OASIS3-MCT will calculate these weights and corresponding addresses (if they are not already provided) but will not, at run time, calculate the two extra terms to which the second and third weights should be applied.",
            "info [INTEGER; OUT]: returned info code: * OASIS Sent (=4) if the field was sent to another component * OASIS LocTrans (=5) if the field was only used in a time transformation (not sent, not output) * OASIS ToRest (=6) if the field was written to a restart file only * OASIS Output (=7) if the field was written to an output file only * OASIS SentOut (=8) if the field was both written to an output file and sent to another component * OASIS ToRestOut (=9) if the field was written both to a restart file and to an output file.",
            "info [INTEGER; OUT]: returned info code: * OASIS Recvd(=3) if the field was received from another component * OASIS FromRest (=10) if the field was read from a restart file only * OASIS Input (=11) if the field was read from an input file only * OASIS RecvOut (=12) if the field was both received from another component and written to an output file * OASIS FromRestOut (=13) if the field was both read from a restart file and written to an output file * OASIS Ok (=0) otherwise and no error occurred.",
            "$NCDFTYP only affects new files created by OASIS3-MCT.",
            "= 21) for fields received by the component; OASIS Out, PRISM Out (i.e.",
            "vector fields) are not supported anymore in OASIS3-MCT.",
            "as 4 th argument and does not call any other OASIS3-MCT routine.",
            "Note that while this feature is supported in OASIS3-MCT, a more transparent implementation might be to combine fields in the model (not in OASIS3-MCT) after they are received independently.",
            "If both are defined, they must be consistent; OASIS3-MCT will abort if they are not coherent or if both are missing.",
            "2.2.7).The lag (LAG) index works as before in OASIS3.3",
            "The evolution between the different versions of OASIS3-MCT can be followed in real-time by registering on the Redmine project management site at https://inle.cerfacs.fr/",
            "In case of single proc invocations, the constant OASIS No Part can be passed as a placeholder",
            "In case of single proc invocations, the constant OASIS No Part can be passed as a placeholder if no companion grid attribute is needed, the constant OASIS No Companion can be passed as a placeholder \u2022 int oasis c write frac(const char * cgrid, const int nx global, const int ny global, const int nx loc, const int ny loc, const double * frac, const int il partid, const char * companion) nx global and ny global are the first and second dimensions of the global grid nx loc and ny loc are the two dimensions of the local array frac frac is stored with a Fortran compatible (column major) ordering.",
            "In case of single proc invocations, the constant OASIS No Part can be passed as a placeholder if no companion grid attribute is needed, the constant OASIS No Companion can be passed as a placeholder \u2022 int oasis c write area(const char * cgrid, const int nx global, const int ny global, const int nx loc, const int ny loc, const double * area, const int il partid) nx global and ny global are the first and second dimensions of the global grid nx loc and ny loc are the two dimensions of the local array area area is stored with a Fortran compatible (column major) ordering.",
            "In case of single proc invocations, the constant OASIS No Part can be passed as a placeholder \u2022 int oasis c write angle(const char * cgrid, const int nx global, const int ny global, const int nx loc, const int ny loc, const double * angle, const int il partid) nx global and ny global are the first and second dimensions of the global grid nx loc and ny loc are the two dimensions of the local array angle angle is stored with a Fortran compatible (column major) ordering.",
            "In case of single proc invocations, the constant OASIS No Part can be passed as a placeholder \u2022 int oasis c terminate grids writing()",
            "All diagnotics are written to the master process OASIS3-MCT debug file (under the attribute \"CHECK* diags\").",
            "(Note: these remapping schemes, not available in OASIS3-MCT 1.0 were reactivated in OASIS3-MCT 2.0, see B.4.)",
            "\u2022 Exceptions and aborting When an error occurs in OASIS3 MCT, the code coupler returns an error code and an OasisException is raised.",
            "The level of debug information written out to the OASIS3-MCT debug files for each model process is defined by the $NLOGPRT value in the namcouple.",
            "Low-intrusiveness, portability and flexibility are OASIS3-MCT key design concepts.",
            "If the source grid is a gaussian reduced grid (D), OASIS3-MCT 2.0 can calculate the interpolated field using only the values of the source field points.",
            "All previous SCRIPR remapping schemes available in OASIS3.3 are still supported in OASIS3-MCT 1.0 besides BICUBIC and CONSERV/SECOND because these remapping involve at each source grid point the value of the field but also the value of the gradients of the field (which are not known or calculated).",
            "The debug mode was greatly improved as compared to OASIS3.3.",
            "CERFACS has rights to use, reproduce, and distribute OASIS3-MCT.",
            "The main evolution of OASIS3-MCT 3.0 with respect to OASIS3-MCT 2.0 is the support of coupling exchanges between parallel components deployed in much more diverse configurations than before, for example, within one same executable between components running concurrently on separate sets of tasks or between components running sequentially on overlapping sets of tasks.",
            "The developments realised in the different versions of OASIS3-MCT are described in Appendix B. To communicate with another component, or to perform I/O actions, a component model needs to include few specific calls to OASIS3-MCT Application Programming Interface (API).",
            "how to to reproduce different coupling algorithms with OASIS3-MCT using the LAG index (see 2.5.3), and on the SEQ index (see 2.5.4).",
            "mapping, restart, output) new NetCDF files generated by OASIS3.",
            "\u2022 many bug fixes B.4 Changes between OASIS3-MCT 2.0 and OASIS3-MCT 1.0",
            "The first element, var nodims(1), is not used anymore in OASIS3-MCT, so its value can be anything; The second element, var nodims(2), is the number of fields in a bundle (this will be 1 for unbundle fields or greater than 1 for fields that are bundled; note that if var nodims(2)=0, it will be automatically reset to 1 in the routine, to ensure backward compatibility).",
            "Interfacing a component code with OASIS3-MCT At run-time, OASIS3-MCT performs parallel exchange of coupling data between parallel components and sub-components and allows regridding (also called remapping or interpolation), time integration or accumulation and other transformations of these coupling fields.",
            "var type [INTEGER; IN]: type of coupling field array; put OASIS Real or PRISM Real (i.e.",
            "The coupling restart files are also used automatically by OASIS3-MCT to allow partial LOCTRANS time transformation to be saved at the end of a run for exact restart at the start of the next run.",
            "For details on how to compile and run a coupled model with OASIS3-MCT, see section 6.",
            "write restart can take one of the two predefined constants OASIS Write Restart or OASIS No Restart kinfo contains a return status to be compared against the values of the return codes enumeration in oasis c.h (equivalent to the returned value of info argument for the Fortran oasis put routine, see section 2.2.7)",
            "Note that the ability to check mapping files at runtime in OASIS3-MCT is limited.",
            "A few bugs were fixed in the SCRIP library available since OASIS3-MCT",
            "\u2022 EXPORTED: exchanged between components and transformed by OASIS3-MCT \u2022 EXPOUT: exchanged, transformed and also written to two debug NetCDF files, one before the sending action in the source component below the oasis put call (after local transformations LOCTRANS and BLASOLD if present), and one after the receiving action in the target component below the oasis get call (after all transformations).",
            "Compiling, running, debugging, load balancing 6.1 Compiling OASIS3-MCT OASIS3-MCT is a mixed MPI-OpenMP parallel code.",
            "Vector mapping is NOT supported and will not be supported by OASIS3-MCT.",
            "The following targets have been used historically to compile OASIS3-MCT for Fortran codes and they are all still supported:",
            "\u2022 Support of previous prism xxx and new oasis xxx interfaces OASIS3-MCT retains prior interface names of OASIS3.3 (e.g.",
            "The separation of mapping and communication is handled by the OASIS layer.",
            "As described in section 4 for the different SCRIP remappings, OASIS3-MCT support different types of grids.",
            "Different transformations and 2D interpolations are available in OASIS3-MCT to adapt the coupling fields from a source model grid to a target model grid.",
            "To interact with the rest of the coupled system, few calls of the OASIS3-MCT library routines, which sources can be found in oasis3-mct/lib/psmile directory, have to be implemented in component Fortran codes.",
            "For details on the different ways to describe the partitions, see OASIS3 MCT User Guide, section 2.2.3 and examples 1 serial, 2 apple, 3 box, 4 orange, 5 points in pyoasis/examples.",
            "(Note: prism put inquire and prism get freqs were reintroduced in OASIS3-MCT 3.0 and equivalent of prism put restart proto in OASIS3-MCT 4.0.)",
            "Details about the grid definition can be found in section 2.2.4 of OASIS3 MCT User Guide.",
            "The different possible return codes are listed in section 2.2.9 of OASIS3 MCT User Guide.",
            "All combined fields must be received by the same model component in OASIS3-MCT (either via coupling or input), and the field size and decomposition must be consistent across all fields being combined.",
            "The C bindings can be compiled into static or shared libraries by the OASIS3-MCT TopMakefileOasis3 as documented in 6.1.",
            "Compiling, running, debugging, load balancing 6.1 Compiling OASIS3-MCT OASIS3-MCT is a mixed MPI-OpenMP parallel code.",
            "Results obtained with IS-ENES2 coupling technology benchmarks show that OASIS3-MCT performs as well as, and even better at very high number of cores, than other coupling technologies, at least for up to O(10000) cores.",
            "1. Obtain OASIS3-MCT source code (see chapter 1.2). 2. Get familiar with OASIS3-MCT, either by following the Short Private Online Course (SPOC, see https://cerfacs.fr/online-training/) or by going through the tutorial steps.",
            "* $ASSCMP, $PROJCART: UNUSED; vector fields are not supported anymore in OASIS3-MCT.",
            "This section describes how to send (put) and receive (get) fields through OASIS-MCT API.",
            "Different developments were realised to improve the parallel performance of OASIS3-MCT 4.0.",
            "Notice that this choice implies an extra memory copy performed internally by OASIS3-MCT before acting on the field and is therefore to be avoided whenever possible.",
            "\u2022 Mono-process mapping file generation with the SCRIP library But as before, OASIS3-MCT 1.0 can also generate the mapping file using the SCRIP library [Jones 1999].",
            "But besides this aspect, MCT itself, and therefore the communication layer in OASIS, has only minimal OpenMP support at the present time.",
            "If both a mask and fractions are defined for a grid, they must be consistent; OASIS3-MCT will abort if they are not coherent or if both are missing.",
            "\u2022 Using the coupler in interpolator-only mode This is not possible anymore as OASIS3-MCT is now only a coupling library.",
            "This chapter describes how to adapt the component codes to couple them through OASIS3-MCT.",
            "To facilitate this work, a load balancing analysis functionality is included in OASIS3-MCT and can be activated by setting to 1 the third number under $NLOGPRT in the namcouple configuration file (see section 3.2).",
            "The latter is an enumerated type and can have the values pyoasis.OasisParameters.OASIS OUT or pyoasis.OasisParameters.OASIS IN.",
            "write restart can take one of the two predefined constants OASIS Write Restart or OASIS No Restart kinfo contains a return status to be compared against the values of the return codes enumeration in oasis c.h (equivalent to the returned value of info argument for the Fortran oasis put routine, see section 2.2.7)",
            "If such a communicator already exists in the code, it should simply be provided to OASIS3 MCT with the method set couplcomm; as in pyoasis/examples/6-apple and orange/python.",
            "All previous SCRIPR remapping schemes available in OASIS3.3 are still supported in OASIS3-MCT 1.0 besides BICUBIC and CONSERV/SECOND because these remapping involve at each source grid point the value of the field but also the value of the gradients of the field (which are not known or calculated).",
            "their coupling period, the list of transformations or remapping to be performed by OASIS3-MCT and associated configuring lines (described in more details in chapter 4).",
            "\u2022 OASIS3-MCT is (only) a coupling library Much of the underlying implementation of OASIS3 was refactored to leverage the Model Coupling Toolkit (MCT).",
            "\u2022 The namcouple configuration file of OASIS3-MCT is fully backward compatible with OASIS3.3.",
            "The public may copy, distribute, use, prepare derivative works and publicly display OASIS3-MCT under the terms of the Lesser GNU General Public License (LGPL) as published by the Free Software Foundation, provided that this notice and any statement of authorship are reproduced on all copies.",
            "(Note: these remapping schemes, not available in OASIS3-MCT 1.0 were reactivated in OASIS3-MCT 2.0, see B.4.)",
            "-The following transformations are not available as they were already deprecated in OASIS3.3",
            "Its design philosophy, based on flexibility and minimal invasiveness, is close to the OASIS3-MCT approach.",
            "\u2022 CALL prism enddef proto(kinfo) kinfo [INTEGER; OUT]: returned error code. 2 Parameters OASIS In, PRISM In, OASIS Out, PRISM Out are defined in oasis3mct/lib/psmile/src/mod oasis parameters.F90",
            "\u2022 Other transformations not supported -The following transformations are not available in OASIS3.3 and will most probably not be implemented as it should be not too difficult to implement the equivalent operations in the component models themselves: CORRECT, FILLING, SUBGRID, MASKP -LOCTRANS/ONCE is not explicitely offered as it is equivalent to defining a coupling period equal to the total runtime.",
            "If this communicator already exists in the code, the component should simply provide it to OASIS3-MCT with:",
            "When activated, the load balancing analysis functionality outputs the full timeline of all OASIS3-MCT related events, for any of the allocated resources.",
            "In the future, it is possible that some dynamic grid capabilities might be supported through OASIS3-MCT but requirements and implementation are still being assessed.",
            "The test interpolation environment (see section ?? ) gives a practical example on how to use OASIS3-MCT 4.0 to pre-calculate (i.e. in a separate job prior to the \"real\" simulation) the remapping weight and address file.",
            "This tutorial is extracted from the Short Online Private Course (SPOC) on \"Code Coupling with OASIS3-MCT\" shortly described in the next section.",
            "A user cannot send a single grid point value to multiple destination gridcells or processes via OASIS3-MCT.",
            "The interface in module mod prism is provided for backwards compatability with prior versions of OASIS3.",
            "There are some floating point operations in the sparse matrix multiple as well as in some of the OASIS3-MCT transforms; but generally, these are highly parallel and would often not benefit from use of OpenMP.",
            "\u2022 IGNORED: with OASIS3-MCT, this setting is equivalent to and converted to EXPORTED \u2022 IGNOUT: with OASIS3-MCT, this setting is equivalent to and converted to EXPOUT \u2022 INPUT: read in from the input file by the target component below the oasis get call at appropriate times corresponding to the input period indicated by the user in the namcouple.",
            "\u2022 make -f TopMakefileOasis3 or make -f TopMakefileOasis3 oasis3 psmile compiles static versions of OASIS3-MCT Fortran libraries mct, mpeu, scrip and psmile;",
            "\u2022 Better support of components for which only a subset of processes participate in the coupling In OASIS3.3,",
            "B.5.3 Functionality not offered anymore \u2022 SCRIPR/BICUBIC and SCRIPR/CONSERV/SECOND remappings As in OASIS3.3, the SCRIP library can be used to generate the remapping/interpolation weights and addresses and write them to a mapping file.",
            "90.0 for both, not 450.0 for one and 90.0 for the other) to ensure automatic detection of overlap by OASIS3-MCT (which is essential to have a correct conservative remapping SCRIPR/CONSERV, see section 4.3).",
            "The tutorial involves two toy model codes, ocean.F90 and atmos.F90, to be instrumented with calls to OASIS3-MCT API (Application Program Interface) routines.",
            "The number of OpenMP threads per MPI process used by SCRIP is set by a dedicated environment variable OASIS OMP NUM THREADS, which can be different from the default number of threads per MPI process used elsewhere in the application, set by the environment variable OMP NUM THREADS ; in practice, OASIS OMP NUM THREADS has to be smaller or equal to OMP NUM THREADS.",
            "360.0 for both, not 450.0 for one and 90.0 for the other) to ensure automatic detection of overlap by OASIS3-MCT.",
            "3. Identify the coupling or I/O fields and adapt the codes to implement the coupling exchanges with the OASIS3-MCT coupling library based on MPI message passing.",
            "info [INTEGER; OUT]: returned info code: * OASIS Sent (=4) if the field was sent to another component * OASIS LocTrans (=5) if the field was only used in a time transformation (not sent, not output) * OASIS ToRest (=6) if the field was written to a restart file only * OASIS Output (=7) if the field was written to an output file only * OASIS SentOut (=8) if the field was both written to an output file and sent to another component * OASIS ToRestOut (=9) if the field was written both to a restart file and to an output file.",
            "\u2022 Support of previous prism xxx and new oasis xxx interfaces OASIS3-MCT retains prior interface names of OASIS3.3 (e.g.",
            "This directory contains the sources used in the Short Online Private Course (SPOC) on \"Code Coupling with OASIS3-MCT\" developed in the framework of the ESiWACE Centre of Excellence.",
            "For example, the following constructs are equivalent in the two languages: For convenience a similar macro OASIS CHECK MPI ERR has been defined for testing the return code of any MPI function against MPI SUCCESS and cleanly aborting OASIS3-MCT in case of failure.",
            "\u2022 CALL prism enddef proto(kinfo) kinfo [INTEGER; OUT]: returned error code. 2 Parameters OASIS In, PRISM In, OASIS Out, PRISM Out are defined in oasis3mct/lib/psmile/src/mod oasis parameters.F90",
            "info [INTEGER; OUT]: returned info code: * OASIS Recvd(=3) if the field was received from another component * OASIS FromRest (=10) if the field was read from a restart file only * OASIS Input (=11) if the field was read from an input file only * OASIS RecvOut (=12) if the field was both received from another component and written to an output file * OASIS FromRestOut (=13) if the field was both read from a restart file and written to an output file * OASIS Ok (=0) otherwise and no error occurred.",
            "or by the code itself in the initialisation phase by calling routine oasis write corner (see section 2.2.4) ; OASIS3-MCT will not attempt to automatically calculate them as OASIS3.3.",
            "-oasis3-mct/lib/cbindings C language bindings source code /mct Model Coupling Toolkit Coupling Software /psmile OASIS3-MCT coupling library /scrip SCRIP interpolation library -oasis3-mct/doc OASIS3-MCT User Guide -oasis3-mct/util/make_dir Utilities to compile OASIS3-MCT /load_balancing Tool for load balancing analysis -oasis3-mct/pyoasis Python wrapper source code -oasis3-mct/examples Environment to compile, run and use different toy coupled models.",
            "\u2022 If required, broadcast the scalars after being received from the root process to the other processes, outside the OASIS3-MCT layer.",
            "If grid cell fractions are also defined in that file, the mask and fractions are considered and must be consistent; OASIS3-MCT will abort if they are not or if both are missing.",
            "The latter is an enumerated type and can have the values pyoasis.OasisParameters.OASIS OUT or pyoasis.OasisParameters.OASIS IN.",
            "To interface a component code with OASIS3-MCT and use the module mod oasis (see section 2.2.1), it is required to include OASIS3-MCT modules from $ARCHDIR/include and link with appropriate libraries in $ARCHDIR/lib during the compilation and linking.",
            "(Note: prism put inquire and prism get freqs were reintroduced in OASIS3-MCT 3.0 and equivalent of prism put restart proto in OASIS3-MCT 4.0.)",
            "\u2022 Also the following inputs should not appear in the namcouple anymore as the related functionality are not supported anymore in OASIS3-MCT (see above): field status AUXILARY, time transformation ONCE, REDGLO, INVERT, MASK, EXTRAP, CORRECT, INTERP, MOZAIC, FILLING, SUBGRID, MASKP, REVERSE, GLORED.",
            "The prior ability to perform a linear combination of the current coupling field with other coupling fields has been deprecated in OASIS3-MCT.",
            "It is also possible to provide an optional coupling flag argument which defaults to \"True\", which means the component is coupled through OASIS3 MCT.",
            "These additional lines are described in more details in the chapter 4. Support to couple multiple fields via a single communication With OASIS3-MCT, it is possible to couple mutiple fields via a single communication.",
            "Note that while this feature is supported in OASIS3-MCT, a more transparent implementation might be to combine fields in the model (not in OASIS3-MCT) after they are received independently.",
            "In case of single proc invocations, the constant OASIS No Part can be passed as a placeholder if no companion grid attribute is needed, the constant OASIS No Companion can be passed as a placeholder \u2022 int oasis c write frac(const char * cgrid, const int nx global, const int ny global, const int nx loc, const int ny loc, const double * frac, const int il partid, const char * companion) nx global and ny global are the first and second dimensions of the global grid nx loc and ny loc are the two dimensions of the local array frac frac is stored with a Fortran compatible (column major) ordering.",
            "In case of single proc invocations, the constant OASIS No Part can be passed as a placeholder if no companion grid attribute is needed, the constant OASIS No Companion can be passed as a placeholder \u2022 int oasis c write area(const char * cgrid, const int nx global, const int ny global, const int nx loc, const int ny loc, const double * area, const int il partid) nx global and ny global are the first and second dimensions of the global grid nx loc and ny loc are the two dimensions of the local array area area is stored with a Fortran compatible (column major) ordering.",
            "When this is the case, the mapping file generation is done on one process of the model components; all previous SCRIPR remapping schemes available in OASIS3.3 are still supported besides BICUBIC and CONSERV/SECOND.",
            "\u2022 New routines oasis get debug and oasis set debug New routines oasis get debug and oasis set debug are now available to respectively retrieve the current OASIS3-MCT internal debug level (set by $NLOGPRT in the namcouple) or to change it (see section 2.2.9).",
            "The goal is to instrument two toy models to set-up a real coupled model exchanging coupling fields (directory /spoc communication) and to learn more about OASIS3-MCT regridding functionality (directory /spoc regridding).",
            "There are other situations where the value of the actual mapping weight is scientifically incorrect, but this is not easy to detect and is not dealt with in OASIS3-MCT.",
            "\u2022 To use the OASIS3-MCT C bindings, the statement for the cases in which the ig size and name arguments are not relevant for the partition definition, the placeholders OASIS No Gsize and OASIS No Name can be used instead Here an example for the OASIS Part Apple strategy int part_params[OASIS_Apple_Params]; part_params[OASIS_Strategy] = OASIS_Apple; part_params[OASIS_Offset] = offset; part_params[OASIS_Length] = local_size; int part_id; OASIS_CHECK_ERR(oasis_c_def_partition(&part_id, OASIS_Apple_Params, part_params, OASIS_No_Gsize, OASIS_No_Name));",
            "Because cdf5 may not be generally available in all NetCDF installations, use of this option requires that the C preprocessor directive CDF 64BIT DATA be used when compiling OASIS3-MCT.",
            "or by the code itself in the initialisation phase by calling routine oasis write corner (see section 2.2.4) ; OASIS3-MCT will not attempt to automatically calculate them as OASIS3.3.",
            "Note that the option of having the value 1.0E+20 assigned to these target grid cell intersecting only masked source cells (for easier identification) is not yet availble in OASIS3-MCT.",
            "info [INTEGER; OUT]: returned info code: * OASIS Recvd(=3) if the field was received from another component * OASIS FromRest (=10) if the field was read from a restart file only * OASIS Input (=11) if the field was read from an input file only * OASIS RecvOut (=12) if the field was both received from another component and written to an output file * OASIS FromRestOut (=13) if the field was both read from a restart file and written to an output file * OASIS Ok (=0) otherwise and no error occurred.",
            "An interface named oasis interface in Fortran can be expected to be named oasis c interface in C. All of the C interfaces return an integer error code which can be tested against the OASIS Ok (or the equivalent OASIS Success) constant.",
            "\u2022 To use the OASIS3-MCT C bindings, the statement for the cases in which the ig size and name arguments are not relevant for the partition definition, the placeholders OASIS No Gsize and OASIS No Name can be used instead Here an example for the OASIS Part Apple strategy int part_params[OASIS_Apple_Params]; part_params[OASIS_Strategy] = OASIS_Apple; part_params[OASIS_Offset] = offset; part_params[OASIS_Length] = local_size; int part_id; OASIS_CHECK_ERR(oasis_c_def_partition(&part_id, OASIS_Apple_Params, part_params, OASIS_No_Gsize, OASIS_No_Name));",
            "For example, if they are declared as double pointers, they have to be lon[ny loc][nx loc] il partid is relevant only for parallel writing; in case of single proc invocations, the constant OASIS No Part can be passed as a placeholder",
            "At the present time, it is not possible to map the field as part of the communication rearrangement, although in theory, that capability should be possible to implement in the future, and OASIS3-MCT developers are considering it.",
            "Users need to be aware which processes contain valid scalar data both on the source and destination side and to manage data synchronization between processes within a component outside the OASIS3-MCT layer.",
            "-oasis3-mct/lib/cbindings C language bindings source code /mct Model Coupling Toolkit Coupling Software /psmile OASIS3-MCT coupling library /scrip SCRIP interpolation library -oasis3-mct/doc OASIS3-MCT User Guide -oasis3-mct/util/make_dir Utilities to compile OASIS3-MCT /load_balancing Tool for load balancing analysis -oasis3-mct/pyoasis Python wrapper source code -oasis3-mct/examples Environment to compile, run and use different toy coupled models.",
            "\u2022 CALL prism get debug(debug, kinfo) debug [INTEGER; OUT]: output debug value kinfo [INTEGER; OUT; OPTIONAL]: returned error code This routine may be called at any time to retrieve the current OASIS3-MCT internal debug level (see $NLOGPRT in section 3.",
            "Notice that for unstructured grids y size=1 bundle size should be coherent with the argument of same name in the corresponding oasis c def var fkind can take one of the two predefined constants OASIS Real or OASIS Double (also in the form OASIS REAL or OASIS DOUBLE) should be coherent with the argument ktype in oasis c def var storage can take one of the two predefined constants OASIS COL MAJOR or OASIS ROW MAJOR.",
            "\u2022 CALL prism set debug(debug, kinfo) debug [INTEGER; IN]: input debug value kinfo [INTEGER; OUT; OPTIONAL]: returned error code This routine may be called at any time to change the debug level in OASIS3-MCT.",
            "info [INTEGER; OUT]: returned info code: * OASIS Sent (=4) if the field was sent to another component * OASIS LocTrans (=5) if the field was only used in a time transformation (not sent, not output) * OASIS ToRest (=6) if the field was written to a restart file only * OASIS Output (=7) if the field was written to an output file only * OASIS SentOut (=8) if the field was both written to an output file and sent to another component * OASIS ToRestOut (=9) if the field was written both to a restart file and to an output file.",
            "New routines oasis create couplcomm and oasis set couplcomm are now available to create or set a coupling communicator gathering only these processes (see section 2.2.2). (Note: this was further improved in OASIS3-MCT 3.0.)",
            "Notice that for unstructured grids y size=1 bundle size should be coherent with the argument of same name in the corresponding oasis c def var fkind can take one of the two predefined constants OASIS Real or OASIS Double (also in the form OASIS REAL or OASIS DOUBLE) should be coherent with the argument ktype in oasis c def var storage can take one of the two predefined constants OASIS COL MAJOR or OASIS ROW MAJOR.",
            "\u2022 CALL oasis get freqs(var id, mop, ncpl, cpl freqs, kinfo) \u2022 CALL prism get freqs proto(var id, mop, ncpl, cpl freqs, kinfo) var id [INTEGER; IN]: field ID (from corresponding oasis def var) mop [INTEGER; IN]: OASIS Out or OASIS In ncpl [INTEGER; IN]: number of couplings in which the field is involved (i.e. when a field is sent to multiple targets) cpl freqs [INTEGER; DIMENSION(ncpl); OUT]: coupling period(s) (in number of seconds) of field var id.",
            "An interface named oasis interface in Fortran can be expected to be named oasis c interface in C. All of the C interfaces return an integer error code which can be tested against the OASIS Ok (or the equivalent OASIS Success) constant.",
            "However, given these modifications, one cannot expect to get exactly the same results for the weight-and-address remapping files with this new parallel SCRIP version as compared to the previous SCRIP version in OASIS3-MCT 3.0.",
            "the source symbolic name must be repeated twice on the field first line -1 : UNUSED but still required for parsing -86400 : output period for the field, in seconds -1 : number of transformations to be performed by OASIS3-MCT on this field -flda3.nc",
            "OASIS3-MCT will calculate the remapping weights and addresses (if they are not already provided) but will not, at run time, calculate the two gradients and the cross-gradient of the source field (as was the case with OASIS3.3).",
            "The developments realised in the different versions of OASIS3-MCT are described in Appendix B. To communicate with another component, or to perform I/O actions, a component model needs to include few specific calls to OASIS3-MCT Application Programming Interface (API).",
            "\u2022 EU Centre of Excellence ESiWACE2 , GA #823988 \u2022 EU IS-ENES3 -Infrastructure for the European Network for Earth System modelling -Phase 3 project (GA # 824084) We would like to thank the main past or present developers of OASIS (in alphabetical order, with the name of their institution at the time of their contribution to OASIS): Arnaud Caubel (LSCE/IPSL & FECIT/Fujitsu), Laure Coquart (CNRS/CERFACS) Anthony Craig (CER-FACS -consultant), Damien Declat (CERFACS), Italo Epicoco (CMCC), Rupert Ford (STFC), Philippe Gambron (STFC), Veronika Gayler (MPI-M&D), Josefine Ghattas (CERFACS), Christopher Goodyer (NAG) Jean Latour (CERFACS & Fujitsu-Fecit), Eric Maisonnave (CERFACS), Silvia Mocavero (CMCC), Andrea Piacentini (CERFACS -consultant) Elodie Rapaport (CERFACS), Sami Saarinen (ECMWF), Eric",
            "\u2022 CALL oasis get freqs(var id, mop, ncpl, cpl freqs, kinfo) \u2022 CALL prism get freqs proto(var id, mop, ncpl, cpl freqs, kinfo) var id [INTEGER; IN]: field ID (from corresponding oasis def var) mop [INTEGER; IN]: OASIS Out or OASIS In ncpl [INTEGER; IN]: number of couplings in which the field is involved (i.e. when a field is sent to multiple targets) cpl freqs [INTEGER; DIMENSION(ncpl); OUT]: coupling period(s) (in number of seconds) of field var id.",
            "coupl comm [INTEGER; IN]: MPI communicator gathering only component processes participating in the coupling kinfo [INTEGER; OUT; OPTIONAL]: returned error code This routine allows users to provide a local coupling communicator to OASIS3-MCT, given that it already exists in the code.",
            "il part id [INTEGER; OUT]: partition ID ig paral [INTEGER, DIMENSION(:), IN]: vector of integers describing the local grid partition in the global index space; has a different expression depending on the type of the partition; in OASIS3-MCT, 5 types of partition are supported: Serial (no partition), Apple, Box, Orange, and Points (see below).",
            "For example, the following constructs are equivalent in the two languages: For convenience a similar macro OASIS CHECK MPI ERR has been defined for testing the return code of any MPI function against MPI SUCCESS and cleanly aborting OASIS3-MCT in case of failure.",
            "Even if $AVALUE is zero, this line must still be included if $NBFIELDS is greater than 0. If $NBFIELDS is greater than 1, then additional input lines have the format $FNAME $XMULT $AVALUE where $FNAME is the name of a field received in OASIS3-MCT in the same model and $XMULT and $AVALUE are the multipliers and additive terms to be applied to $FNAME :",
            "Notice that for unstructured grids y size=1 bundle size should be coherent with the argument of same name in the corresponding oasis c def var fkind can take one of the two predefined constants OASIS Real or OASIS Double (also in the form OASIS REAL or OASIS DOUBLE) should be coherent with the argument ktype in oasis c def var storage can take one of the two predefined constants OASIS COL MAJOR or OASIS ROW MAJOR.",
            "As before with the MPI1 mode, all component models must be started by the user in the job script in a pseudo-MPMD mode; in this case, they will automatically share the same MPI COMM WORLD communicator and an internal communicator created by OASIS3-MCT needs to be used for internal parallelization (see section 2.2.2).",
            "\u2022 To use the OASIS3-MCT C bindings, the statement for the cases in which the ig size and name arguments are not relevant for the partition definition, the placeholders OASIS No Gsize and OASIS No Name can be used instead Here an example for the OASIS Part Apple strategy int part_params[OASIS_Apple_Params]; part_params[OASIS_Strategy] = OASIS_Apple; part_params[OASIS_Offset] = offset; part_params[OASIS_Length] = local_size; int part_id; OASIS_CHECK_ERR(oasis_c_def_partition(&part_id, OASIS_Apple_Params, part_params, OASIS_No_Gsize, OASIS_No_Name));",
            "info [INTEGER; OUT]: returned info code: * OASIS Recvd(=3) if the field was received from another component * OASIS FromRest (=10) if the field was read from a restart file only * OASIS Input (=11) if the field was read from an input file only * OASIS RecvOut (=12) if the field was both received from another component and written to an output file * OASIS FromRestOut (=13) if the field was both read from a restart file and written to an output file * OASIS Ok (=0) otherwise and no error occurred.",
            "It provides the comprehensive sequence of any operations related to the coupling (field exchange through MPI, field output on disk, field interpolation and mapping, field reading on disk, restart writing, initialisation and termination phase of the OASIS3-MCT setup) so that any simulation slow down in link with the use of the OASIS library can be identified.",
            "Notice that for unstructured grids y size=1 bundle size should be coherent with the argument of same name in the corresponding oasis c def var fkind can take one of the two predefined constants OASIS Real or OASIS Double (also in the form OASIS REAL or OASIS DOUBLE) should be coherent with the argument ktype in oasis c def var storage can take one of the two predefined constants OASIS COL MAJOR or OASIS ROW MAJOR.",
            "It provides the comprehensive sequence of all operations related to the coupling (field send and receive through MPI, field output on disk, field interpolation and mapping, field reading on disk, restart writing, initialisation and termination phase of the OASIS3-MCT setup) so that any simulation slow down in link with the use of the OASIS3-MCT library can be identified.",
            "-oasis3-mct/lib/cbindings C language bindings source code /mct Model Coupling Toolkit Coupling Software /psmile OASIS3-MCT coupling library /scrip SCRIP interpolation library -oasis3-mct/doc OASIS3-MCT User Guide -oasis3-mct/util/make_dir Utilities to compile OASIS3-MCT /load_balancing Tool for load balancing analysis -oasis3-mct/pyoasis Python wrapper source code -oasis3-mct/examples Environment to compile, run and use different toy coupled models.",
            "info [INTEGER; OUT]: returned info code: * OASIS Sent (=4) if the field was sent to another component * OASIS LocTrans (=5) if the field was only used in a time transformation (not sent, not output) * OASIS ToRest (=6) if the field was written to a restart file only * OASIS Output (=7) if the field was written to an output file only * OASIS SentOut (=8) if the field was both written to an output file and sent to another component * OASIS ToRestOut (=9) if the field was written both to a restart file and to an output file.",
            "\u2022 int oasis c def var(int * var id, const char * name, const int il part id, const bundle size, const int kinout, const int var type) bundle size is a scalar integer, corresponding to the second entry of the Fortran var nodims array kinout can receive one of the two predefined constants OASIS In or OASIS Out (also in the form OASIS IN or OASIS OUT) var type can receive one of the two predefined constants OASIS Real or OASIS Double (also in the form OASIS REAL or OASIS DOUBLE)",
            "It has to match the argument name of the corresponding field declaration in the target component; see oasis def var in section 2.2.5 -1 : UNUSED but still required for parsing -86400 : coupling and/or I/O period for the field, in seconds -5 : number of transformations to be performed by OASIS3 on this field sstoc.nc",
            "var id [INTEGER; IN]: field ID (from corresponding oasis def var) date [INTEGER; IN]: as in oasis put, number of seconds (or any other time units as long as the same are used in all components and in the namcouple) in the run at the time of the call kinfo [INTEGER; OUT]: returned info code * OASIS ToRestOut (=9) if the field would be written both to a restart file and to an output file.",
            "The number of OpenMP threads per MPI process used by SCRIP is set by a dedicated environment variable OASIS OMP NUM THREADS, which can be different from the default number of threads per MPI process used elsewhere in the application, set by the environment variable OMP NUM THREADS ; in practice, OASIS OMP NUM THREADS has to be smaller or equal to OMP NUM THREADS.",
            "\u2022 int oasis c def var(int * var id, const char * name, const int il part id, const bundle size, const int kinout, const int var type) bundle size is a scalar integer, corresponding to the second entry of the Fortran var nodims array kinout can receive one of the two predefined constants OASIS In or OASIS Out (also in the form OASIS IN or OASIS OUT) var type can receive one of the two predefined constants OASIS Real or OASIS Double (also in the form OASIS REAL or OASIS DOUBLE)",
            "\u2022 EU Centre of Excellence ESiWACE2 , GA #823988 \u2022 EU IS-ENES3 -Infrastructure for the European Network for Earth System modelling -Phase 3 project (GA # 824084) We would like to thank the main past or present developers of OASIS (in alphabetical order, with the name of their institution at the time of their contribution to OASIS): Arnaud Caubel (LSCE/IPSL & FECIT/Fujitsu), Laure Coquart (CNRS/CERFACS) Anthony Craig (CER-FACS -consultant), Damien Declat (CERFACS), Italo Epicoco (CMCC), Rupert Ford (STFC), Philippe Gambron (STFC), Veronika Gayler (MPI-M&D), Josefine Ghattas (CERFACS), Christopher Goodyer (NAG) Jean Latour (CERFACS & Fujitsu-Fecit), Eric Maisonnave (CERFACS), Silvia Mocavero (CMCC), Andrea Piacentini (CERFACS -consultant) Elodie Rapaport (CERFACS), Sami Saarinen (ECMWF), Eric",
            "\u2022 int oasis c def var(int * var id, const char * name, const int il part id, const bundle size, const int kinout, const int var type) bundle size is a scalar integer, corresponding to the second entry of the Fortran var nodims array kinout can receive one of the two predefined constants OASIS In or OASIS Out (also in the form OASIS IN or OASIS OUT) var type can receive one of the two predefined constants OASIS Real or OASIS Double (also in the form OASIS REAL or OASIS DOUBLE)",
            "It provides the comprehensive sequence of any operations related to the coupling (field exchange through MPI, field output on disk, field interpolation and mapping, field reading on disk, restart writing, initialisation and termination phase of the OASIS3-MCT setup) so that any simulation slow down in link with the use of the OASIS library can be identified.",
            "info [INTEGER; OUT]: returned info code: * OASIS Sent (=4) if the field was sent to another component * OASIS LocTrans (=5) if the field was only used in a time transformation (not sent, not output) * OASIS ToRest (=6) if the field was written to a restart file only * OASIS Output (=7) if the field was written to an output file only * OASIS SentOut (=8) if the field was both written to an output file and sent to another component * OASIS ToRestOut (=9) if the field was written both to a restart file and to an output file.",
            "name [CHARACTER, OPTIONAL, IN]: Optional argument associating a name to the partition, mandatory if oasis def partition is called either for a grid decomposed not across all the processes of a component or if the related oasis def partition are not called in the same order on the different component processes; this argument is new since OASIS3-MCT 3.0 release and is linked to the greater flexibility in the configuration of components supported (see 2.1); it has a maximum length of 120 characters.",
            "\u2022 int oasis c def var(int * var id, const char * name, const int il part id, const bundle size, const int kinout, const int var type) bundle size is a scalar integer, corresponding to the second entry of the Fortran var nodims array kinout can receive one of the two predefined constants OASIS In or OASIS Out (also in the form OASIS IN or OASIS OUT) var type can receive one of the two predefined constants OASIS Real or OASIS Double (also in the form OASIS REAL or OASIS DOUBLE)",
            "info [INTEGER; OUT]: returned info code: * OASIS Recvd(=3) if the field was received from another component * OASIS FromRest (=10) if the field was read from a restart file only * OASIS Input (=11) if the field was read from an input file only * OASIS RecvOut (=12) if the field was both received from another component and written to an output file * OASIS FromRestOut (=13) if the field was both read from a restart file and written to an output file * OASIS Ok (=0) otherwise and no error occurred.",
            "Notice that for unstructured grids y size=1 bundle size should be coherent with the argument of same name in the corresponding oasis c def var fkind can take one of the two predefined constants OASIS Real or OASIS Double (also in the form OASIS REAL or OASIS DOUBLE) should be coherent with the argument ktype in oasis c def var storage can take one of the two predefined constants OASIS COL MAJOR or OASIS ROW MAJOR.",
            "Notice that for unstructured grids y size=1 bundle size should be coherent with the argument of same name in the corresponding oasis c def var fkind can take one of the two predefined constants OASIS Real or OASIS Double (also in the form OASIS REAL or OASIS DOUBLE) should be coherent with the argument ktype in oasis c def var storage can take one of the two predefined constants OASIS COL MAJOR or OASIS ROW MAJOR.",
            "\u2022 int oasis c def var(int * var id, const char * name, const int il part id, const bundle size, const int kinout, const int var type) bundle size is a scalar integer, corresponding to the second entry of the Fortran var nodims array kinout can receive one of the two predefined constants OASIS In or OASIS Out (also in the form OASIS IN or OASIS OUT) var type can receive one of the two predefined constants OASIS Real or OASIS Double (also in the form OASIS REAL or OASIS DOUBLE)",
            "\u2022 int oasis c def var(int * var id, const char * name, const int il part id, const bundle size, const int kinout, const int var type) bundle size is a scalar integer, corresponding to the second entry of the Fortran var nodims array kinout can receive one of the two predefined constants OASIS In or OASIS Out (also in the form OASIS IN or OASIS OUT) var type can receive one of the two predefined constants OASIS Real or OASIS Double (also in the form OASIS REAL or OASIS DOUBLE)",
            "info [INTEGER; OUT]: returned info code: * OASIS Sent (=4) if the field was sent to another component * OASIS LocTrans (=5) if the field was only used in a time transformation (not sent, not output) * OASIS ToRest (=6) if the field was written to a restart file only * OASIS Output (=7) if the field was written to an output file only * OASIS SentOut (=8) if the field was both written to an output file and sent to another component * OASIS ToRestOut (=9) if the field was written both to a restart file and to an output file.",
            "\u2022 int oasis c def var(int * var id, const char * name, const int il part id, const bundle size, const int kinout, const int var type) bundle size is a scalar integer, corresponding to the second entry of the Fortran var nodims array kinout can receive one of the two predefined constants OASIS In or OASIS Out (also in the form OASIS IN or OASIS OUT) var type can receive one of the two predefined constants OASIS Real or OASIS Double (also in the form OASIS REAL or OASIS DOUBLE)",
            "info [INTEGER; OUT]: returned info code: * OASIS Recvd(=3) if the field was received from another component * OASIS FromRest (=10) if the field was read from a restart file only * OASIS Input (=11) if the field was read from an input file only * OASIS RecvOut (=12) if the field was both received from another component and written to an output file * OASIS FromRestOut (=13) if the field was both read from a restart file and written to an output file * OASIS Ok (=0) otherwise and no error occurred.",
            "\u2022 int oasis c def var(int * var id, const char * name, const int il part id, const bundle size, const int kinout, const int var type) bundle size is a scalar integer, corresponding to the second entry of the Fortran var nodims array kinout can receive one of the two predefined constants OASIS In or OASIS Out (also in the form OASIS IN or OASIS OUT) var type can receive one of the two predefined constants OASIS Real or OASIS Double (also in the form OASIS REAL or OASIS DOUBLE)",
            "$TRANSFORM where $TRANSFORM can be -INSTANT: no time transformation, the instantaneous field is transferred; -ACCUMUL: the field accumulated over the previous coupling period is exchanged (the accumulation is simply done over the arrays field array provided as third argument to the oasis put calls without any specific weighting); -AVERAGE: the field averaged over the previous coupling period is transferred (the average is simply done over the arrays field array provided as third argument to the oasis put calls without any specific weighting); -T MIN: the minimum value of the field for each source grid point over the previous coupling period is transferred; -T MAX: the maximum value of the field for each source grid point over the previous coupling period is transferred; -ONCE: UNUSED, not supported in OASIS3-MCT."
        ]
    }
}
2026-04-05 07:02:15 urn:uuid:fa22c4cf-4175-4ce6-b91c-d16cf7f17b72 https://datalake.inria.fr https://inria.hal.science ["Offer","coar-notify:ReviewAction"]
{
    "@context": [
        "https://www.w3.org/ns/activitystreams",
        "https://purl.org/coar/notify"
    ],
    "id": "urn:uuid:fa22c4cf-4175-4ce6-b91c-d16cf7f17b72",
    "type": [
        "Offer",
        "coar-notify:ReviewAction"
    ],
    "actor": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "name": "Inria DataLake"
    },
    "origin": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "inbox": "https://prod-datadcis-api.inria.fr/coar/inbox"
    },
    "target": {
        "id": "https://inria.hal.science",
        "type": "Service",
        "inbox": "https://inbox.hal.science"
    },
    "object": {
        "id": "https://hal.science/hal-04739698v1",
        "ietf:cite-as": null,
        "sorg:citation": {
            "@context": "https://doi.org/10.5063/schema/codemeta-2.0",
            "type": "SoftwareSourceCode",
            "name": "components",
            "codeRepository": null,
            "referencePublication": null
        },
        "mentionType": "software",
        "mentionContext": [
            "\u2022 9-python fortran C-multi intracomm: illustrates the set-up of an intracommunicator between a Fortran, a C and a python components using OASIS3-MCT; a bcast is then realised to share some data."
        ]
    }
}
2026-04-05 07:02:15 urn:uuid:7564402e-fc05-45e8-bd6e-de617231ff3c https://datalake.inria.fr https://inria.hal.science ["Offer","coar-notify:ReviewAction"]
{
    "@context": [
        "https://www.w3.org/ns/activitystreams",
        "https://purl.org/coar/notify"
    ],
    "id": "urn:uuid:7564402e-fc05-45e8-bd6e-de617231ff3c",
    "type": [
        "Offer",
        "coar-notify:ReviewAction"
    ],
    "actor": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "name": "Inria DataLake"
    },
    "origin": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "inbox": "https://prod-datadcis-api.inria.fr/coar/inbox"
    },
    "target": {
        "id": "https://inria.hal.science",
        "type": "Service",
        "inbox": "https://inbox.hal.science"
    },
    "object": {
        "id": "https://hal.science/hal-04739698v1",
        "ietf:cite-as": null,
        "sorg:citation": {
            "@context": "https://doi.org/10.5063/schema/codemeta-2.0",
            "type": "SoftwareSourceCode",
            "name": "BLASNEW",
            "codeRepository": null,
            "referencePublication": null
        },
        "mentionType": "software",
        "mentionContext": [
            "BLASNEW performs a scalar multiply or scalar add to any destination field.",
            "\u2022 BLASNEW:",
            "# BLASNEW operation $XMULT $NBFIELDS where $XMULT is the multiplicative coefficient of the destination field.",
            "-Field combination with BLASOLD and BLASNEW; these transformations only support multiplication and addition terms to the fields (see section 4.2).",
            "EXPOUT 182 149 128 64 toce atmo LAG=+14400 SEQ=+1 P 2 P 0 LOCTRANS CHECKIN MAPPING BLASNEW CHECKOUT # AVERAGE INT=1 map_toce_atmo_120315.nc src opt 1.0 1 CONSTANT 273.15 INT=1 # # Field 2 CONSFTOT SOHEFLDO 6 86400 4 flxat.nc"
        ]
    }
}
2026-04-05 07:02:08 urn:uuid:f707517b-f097-4c1c-bfa3-5de41cff62c6 https://datalake.inria.fr https://inria.hal.science ["Offer","coar-notify:ReviewAction"]
{
    "@context": [
        "https://www.w3.org/ns/activitystreams",
        "https://purl.org/coar/notify"
    ],
    "id": "urn:uuid:f707517b-f097-4c1c-bfa3-5de41cff62c6",
    "type": [
        "Offer",
        "coar-notify:ReviewAction"
    ],
    "actor": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "name": "Inria DataLake"
    },
    "origin": {
        "id": "https://datalake.inria.fr",
        "type": "Service",
        "inbox": "https://prod-datadcis-api.inria.fr/coar/inbox"
    },
    "target": {
        "id": "https://inria.hal.science",
        "type": "Service",
        "inbox": "https://inbox.hal.science"
    },
    "object": {
        "id": "https://hal.science/tel-01958588v1",
        "ietf:cite-as": null,
        "sorg:citation": {
            "@context": "https://doi.org/10.5063/schema/codemeta-2.0",
            "type": "SoftwareSourceCode",
            "name": "******* ******* ******* ******* 0",
            "codeRepository": null,
            "referencePublication": null
        },
        "mentionType": "software",
        "mentionContext": [
            "108.18 ******* ******* ******* ******* 0.01 -0.11 0.09 0.01 -0.01 -0.02 0.06 -0.03 1928-8-31 1 7 228.93 276.16 -202.88 -302.21",
            "i 4 -0.18 1928-8-24 2 43 101.74 100.83 -347.75 145.18 ******* ******* ******* ******* 0.03 -0.14 0.21 -0.10 -0.01 -0.04 0.22 -0.17 1928-8-25 2 1 8 24.44 -31.30",
            "73.71 289.43 ....... ******* ******* ******* o.04 1913-9-22 19 35 -152.04 -55.66 -73.16 280.86 ******* ******* ******* ******* 0.08 1913-9-24 21 8 11.01 -129.33 -240.08 358.40 ******* ******* ....... **.*.*."
        ]
    }
}