From b6ef758dce59b1d02991dbbf1819256420d671f9 Mon Sep 17 00:00:00 2001 From: Joel Trubilowicz Date: Tue, 7 Oct 2025 19:21:20 +0000 Subject: [PATCH 1/5] Successfully run on GC Science ppp5 --- etc/clusters/eccc-science.json | 29 ++++++------- etc/schedulers/pbs.json | 6 +++ examples/Casrv3p1_example.sh | 45 +++++++++++++++++++++ examples/rdrs_example_ssrb_1980_2018.sh | 13 +++--- extract-dataset.sh | 42 ++++++++++++++++--- var/repos/builtin/recipes/eccc-casr/casr.sh | 4 +- 6 files changed, 108 insertions(+), 31 deletions(-) create mode 100644 etc/schedulers/pbs.json create mode 100755 examples/Casrv3p1_example.sh diff --git a/etc/clusters/eccc-science.json b/etc/clusters/eccc-science.json index 941abf4..3934c3f 100644 --- a/etc/clusters/eccc-science.json +++ b/etc/clusters/eccc-science.json @@ -1,26 +1,21 @@ { "scheduler": "pbs", "specs": { - "cpus": 1, - "time": "04:00:00", + "cpus": 8, + "time": "01:00:00", "nodes": 1, - "partition": "", - "account": "", - "mem": "8000M" + "mem": "16000M" }, "modules": { "preload": [ - "module -q purge", - "module -q load StdEnv/2023", - "module -q load gcc/12.3" - ], - "gdal": "module -q load gdal/3.9.1", - "cdo": "module -q load cdo/2.2.2", - "ncks": "module -q load nco/5.1.7" - }, - "executables": { - "gdal": "", - "nco": "", - "cdo": "" + "module -q purge", + ". ssmuse-sh -x /fs/ssm/main/opt/gcc/gcc-4.9.1" + ], + "compiler": ". ssmuse-sh -x /fs/ssm/main/opt/gcc/gcc-4.9.1", + "mpi": ". ssmuse-sh -x /fs/ssm/main/opt/openmpi/openmpi-2.1.1/gcc--hpcx-1.8", + "gdal": ". ssmuse-sh -x /fs/ssm/main/opt/gdal/gdal-3.1.3", + "cdo": ". r.load.dot crd/ccrm/main/opt/cdo/cdo_2.1.1_rhel-8-amd64-64", + "ncl": ". r.load.dot comm/eccc/all/opt/ncl-ncarg/6.4.0/ncl_6.4.0_all", + "nco": " . r.load.dot cmd/cmds/ext/master/nco_5.0.5-3_rhel-8-amd64-64" } } diff --git a/etc/schedulers/pbs.json b/etc/schedulers/pbs.json new file mode 100644 index 0000000..a720855 --- /dev/null +++ b/etc/schedulers/pbs.json @@ -0,0 +1,6 @@ +{ + "environment_variables": { + "array_task_id": "$PBS_ARRAY_INDEX", + "array_job_id": "$PBS_JOBID" + } +} diff --git a/examples/Casrv3p1_example.sh b/examples/Casrv3p1_example.sh new file mode 100755 index 0000000..7356922 --- /dev/null +++ b/examples/Casrv3p1_example.sh @@ -0,0 +1,45 @@ +#!/bin/bash + +# Meteorological Data Processing Workflow +# Copyright (C) 2022, University of Saskatchewan +# +# This file is part of Meteorological Data Processing Workflow +# +# This program is free software: you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation, either version 3 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, see . + +# This is a simple example to extract ECCC CasrV3.1 data for the +# South Saskatchewan River Basin (SSRB) approximate extents +# from Jan 2015 to Dec 2018. + +# As is mentioned on the main webpage of the repository, it is +# recommended to submit annual jobs for this dataset. + +# This example is meant to be called from the home directory, as is required by GC Science PBS job submission +cd datatool +echo "The current directory is: $(pwd)" + +# chunking done on an 'annual' basis +./extract-dataset.sh --dataset="casr" \ + --dataset-dir="/home/scar700/data/ppp6/CaSRv3.1/postproc_casr4caspar_20250416/link2out4pilot_netcdf/" \ + --output-dir="$HOME/scratch/casr31_output/" \ + --start-date="2015-01-01" \ + --end-date="2018-12-30" \ + --lat-lims=49,54 \ + --lon-lims=-120,-98 \ + --variable="CaSR_v3.1_P_TT_1.5m,CaSR_v3.1_A_PR0_SFC" \ + --prefix="casrv3.1_" \ + --cluster="./etc/clusters/eccc-science.json" \ + --email="joel.trubilowicz@ec.gc.ca" \ + -j; + diff --git a/examples/rdrs_example_ssrb_1980_2018.sh b/examples/rdrs_example_ssrb_1980_2018.sh index 129203c..e5943ca 100755 --- a/examples/rdrs_example_ssrb_1980_2018.sh +++ b/examples/rdrs_example_ssrb_1980_2018.sh @@ -30,15 +30,16 @@ cd .. echo "The current directory is: $(pwd)" # chunking done on an 'annual' basis -./extract-dataset.sh --dataset=RDRS \ - --dataset-dir="/project/rpp-kshook/Model_Output/RDRSv2.1" \ - --output-dir="$HOME/scratch/rdrs_output/" \ +./extract-dataset.sh --dataset=CaSR \ + --dataset-dir="/home/scar700/data/ppp6/CaSRv3.1/postproc_casr4caspar_20250416/link2out4pilot_netcdf" \ + --output-dir="$HOME/scratch/casr31_output/" \ --start-date="1980-01-01" \ --end-date="2018-12-30" \ --lat-lims=49,54 \ --lon-lims=-120,-98 \ - --variable="RDRS_v2.1_P_P0_SFC,RDRS_v2.1_P_HU_1.5m,RDRS_v2.1_P_TT_1.5m,RDRS_v2.1_P_UVC_10m,RDRS_v2.1_A_PR0_SFC,RDRS_v2.1_P_FB_SFC,RDRS_v2.1_P_FI_SFC" \ - --prefix="rdrsv2.1_" \ - --email="youremail@company.ca" \ + --variable="CaSR_v3.1_P_TT_1.5m,CaSR_v3.1_A_PR0_SFC" \ + --prefix="casrv3.1_" \ + --cluster="./etc/clusters/eccc_science.json" + --email="joel.trubilowicz@ec.gc.ca" \ -j; diff --git a/extract-dataset.sh b/extract-dataset.sh index 1f4d57f..f2558e5 100755 --- a/extract-dataset.sh +++ b/extract-dataset.sh @@ -550,7 +550,13 @@ function call_processing_func () { --arg "ensembleArr" "${ensemble}" \ --arg "modelArr" "${model}" \ --arg "scenarioArr" "${scenario}" \ - '$ARGS.named | with_entries(.value |= split(","))' \ + '{ + startDateArr: ($startDateArr | split(",")), + endDateArr: ($endDateArr | split(",")), + ensembleArr: ($ensembleArr | split(",")), + modelArr: ($modelArr | split(",")), + scenarioArr: ($scenarioArr | split(",")) + }' )" # job chunk variable information @@ -563,7 +569,15 @@ function call_processing_func () { --arg "dateIter" "$dateIter" \ --arg "ensembleIter" "$ensembleIter" \ --arg "modelIter" "$modelIter" \ - '$ARGS.named' + '{ + ensembleLen: $ensembleLen, + modelLen: $modelLen, + scenarioLen: $scenarioLen, + dateLen: $dateLen, + dateIter: $dateIter, + ensembleIter: $ensembleIter, + modelIter: $modelIter + }' )" # scheduler information @@ -584,8 +598,14 @@ function call_processing_func () { --arg "logDir" "$logDir" \ --arg "email" "$email" \ --arg "parsable" "$parsable" \ - --argjson "specs" "$(jq -r '.specs' $cluster)" \ - '$ARGS.named + $specs | del(.specs)' \ + --argjson specs "$(jq '.specs' "$cluster")" \ + '{ + jobArrlen: $jobArrLen, + scriptName: $scriptName, + logDir: $logDir, + email: $email, + parsable: $parsable + } + $specs' )" # job script information @@ -604,8 +624,18 @@ function call_processing_func () { --arg "latLims" "${funcArgs[latLims]}" \ --arg "lonLims" "${funcArgs[lonLims]}" \ --arg "prefix" "${funcArgs[prefixStr]}" \ - --arg "cache" "${funcArgs[cache]}" \ - '$ARGS.named' \ + --arg "cache" "${funcArgs[cache]}" \ + '{ + scriptFile: $scriptFile, + datasetDir: $datasetDir, + variable: $variable, + outputDir: $outputDir, + timeScale: $timeScale, + latLims: $latLims, + lonLims: $lonLims, + prefix: $prefix, + cache: $cache + }' )" # job module init information - not JSON as echoed as is diff --git a/var/repos/builtin/recipes/eccc-casr/casr.sh b/var/repos/builtin/recipes/eccc-casr/casr.sh index 55573ef..bb6676e 100755 --- a/var/repos/builtin/recipes/eccc-casr/casr.sh +++ b/var/repos/builtin/recipes/eccc-casr/casr.sh @@ -191,12 +191,12 @@ latLims="${minLat},${maxLat}" lonLims="${minLon},${maxLon}" # extract the associated indices corresponding to $latLims and $lonLims -coordIdx="$(ncl -nQ 'coord_file='\"$domainFile\" 'minlat='"$minLat" 'maxlat='"$maxLat" 'minlon='"$minLon" 'maxlon='"$maxLon" "$coordIdxScript")" +coordIdx="$(singularity exec $NCL_SINGULARITY_IMAGE ncl -nQ 'coord_file='\"$domainFile\" 'minlat='"$minLat" 'maxlat='"$maxLat" 'minlon='"$minLon" 'maxlon='"$maxLon" "$coordIdxScript")" # if spatial index out-of-bound, i.e., 'ERROR' is return if [[ "${coordIdx}" == "ERROR" ]]; then # extract the closest index values - coordIdx="$(ncl -nQ 'coord_file='\"$domainFile\" 'minlat='"$minLat" 'maxlat='"$maxLat" 'minlon='"$minLon" 'maxlon='"$maxLon" "$coordClosestIdxScript")" + coordIdx="$(singularity exec $NCL_SINGULARITY_IMAGE ncl -nQ 'coord_file='\"$domainFile\" 'minlat='"$minLat" 'maxlat='"$maxLat" 'minlon='"$minLon" 'maxlon='"$maxLon" "$coordClosestIdxScript")" fi # parse the output index for latitude and longitude From e2705eecf5963501385574f0b941e13a392a6315 Mon Sep 17 00:00:00 2001 From: Joel Trubilowicz Date: Tue, 7 Oct 2025 21:40:53 +0000 Subject: [PATCH 2/5] fixed pbspro directive header --- etc/schedulers/pbs.m4 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/etc/schedulers/pbs.m4 b/etc/schedulers/pbs.m4 index 5faf12c..25201fc 100644 --- a/etc/schedulers/pbs.m4 +++ b/etc/schedulers/pbs.m4 @@ -3,8 +3,8 @@ `#'PBS -l select=__NODES__:ncpus=__CPUS__:mem=__MEM__ `#'PBS -l walltime=__TIME__ `#'PBS -N DATA-__SCRIPTNAME__ -`#'PBS -e __LOGDIR__/datatool_$PBS_JOBID-$PBS_ARRAY_INDEX_err.txt -`#'PBS -o __LOGDIR__/datatool_$PBS_JOBID-$PBS_ARRAY_INDEX.txt +`#'PBS -e __LOGDIR__/datatool_err.txt +`#'PBS -o __LOGDIR__/datatool_log.txt ifdef(`__ACCOUNT__', `#PBS -A '__ACCOUNT__, `dnl') ifdef(`__PARTITION__', `#PBS -q '__PARTITION__, `dnl') ifdef(`__EMAIL__', From e8d72310ec3556156ffa78ca70fba7b475141222 Mon Sep 17 00:00:00 2001 From: Joel Trubilowicz Date: Tue, 14 Oct 2025 22:14:55 +0000 Subject: [PATCH 3/5] started recipe for casr rivers by copying RDRS --- .../builtin/recipes/eccc-casrriv/LICENSE | 675 ++++++++++++++++++ .../builtin/recipes/eccc-casrriv/README.md | 79 ++ .../builtin/recipes/eccc-casrriv/cassriv.sh | 316 ++++++++ 3 files changed, 1070 insertions(+) create mode 100644 var/repos/builtin/recipes/eccc-casrriv/LICENSE create mode 100644 var/repos/builtin/recipes/eccc-casrriv/README.md create mode 100755 var/repos/builtin/recipes/eccc-casrriv/cassriv.sh diff --git a/var/repos/builtin/recipes/eccc-casrriv/LICENSE b/var/repos/builtin/recipes/eccc-casrriv/LICENSE new file mode 100644 index 0000000..53d1f3d --- /dev/null +++ b/var/repos/builtin/recipes/eccc-casrriv/LICENSE @@ -0,0 +1,675 @@ + GNU GENERAL PUBLIC LICENSE + Version 3, 29 June 2007 + + Copyright (C) 2007 Free Software Foundation, Inc. + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The GNU General Public License is a free, copyleft license for +software and other kinds of works. + + The licenses for most software and other practical works are designed +to take away your freedom to share and change the works. By contrast, +the GNU General Public License is intended to guarantee your freedom to +share and change all versions of a program--to make sure it remains free +software for all its users. We, the Free Software Foundation, use the +GNU General Public License for most of our software; it applies also to +any other work released this way by its authors. You can apply it to +your programs, too. + + When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge for +them if you wish), that you receive source code or can get it if you +want it, that you can change the software or use pieces of it in new +free programs, and that you know you can do these things. + + To protect your rights, we need to prevent others from denying you +these rights or asking you to surrender the rights. Therefore, you have +certain responsibilities if you distribute copies of the software, or if +you modify it: responsibilities to respect the freedom of others. + + For example, if you distribute copies of such a program, whether +gratis or for a fee, you must pass on to the recipients the same +freedoms that you received. You must make sure that they, too, receive +or can get the source code. And you must show them these terms so they +know their rights. + + Developers that use the GNU GPL protect your rights with two steps: +(1) assert copyright on the software, and (2) offer you this License +giving you legal permission to copy, distribute and/or modify it. + + For the developers' and authors' protection, the GPL clearly explains +that there is no warranty for this free software. For both users' and +authors' sake, the GPL requires that modified versions be marked as +changed, so that their problems will not be attributed erroneously to +authors of previous versions. + + Some devices are designed to deny users access to install or run +modified versions of the software inside them, although the manufacturer +can do so. This is fundamentally incompatible with the aim of +protecting users' freedom to change the software. The systematic +pattern of such abuse occurs in the area of products for individuals to +use, which is precisely where it is most unacceptable. Therefore, we +have designed this version of the GPL to prohibit the practice for those +products. If such problems arise substantially in other domains, we +stand ready to extend this provision to those domains in future versions +of the GPL, as needed to protect the freedom of users. + + Finally, every program is threatened constantly by software patents. +States should not allow patents to restrict development and use of +software on general-purpose computers, but in those that do, we wish to +avoid the special danger that patents applied to a free program could +make it effectively proprietary. To prevent this, the GPL assures that +patents cannot be used to render the program non-free. + + The precise terms and conditions for copying, distribution and +modification follow. + + TERMS AND CONDITIONS + + 0. Definitions. + + "This License" refers to version 3 of the GNU General Public License. + + "Copyright" also means copyright-like laws that apply to other kinds of +works, such as semiconductor masks. + + "The Program" refers to any copyrightable work licensed under this +License. Each licensee is addressed as "you". "Licensees" and +"recipients" may be individuals or organizations. + + To "modify" a work means to copy from or adapt all or part of the work +in a fashion requiring copyright permission, other than the making of an +exact copy. The resulting work is called a "modified version" of the +earlier work or a work "based on" the earlier work. + + A "covered work" means either the unmodified Program or a work based +on the Program. + + To "propagate" a work means to do anything with it that, without +permission, would make you directly or secondarily liable for +infringement under applicable copyright law, except executing it on a +computer or modifying a private copy. Propagation includes copying, +distribution (with or without modification), making available to the +public, and in some countries other activities as well. + + To "convey" a work means any kind of propagation that enables other +parties to make or receive copies. Mere interaction with a user through +a computer network, with no transfer of a copy, is not conveying. + + An interactive user interface displays "Appropriate Legal Notices" +to the extent that it includes a convenient and prominently visible +feature that (1) displays an appropriate copyright notice, and (2) +tells the user that there is no warranty for the work (except to the +extent that warranties are provided), that licensees may convey the +work under this License, and how to view a copy of this License. If +the interface presents a list of user commands or options, such as a +menu, a prominent item in the list meets this criterion. + + 1. Source Code. + + The "source code" for a work means the preferred form of the work +for making modifications to it. "Object code" means any non-source +form of a work. + + A "Standard Interface" means an interface that either is an official +standard defined by a recognized standards body, or, in the case of +interfaces specified for a particular programming language, one that +is widely used among developers working in that language. + + The "System Libraries" of an executable work include anything, other +than the work as a whole, that (a) is included in the normal form of +packaging a Major Component, but which is not part of that Major +Component, and (b) serves only to enable use of the work with that +Major Component, or to implement a Standard Interface for which an +implementation is available to the public in source code form. A +"Major Component", in this context, means a major essential component +(kernel, window system, and so on) of the specific operating system +(if any) on which the executable work runs, or a compiler used to +produce the work, or an object code interpreter used to run it. + + The "Corresponding Source" for a work in object code form means all +the source code needed to generate, install, and (for an executable +work) run the object code and to modify the work, including scripts to +control those activities. However, it does not include the work's +System Libraries, or general-purpose tools or generally available free +programs which are used unmodified in performing those activities but +which are not part of the work. For example, Corresponding Source +includes interface definition files associated with source files for +the work, and the source code for shared libraries and dynamically +linked subprograms that the work is specifically designed to require, +such as by intimate data communication or control flow between those +subprograms and other parts of the work. + + The Corresponding Source need not include anything that users +can regenerate automatically from other parts of the Corresponding +Source. + + The Corresponding Source for a work in source code form is that +same work. + + 2. Basic Permissions. + + All rights granted under this License are granted for the term of +copyright on the Program, and are irrevocable provided the stated +conditions are met. This License explicitly affirms your unlimited +permission to run the unmodified Program. The output from running a +covered work is covered by this License only if the output, given its +content, constitutes a covered work. This License acknowledges your +rights of fair use or other equivalent, as provided by copyright law. + + You may make, run and propagate covered works that you do not +convey, without conditions so long as your license otherwise remains +in force. You may convey covered works to others for the sole purpose +of having them make modifications exclusively for you, or provide you +with facilities for running those works, provided that you comply with +the terms of this License in conveying all material for which you do +not control copyright. Those thus making or running the covered works +for you must do so exclusively on your behalf, under your direction +and control, on terms that prohibit them from making any copies of +your copyrighted material outside their relationship with you. + + Conveying under any other circumstances is permitted solely under +the conditions stated below. Sublicensing is not allowed; section 10 +makes it unnecessary. + + 3. Protecting Users' Legal Rights From Anti-Circumvention Law. + + No covered work shall be deemed part of an effective technological +measure under any applicable law fulfilling obligations under article +11 of the WIPO copyright treaty adopted on 20 December 1996, or +similar laws prohibiting or restricting circumvention of such +measures. + + When you convey a covered work, you waive any legal power to forbid +circumvention of technological measures to the extent such circumvention +is effected by exercising rights under this License with respect to +the covered work, and you disclaim any intention to limit operation or +modification of the work as a means of enforcing, against the work's +users, your or third parties' legal rights to forbid circumvention of +technological measures. + + 4. Conveying Verbatim Copies. + + You may convey verbatim copies of the Program's source code as you +receive it, in any medium, provided that you conspicuously and +appropriately publish on each copy an appropriate copyright notice; +keep intact all notices stating that this License and any +non-permissive terms added in accord with section 7 apply to the code; +keep intact all notices of the absence of any warranty; and give all +recipients a copy of this License along with the Program. + + You may charge any price or no price for each copy that you convey, +and you may offer support or warranty protection for a fee. + + 5. Conveying Modified Source Versions. + + You may convey a work based on the Program, or the modifications to +produce it from the Program, in the form of source code under the +terms of section 4, provided that you also meet all of these conditions: + + a) The work must carry prominent notices stating that you modified + it, and giving a relevant date. + + b) The work must carry prominent notices stating that it is + released under this License and any conditions added under section + 7. This requirement modifies the requirement in section 4 to + "keep intact all notices". + + c) You must license the entire work, as a whole, under this + License to anyone who comes into possession of a copy. This + License will therefore apply, along with any applicable section 7 + additional terms, to the whole of the work, and all its parts, + regardless of how they are packaged. This License gives no + permission to license the work in any other way, but it does not + invalidate such permission if you have separately received it. + + d) If the work has interactive user interfaces, each must display + Appropriate Legal Notices; however, if the Program has interactive + interfaces that do not display Appropriate Legal Notices, your + work need not make them do so. + + A compilation of a covered work with other separate and independent +works, which are not by their nature extensions of the covered work, +and which are not combined with it such as to form a larger program, +in or on a volume of a storage or distribution medium, is called an +"aggregate" if the compilation and its resulting copyright are not +used to limit the access or legal rights of the compilation's users +beyond what the individual works permit. Inclusion of a covered work +in an aggregate does not cause this License to apply to the other +parts of the aggregate. + + 6. Conveying Non-Source Forms. + + You may convey a covered work in object code form under the terms +of sections 4 and 5, provided that you also convey the +machine-readable Corresponding Source under the terms of this License, +in one of these ways: + + a) Convey the object code in, or embodied in, a physical product + (including a physical distribution medium), accompanied by the + Corresponding Source fixed on a durable physical medium + customarily used for software interchange. + + b) Convey the object code in, or embodied in, a physical product + (including a physical distribution medium), accompanied by a + written offer, valid for at least three years and valid for as + long as you offer spare parts or customer support for that product + model, to give anyone who possesses the object code either (1) a + copy of the Corresponding Source for all the software in the + product that is covered by this License, on a durable physical + medium customarily used for software interchange, for a price no + more than your reasonable cost of physically performing this + conveying of source, or (2) access to copy the + Corresponding Source from a network server at no charge. + + c) Convey individual copies of the object code with a copy of the + written offer to provide the Corresponding Source. This + alternative is allowed only occasionally and noncommercially, and + only if you received the object code with such an offer, in accord + with subsection 6b. + + d) Convey the object code by offering access from a designated + place (gratis or for a charge), and offer equivalent access to the + Corresponding Source in the same way through the same place at no + further charge. You need not require recipients to copy the + Corresponding Source along with the object code. If the place to + copy the object code is a network server, the Corresponding Source + may be on a different server (operated by you or a third party) + that supports equivalent copying facilities, provided you maintain + clear directions next to the object code saying where to find the + Corresponding Source. Regardless of what server hosts the + Corresponding Source, you remain obligated to ensure that it is + available for as long as needed to satisfy these requirements. + + e) Convey the object code using peer-to-peer transmission, provided + you inform other peers where the object code and Corresponding + Source of the work are being offered to the general public at no + charge under subsection 6d. + + A separable portion of the object code, whose source code is excluded +from the Corresponding Source as a System Library, need not be +included in conveying the object code work. + + A "User Product" is either (1) a "consumer product", which means any +tangible personal property which is normally used for personal, family, +or household purposes, or (2) anything designed or sold for incorporation +into a dwelling. In determining whether a product is a consumer product, +doubtful cases shall be resolved in favor of coverage. For a particular +product received by a particular user, "normally used" refers to a +typical or common use of that class of product, regardless of the status +of the particular user or of the way in which the particular user +actually uses, or expects or is expected to use, the product. A product +is a consumer product regardless of whether the product has substantial +commercial, industrial or non-consumer uses, unless such uses represent +the only significant mode of use of the product. + + "Installation Information" for a User Product means any methods, +procedures, authorization keys, or other information required to install +and execute modified versions of a covered work in that User Product from +a modified version of its Corresponding Source. The information must +suffice to ensure that the continued functioning of the modified object +code is in no case prevented or interfered with solely because +modification has been made. + + If you convey an object code work under this section in, or with, or +specifically for use in, a User Product, and the conveying occurs as +part of a transaction in which the right of possession and use of the +User Product is transferred to the recipient in perpetuity or for a +fixed term (regardless of how the transaction is characterized), the +Corresponding Source conveyed under this section must be accompanied +by the Installation Information. But this requirement does not apply +if neither you nor any third party retains the ability to install +modified object code on the User Product (for example, the work has +been installed in ROM). + + The requirement to provide Installation Information does not include a +requirement to continue to provide support service, warranty, or updates +for a work that has been modified or installed by the recipient, or for +the User Product in which it has been modified or installed. Access to a +network may be denied when the modification itself materially and +adversely affects the operation of the network or violates the rules and +protocols for communication across the network. + + Corresponding Source conveyed, and Installation Information provided, +in accord with this section must be in a format that is publicly +documented (and with an implementation available to the public in +source code form), and must require no special password or key for +unpacking, reading or copying. + + 7. Additional Terms. + + "Additional permissions" are terms that supplement the terms of this +License by making exceptions from one or more of its conditions. +Additional permissions that are applicable to the entire Program shall +be treated as though they were included in this License, to the extent +that they are valid under applicable law. If additional permissions +apply only to part of the Program, that part may be used separately +under those permissions, but the entire Program remains governed by +this License without regard to the additional permissions. + + When you convey a copy of a covered work, you may at your option +remove any additional permissions from that copy, or from any part of +it. (Additional permissions may be written to require their own +removal in certain cases when you modify the work.) You may place +additional permissions on material, added by you to a covered work, +for which you have or can give appropriate copyright permission. + + Notwithstanding any other provision of this License, for material you +add to a covered work, you may (if authorized by the copyright holders of +that material) supplement the terms of this License with terms: + + a) Disclaiming warranty or limiting liability differently from the + terms of sections 15 and 16 of this License; or + + b) Requiring preservation of specified reasonable legal notices or + author attributions in that material or in the Appropriate Legal + Notices displayed by works containing it; or + + c) Prohibiting misrepresentation of the origin of that material, or + requiring that modified versions of such material be marked in + reasonable ways as different from the original version; or + + d) Limiting the use for publicity purposes of names of licensors or + authors of the material; or + + e) Declining to grant rights under trademark law for use of some + trade names, trademarks, or service marks; or + + f) Requiring indemnification of licensors and authors of that + material by anyone who conveys the material (or modified versions of + it) with contractual assumptions of liability to the recipient, for + any liability that these contractual assumptions directly impose on + those licensors and authors. + + All other non-permissive additional terms are considered "further +restrictions" within the meaning of section 10. If the Program as you +received it, or any part of it, contains a notice stating that it is +governed by this License along with a term that is a further +restriction, you may remove that term. If a license document contains +a further restriction but permits relicensing or conveying under this +License, you may add to a covered work material governed by the terms +of that license document, provided that the further restriction does +not survive such relicensing or conveying. + + If you add terms to a covered work in accord with this section, you +must place, in the relevant source files, a statement of the +additional terms that apply to those files, or a notice indicating +where to find the applicable terms. + + Additional terms, permissive or non-permissive, may be stated in the +form of a separately written license, or stated as exceptions; +the above requirements apply either way. + + 8. Termination. + + You may not propagate or modify a covered work except as expressly +provided under this License. Any attempt otherwise to propagate or +modify it is void, and will automatically terminate your rights under +this License (including any patent licenses granted under the third +paragraph of section 11). + + However, if you cease all violation of this License, then your +license from a particular copyright holder is reinstated (a) +provisionally, unless and until the copyright holder explicitly and +finally terminates your license, and (b) permanently, if the copyright +holder fails to notify you of the violation by some reasonable means +prior to 60 days after the cessation. + + Moreover, your license from a particular copyright holder is +reinstated permanently if the copyright holder notifies you of the +violation by some reasonable means, this is the first time you have +received notice of violation of this License (for any work) from that +copyright holder, and you cure the violation prior to 30 days after +your receipt of the notice. + + Termination of your rights under this section does not terminate the +licenses of parties who have received copies or rights from you under +this License. If your rights have been terminated and not permanently +reinstated, you do not qualify to receive new licenses for the same +material under section 10. + + 9. Acceptance Not Required for Having Copies. + + You are not required to accept this License in order to receive or +run a copy of the Program. Ancillary propagation of a covered work +occurring solely as a consequence of using peer-to-peer transmission +to receive a copy likewise does not require acceptance. However, +nothing other than this License grants you permission to propagate or +modify any covered work. These actions infringe copyright if you do +not accept this License. Therefore, by modifying or propagating a +covered work, you indicate your acceptance of this License to do so. + + 10. Automatic Licensing of Downstream Recipients. + + Each time you convey a covered work, the recipient automatically +receives a license from the original licensors, to run, modify and +propagate that work, subject to this License. You are not responsible +for enforcing compliance by third parties with this License. + + An "entity transaction" is a transaction transferring control of an +organization, or substantially all assets of one, or subdividing an +organization, or merging organizations. If propagation of a covered +work results from an entity transaction, each party to that +transaction who receives a copy of the work also receives whatever +licenses to the work the party's predecessor in interest had or could +give under the previous paragraph, plus a right to possession of the +Corresponding Source of the work from the predecessor in interest, if +the predecessor has it or can get it with reasonable efforts. + + You may not impose any further restrictions on the exercise of the +rights granted or affirmed under this License. For example, you may +not impose a license fee, royalty, or other charge for exercise of +rights granted under this License, and you may not initiate litigation +(including a cross-claim or counterclaim in a lawsuit) alleging that +any patent claim is infringed by making, using, selling, offering for +sale, or importing the Program or any portion of it. + + 11. Patents. + + A "contributor" is a copyright holder who authorizes use under this +License of the Program or a work on which the Program is based. The +work thus licensed is called the contributor's "contributor version". + + A contributor's "essential patent claims" are all patent claims +owned or controlled by the contributor, whether already acquired or +hereafter acquired, that would be infringed by some manner, permitted +by this License, of making, using, or selling its contributor version, +but do not include claims that would be infringed only as a +consequence of further modification of the contributor version. For +purposes of this definition, "control" includes the right to grant +patent sublicenses in a manner consistent with the requirements of +this License. + + Each contributor grants you a non-exclusive, worldwide, royalty-free +patent license under the contributor's essential patent claims, to +make, use, sell, offer for sale, import and otherwise run, modify and +propagate the contents of its contributor version. + + In the following three paragraphs, a "patent license" is any express +agreement or commitment, however denominated, not to enforce a patent +(such as an express permission to practice a patent or covenant not to +sue for patent infringement). To "grant" such a patent license to a +party means to make such an agreement or commitment not to enforce a +patent against the party. + + If you convey a covered work, knowingly relying on a patent license, +and the Corresponding Source of the work is not available for anyone +to copy, free of charge and under the terms of this License, through a +publicly available network server or other readily accessible means, +then you must either (1) cause the Corresponding Source to be so +available, or (2) arrange to deprive yourself of the benefit of the +patent license for this particular work, or (3) arrange, in a manner +consistent with the requirements of this License, to extend the patent +license to downstream recipients. "Knowingly relying" means you have +actual knowledge that, but for the patent license, your conveying the +covered work in a country, or your recipient's use of the covered work +in a country, would infringe one or more identifiable patents in that +country that you have reason to believe are valid. + + If, pursuant to or in connection with a single transaction or +arrangement, you convey, or propagate by procuring conveyance of, a +covered work, and grant a patent license to some of the parties +receiving the covered work authorizing them to use, propagate, modify +or convey a specific copy of the covered work, then the patent license +you grant is automatically extended to all recipients of the covered +work and works based on it. + + A patent license is "discriminatory" if it does not include within +the scope of its coverage, prohibits the exercise of, or is +conditioned on the non-exercise of one or more of the rights that are +specifically granted under this License. You may not convey a covered +work if you are a party to an arrangement with a third party that is +in the business of distributing software, under which you make payment +to the third party based on the extent of your activity of conveying +the work, and under which the third party grants, to any of the +parties who would receive the covered work from you, a discriminatory +patent license (a) in connection with copies of the covered work +conveyed by you (or copies made from those copies), or (b) primarily +for and in connection with specific products or compilations that +contain the covered work, unless you entered into that arrangement, +or that patent license was granted, prior to 28 March 2007. + + Nothing in this License shall be construed as excluding or limiting +any implied license or other defenses to infringement that may +otherwise be available to you under applicable patent law. + + 12. No Surrender of Others' Freedom. + + If conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot convey a +covered work so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you may +not convey it at all. For example, if you agree to terms that obligate you +to collect a royalty for further conveying from those to whom you convey +the Program, the only way you could satisfy both those terms and this +License would be to refrain entirely from conveying the Program. + + 13. Use with the GNU Affero General Public License. + + Notwithstanding any other provision of this License, you have +permission to link or combine any covered work with a work licensed +under version 3 of the GNU Affero General Public License into a single +combined work, and to convey the resulting work. The terms of this +License will continue to apply to the part which is the covered work, +but the special requirements of the GNU Affero General Public License, +section 13, concerning interaction through a network will apply to the +combination as such. + + 14. Revised Versions of this License. + + The Free Software Foundation may publish revised and/or new versions of +the GNU General Public License from time to time. Such new versions will +be similar in spirit to the present version, but may differ in detail to +address new problems or concerns. + + Each version is given a distinguishing version number. If the +Program specifies that a certain numbered version of the GNU General +Public License "or any later version" applies to it, you have the +option of following the terms and conditions either of that numbered +version or of any later version published by the Free Software +Foundation. If the Program does not specify a version number of the +GNU General Public License, you may choose any version ever published +by the Free Software Foundation. + + If the Program specifies that a proxy can decide which future +versions of the GNU General Public License can be used, that proxy's +public statement of acceptance of a version permanently authorizes you +to choose that version for the Program. + + Later license versions may give you additional or different +permissions. However, no additional obligations are imposed on any +author or copyright holder as a result of your choosing to follow a +later version. + + 15. Disclaimer of Warranty. + + THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY +APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT +HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY +OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, +THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM +IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF +ALL NECESSARY SERVICING, REPAIR OR CORRECTION. + + 16. Limitation of Liability. + + IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS +THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY +GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE +USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF +DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD +PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), +EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF +SUCH DAMAGES. + + 17. Interpretation of Sections 15 and 16. + + If the disclaimer of warranty and limitation of liability provided +above cannot be given local legal effect according to their terms, +reviewing courts shall apply local law that most closely approximates +an absolute waiver of all civil liability in connection with the +Program, unless a warranty or assumption of liability accompanies a +copy of the Program in return for a fee. + + END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Programs + + If you develop a new program, and you want it to be of the greatest +possible use to the public, the best way to achieve this is to make it +free software which everyone can redistribute and change under these terms. + + To do so, attach the following notices to the program. It is safest +to attach them to the start of each source file to most effectively +state the exclusion of warranty; and each file should have at least +the "copyright" line and a pointer to where the full notice is found. + + + Copyright (C) + + This program is free software: you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation, either version 3 of the License, or + (at your option) any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this program. If not, see . + +Also add information on how to contact you by electronic and paper mail. + + If the program does terminal interaction, make it output a short +notice like this when it starts in an interactive mode: + + Copyright (C) + This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. + This is free software, and you are welcome to redistribute it + under certain conditions; type `show c' for details. + +The hypothetical commands `show w' and `show c' should show the appropriate +parts of the General Public License. Of course, your program's commands +might be different; for a GUI interface, you would use an "about box". + + You should also get your employer (if you work as a programmer) or school, +if any, to sign a "copyright disclaimer" for the program, if necessary. +For more information on this, and how to apply and follow the GNU GPL, see +. + + The GNU General Public License does not permit incorporating your program +into proprietary programs. If your program is a subroutine library, you +may consider it more useful to permit linking proprietary applications with +the library. If this is what you want to do, use the GNU Lesser General +Public License instead of this License. But first, please read +. + diff --git a/var/repos/builtin/recipes/eccc-casrriv/README.md b/var/repos/builtin/recipes/eccc-casrriv/README.md new file mode 100644 index 0000000..cf65495 --- /dev/null +++ b/var/repos/builtin/recipes/eccc-casrriv/README.md @@ -0,0 +1,79 @@ +# ECCC `RDRS` v2.1 +In this file, the details of the dataset is explained. + +## Location of Dataset Files +The `RDRS` v2.1 dataset is located under the following directory accessible from Compute Canada (CC) Graham Cluster: +```console +/project/rpp-kshook/Climate_Forcing_Data/meteorological-data/rdrsv2.1 # rpp-kshook allocation +/project/rrg-mclark/data/meteorological-data/rdrsv2.1 # rrg-mclark allocation +``` +and the structure of the dataset hourly files is as following: +```console +/project/rpp-kshook/Model_Output/RDRSv2.1 +├── 1980 +│ ├── 1980010112.nc +│ ├── 1980010212.nc +│ ├── 1980010312.nc +│ ├── . +│ ├── . +│ ├── . +│ └── 1980123112.nc +. +. +. +├── %Y +│ ├── %Y010112.nc +│ ├── . +│ ├── . +│ ├── %Y%m%d12.nc +│ ├── . +│ ├── . +│ └── %Y123112.nc +. +. +. +└── 2018 + ├── 2018010112.nc + ├── . + ├── . + ├── . + └── 2018123112.nc +``` + +## Coordinate Variables and Time-stamps + +### Coordinate Variables +The coordinate variables of the `ERA5` simulations are `lon` and `lat` representing the longitude and latitude points, respectively. +### Time-stamps +The time-stamps are included in the original files. + +## Dataset Variables +The NetCDF files of the dataset contain 28 variables. You may see a list of variables by using the `ncdump -h` command on one of the files: +```console +foo@bar:~$ module load cdo/2.0.4 +foo@bar:~$ module load nco/5.0.6 +foo@bar:~$ ncdump -h /project/rpp-kshook/Model_Output/RDRSv2.1/1980/1980010112.nc +``` + +## Spatial Extent +The spatial extent of the `RDRS` v2.1 is on latitutes from `+5.75` to `+64.75` and longitudes from `-179.9925` to `179.9728` covering North America. The resolution is 0.09 degrees (~10km). + +## Temporal Extent +The time-steps are hourly covering from `January 1980` to `December 2018`. + +## Short Description on `RDRS` v2.1 Variables +In most hydrological modelling applications, usually 7 variables are needed detailed as following: 1) specific humidity (@1.5-2.0m or @40m), 2) surface pressure, 3) air temperature (@1.5m-2.0m or 40m), 4) wind speed (@10m or @40m), 5) precipitation (surface level), 6) downward short wave radiation (surface level), and 7) downward long wave radiation (surface level). These variables are available through `RDRS` v2.1 dataset and their details are described in the table below: +|Variable Name |RDRSv2.1 Variable |Unit |IPCC abbreviation|Comments | +|----------------------|---------------------|-----|-----------------|----------------------| +|surface pressure |RDRS_v2.1_P_P0_SFC |mb |ps | | +|specific humidity@1.5m|RDRS_v2.1_P_HU_1.5m |1 |huss | | +|air tempreature @1.5m |RDRS_v2.1_P_TT_1.5m |°C |tas | | +|wind speed @10m |RDRS_v2.1_P_UVC_10m |kts |wspd |WIND=SQRT(U102+V102)| +|precipitation |RDRS_v2.1_A_PR0_SFC |m/hr | |CaPA outputs | +|short wave radiation |RDRS_v2.1_P_FB_SFC |W m-2|rsds |Downward solar flux | +|long wave radiation |RDRS_v2.1_P_FI_SFC |W m-2|rlds |Downward infrared flux| +|specific humidity @40m|RDRS_v2.1_P_HU_09944 |1 |huss | | +|air temperature @40m |RDRS_v2.1_P_TT_09944 |°C |tas | | +|wind speed @40m |RDRS_v2.1_P_UVC_09944|kts |wspd | | + +Please visit the [official website](https://github.com/julemai/CaSPAr/wiki/Available-products) for the dataset for the most up-to-date information. diff --git a/var/repos/builtin/recipes/eccc-casrriv/cassriv.sh b/var/repos/builtin/recipes/eccc-casrriv/cassriv.sh new file mode 100755 index 0000000..8d19ccf --- /dev/null +++ b/var/repos/builtin/recipes/eccc-casrriv/cassriv.sh @@ -0,0 +1,316 @@ +#!/bin/bash +# Meteorological Data Processing Workflow +# Copyright (C) 2022-2023, University of Saskatchewan +# Copyright (C) 2023-2024, University of Calgary +# +# This file is part of Meteorological Data Processing Workflow +# +# This program is free software: you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation, either version 3 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, see . + +# ========================= +# Credits and contributions +# ========================= +# 1. Parts of the code are taken from +# https://www.shellscript.sh/tips/getopt/index.html + + +# ================ +# General comments +# ================ +# * All variables are camelCased for distinguishing from function names; +# * function names are all in lower_case with words seperated by underscore for legibility; +# * shell style is based on Google Open Source Projects' +# Style Guide: https://google.github.io/styleguide/shellguide.html + + +# =============== +# Usage functions +# =============== +short_usage() { + echo "usage: $(basename $0) [-cio DIR] [-v VARS] [-se DATE] [-t CHAR] [-ln REAL,REAL] [-p STR]" +} + + +# argument parsing using getopt - WORKS ONLY ON LINUX BY DEFAULT +parsedArguments=$(getopt -a -n casrriv -o i:v:o:s:e:t:l:n:p:c:m:S:M: --long dataset-dir:,variable:,output-dir:,start-date:,end-date:,time-scale:,lat-lims:,lon-lims:,prefix:,cache:,ensemble:,scenario:,model: -- "$@") +validArguments=$? +if [ "$validArguments" != "0" ]; then + short_usage; + exit 1; +fi + +# check if no options were passed +if [ $# -eq 0 ]; then + echo "ERROR $(basename $0): arguments missing"; + exit 1; +fi + +# check long and short options passed +eval set -- "$parsedArguments" +while : +do + case "$1" in + -i | --dataset-dir) datasetDir="$2" ; shift 2 ;; # required + -v | --variable) variables="$2" ; shift 2 ;; # required + -o | --output-dir) outputDir="$2" ; shift 2 ;; # required + -s | --start-date) startDate="$2" ; shift 2 ;; # required + -e | --end-date) endDate="$2" ; shift 2 ;; # required + -t | --time-scale) timeScale="$2" ; shift 2 ;; # redundant - added for compatibility + -l | --lat-lims) latLims="$2" ; shift 2 ;; # required + -n | --lon-lims) lonLims="$2" ; shift 2 ;; # required + -p | --prefix) prefix="$2" ; shift 2 ;; # optional + -c | --cache) cache="$2" ; shift 2 ;; # required + -m | --ensemble) ensemble="$2" ; shift 2 ;; # redundant - added for compatibility + -S | --scenario) scenario="$2" ; shift 2 ;; # redundant - added for compatibility + -M | --model) model="$2" ; shift 2 ;; # redundant - added for compatibility + + # -- means the end of the arguments; drop this, and break out of the while loop + --) shift; break ;; + + # in case of invalid option + *) + echo "ERROR $(basename $0): invalid option '$1'"; + short_usage; exit 1 ;; + esac +done + +# useful log date format function +logDate () { echo "($(date +"%Y-%m-%d %H:%M:%S")) "; } + +# check if $ensemble is provided +if [[ -n "$ensemble" ]] || \ + [[ -n "$scenario" ]] || \ + [[ -n "$model" ]]; then + echo "$(logDate)$(basename $0): ERROR! redundant argument provided"; + exit 1; +fi + +# check the prefix of not set +if [[ -z $prefix ]]; then + prefix="data_" +fi + + +# ===================== +# Necessary assumptions +# ===================== +# TZ to be set to UTC to avoid invalid dates due to Daylight Saving +alias date='TZ=UTC date' + +# expand aliases for the one stated above +shopt -s expand_aliases + +# paths +datatoolPath="$(dirname $0)/../../../../../" # datatool's path +# daymet index scripts works on RDRSv2.1 grids as well +# and ESPO-G6-R2 has similar grid system as RDRSv2.1 +coordIdxScript="$datatoolPath/etc/scripts/coord_daymet_idx.ncl" +coordClosestIdxScript="$datatoolPath/etc/scripts/coord_closest_daymet_idx.ncl" + + +# ========================== +# Necessary global variables +# ========================== +# the structure of file names is as follows: "YYYYMMDD12.nc" +rdrsFormat="%Y%m%d" # rdrs file date format +exportFormat="%Y%m%d" # exported file date format +fileStruct="" # source dataset files' prefix constant + +latDim="rlat" +lonDim="rlon" + + +# ================= +# Useful one-liners +# ================= +#calcualte Unix EPOCH time in seconds from 1970-01-01 00:00:00 +unix_epoch () { date --date="$@" +"%s"; } + +#check whether the input is float or real +check_real () { if [[ "$1" == *'.'* ]]; then echo 'float'; else echo 'int'; fi; } + +#convert to float if the number is 'int' +to_float () { if [[ $(check_real $1) == 'int' ]]; then printf "%.1f" "$1"; echo; else printf "%.5f" "$1"; echo; fi; } + +#join array element by the specified delimiter +join_by () { local IFS="$1"; shift; echo "$*"; } + +#to_float the latLims and lonLims, real numbers delimited by ',' +lims_to_float () { IFS=',' read -ra l <<< $@; f_arr=(); for i in "${l[@]}"; do f_arr+=($(to_float $i)); done; echo $(join_by , "${f_arr[@]}"); } + + +# =============== +# Data processing +# =============== +# display info +echo "$(logDate)$(basename $0): processing ECCC CASR Rivers v2.1..." + +# make the output directory +echo "$(logDate)$(basename $0): creating output directory under $outputDir" +mkdir -p "$outputDir" +echo "$(logDate)$(basename $0): creating cache directory under $cache" +mkdir -p "$cache" + + +# ====================== +# Extract domain extents +# ====================== + +# parse the upper and lower bounds of a given spatial limit +minLat=$(echo $latLims | cut -d ',' -f 1) +maxLat=$(echo $latLims | cut -d ',' -f 2) +minLon=$(echo $lonLims | cut -d ',' -f 1) +maxLon=$(echo $lonLims | cut -d ',' -f 2) + +# choose a sample file as all files share the same grid +domainFile="$(find "${datasetDir}/" -type f -name "*.nc" | head -n 1)" + +# parse the upper and lower bounds of a given spatial limit +minLat=$(echo $latLims | cut -d ',' -f 1) +maxLat=$(echo $latLims | cut -d ',' -f 2) +minLon=$(echo $lonLims | cut -d ',' -f 1) +maxLon=$(echo $lonLims | cut -d ',' -f 2) + +# adding/subtracting 0.1 degree to/from max/min values +minLat=$(bc <<< "$minLat - 0.1") +maxLat=$(bc <<< "$maxLat + 0.1") +minLon=$(bc <<< "$minLon - 0.1") +maxLon=$(bc <<< "$maxLon + 0.1") + +# updating $latLims and $lonLims based on new values +latLims="${minLat},${maxLat}" +lonLims="${minLon},${maxLon}" + +# extract the associated indices corresponding to $latLims and $lonLims +coordIdx="$(ncl -nQ 'coord_file='\"$domainFile\" 'minlat='"$minLat" 'maxlat='"$maxLat" 'minlon='"$minLon" 'maxlon='"$maxLon" "$coordIdxScript")" + +# if spatial index out-of-bound, i.e., 'ERROR' is return +if [[ "${coordIdx}" == "ERROR" ]]; then + # extract the closest index values + coordIdx="$(ncl -nQ 'coord_file='\"$domainFile\" 'minlat='"$minLat" 'maxlat='"$maxLat" 'minlon='"$minLon" 'maxlon='"$maxLon" "$coordClosestIdxScript")" +fi + +# parse the output index for latitude and longitude +lonLimsIdx+="$(echo $coordIdx | cut -d ' ' -f 1)" +latLimsIdx+="$(echo $coordIdx | cut -d ' ' -f 2)" + + +# ===================== +# Extract dataset files +# ===================== +# define necessary dates +# Assure the end-date is not beyond 2018-12-30 +endDateInt=$(date --date="$endDate" +"%Y%m%d") +if [[ $endDateInt -gt "20181230" ]]; then + endDate="2018-12-30T23:00:00" +fi +# Assure the start-date is not before 1980-01-01 +startDateInt=$(date --date="$startDate" +"%Y%m%d") +if [[ $startDateInt -lt "19800101" ]]; then + startDate="1980-01-01T12:00:00" +fi + +# assign proper variables for dates +startYear=$(date --date="$startDate" +"%Y") # start year (first folder) +endYear=$(date --date="$endDate" +"%Y") # end year (last folder) +yearsRange=$(seq $startYear $endYear) + +toDate="$startDate" +toDateUnix="$(unix_epoch "$toDate")" +endDateUnix="$(unix_epoch "$endDate")" + +# iterate over the years +for yr in $yearsRange; do + # creating yearly directory + mkdir -p "$outputDir/$yr" # output directory + mkdir -p "$cache/$yr" # cache directory + + # setting the end point, either the end of current year, or the $endDate + # last time-step of the current year + endOfCurrentYearUnix=$(date --date="$yr-01-01 23:00:00 +1year -1day" "+%s") + if [[ $endOfCurrentYearUnix -le $endDateUnix ]]; then + endPointUnix=$endOfCurrentYearUnix + else + endPointUnix=$endDateUnix + fi + + # extract variables from the forcing data files + while [[ "$toDateUnix" -le "$endPointUnix" ]]; do + # date manipulations + # current timestamp formatted to conform to RDRS naming convention + toDateFormatted=$(date --date "$toDate" +"$rdrsFormat") + + # creating file name + file="${toDateFormatted}12.nc" # current file name + + # extracting spatial extents and variables + until cdo -z zip \ + -s -L \ + -sellonlatbox,"$lonLims","$latLims" \ + -selvar,"$variables" \ + "${datasetDir}/${yr}/${file}" \ + "${cache}/${yr}/${file}"; do + echo "$(logDate)$(basename $0): Process killed: restarting process in 10 sec" >&2 + echo "CDO [...] failed" >&2 + sleep 10; + done # until ncks + + # remove any left-over .tmp file + if [[ -e ${cache}/${yr}/${file}*.tmp ]]; then + rm -r "${cache}/${yr}/${file}*.tmp" + fi + + # wait for any left-over processes to finish + # note to self: not sure this even does anything, but anyways + wait + + # change lon values so the extents are from ~-180 to 0 + # assuring the process finished using an `until` loop + until ncap2 -O -s 'where(lon>0) lon=lon-360' \ + "${cache}/${yr}/${file}" \ + "${outputDir}/${yr}/${prefix}${file}"; do + rm "${outputDir}/${yr}/${prefix}${file}" + echo "$(logDate)$(basename $0): Process killed: restarting process in 10 sec" >&2 + echo "$(logDate)$(basename $0): NCAP2 -s [...] failed" >&2 + sleep 10; + done + + # remove any left-over .tmp file + if [[ -e ${cache}/${yr}/${file}*.tmp ]]; then + rm -r "${cache}/${yr}/${file}*.tmp" + fi + + # wait for any left-over processes to finish + # note to self: not sure this even does anything, but anyways + wait + + # increment time-step by one unit + toDate="$(date --date "$toDate 1day")" # current time-step + toDateUnix="$(unix_epoch "$toDate")" # current timestamp in unix EPOCH time + done + + # go to the next year if necessary + if [[ "$toDateUnix" == "$endOfCurrentYearUnix" ]]; then + toDate=$(date --date "$toDate 1day") + fi + +done + +mkdir -p "$HOME/empty_dir" +echo "$(logDate)$(basename $0): deleting temporary files from $cache" +rsync -aP --delete "$HOME/empty_dir/" "$cache" +rm -r "$cache" +echo "$(logDate)$(basename $0): temporary files from $cache are removed" +echo "$(logDate)$(basename $0): results are produced under $outputDir" + From 2e2138b1138da32156dd18eb03380ef471e43b83 Mon Sep 17 00:00:00 2001 From: Joel Trubilowicz Date: Tue, 21 Oct 2025 19:32:58 +0000 Subject: [PATCH 4/5] working version of casr rivers v21 --- examples/Casr_land_example.sh | 45 +++++ examples/Casr_riv_example.sh | 45 +++++ examples/Casrv3p1_example.sh | 2 +- extract-dataset.sh | 6 +- .../eccc-casrriv/{cassriv.sh => casrriv.sh} | 166 ++++++++++-------- 5 files changed, 190 insertions(+), 74 deletions(-) create mode 100755 examples/Casr_land_example.sh create mode 100755 examples/Casr_riv_example.sh rename var/repos/builtin/recipes/eccc-casrriv/{cassriv.sh => casrriv.sh} (70%) diff --git a/examples/Casr_land_example.sh b/examples/Casr_land_example.sh new file mode 100755 index 0000000..f77f3e3 --- /dev/null +++ b/examples/Casr_land_example.sh @@ -0,0 +1,45 @@ +#!/bin/bash + +# Meteorological Data Processing Workflow +# Copyright (C) 2022, University of Saskatchewan +# +# This file is part of Meteorological Data Processing Workflow +# +# This program is free software: you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation, either version 3 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, see . + +# This is a simple example to extract ECCC Casr Land (2.1) data for the +# South Saskatchewan River Basin (SSRB) approximate extents +# from Jan 2015 to Dec 2017. + +# As is mentioned on the main webpage of the repository, it is +# recommended to submit annual jobs for this dataset. + +# This example is meant to be called from the home directory, as is required by GC Science PBS job submission +cd datatool +echo "The current directory is: $(pwd)" + +# chunking done on an 'annual' basis +./extract-dataset.sh --dataset="casr" \ + --dataset-dir="/home/gol000/store6/reanalysis/post_processing/casr_land_v2p1_masking/outdir/outnetcdf_all" \ + --output-dir="$HOME/scratch/casr_land/" \ + --start-date="2015-01-01" \ + --end-date="2017-12-30" \ + --lat-lims=49,54 \ + --lon-lims=-120,-98 \ + --variable="CaSR_Land_v2.1_TRAF_Aggregated,CaSR_Land_v2.1_SWE_Land" \ + --prefix="casrland_21_" \ + --cluster="./etc/clusters/eccc-science.json" \ + --email="joel.trubilowicz@ec.gc.ca" \ + -j; + diff --git a/examples/Casr_riv_example.sh b/examples/Casr_riv_example.sh new file mode 100755 index 0000000..7527c26 --- /dev/null +++ b/examples/Casr_riv_example.sh @@ -0,0 +1,45 @@ +#!/bin/bash + +# Meteorological Data Processing Workflow +# Copyright (C) 2022, University of Saskatchewan +# +# This file is part of Meteorological Data Processing Workflow +# +# This program is free software: you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation, either version 3 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, see . + +# This is a simple example to extract ECCC Casr Rivers (2.1) data near the +# South Sask River Gauge (WSC 05HG001) +# from Jan 2015 to Dec 2017. + +# As is mentioned on the main webpage of the repository, it is +# recommended to submit annual jobs for this dataset. + +# This example is meant to be called from the home directory, as is required by GC Science PBS job submission +cd datatool +echo "The current directory is: $(pwd)" + +# chunking done on an 'annual' basis +./extract-dataset.sh --dataset="casrriv" \ + --dataset-dir="/home/shyd500/data/ppp6/casr_rivers_v2p1_postproc/full_domain/" \ + --output-dir="$HOME/scratch/casr_riv/" \ + --start-date="2015-01-01" \ + --end-date="2017-12-30" \ + --lat-lims=52,52.5 \ + --lon-lims=-107,-106.5 \ + --variable="disc" \ + --prefix="casrriv_21_" \ + --cluster="./etc/clusters/eccc-science.json" \ + --email="joel.trubilowicz@ec.gc.ca" \ + -j; + diff --git a/examples/Casrv3p1_example.sh b/examples/Casrv3p1_example.sh index 7356922..50b5814 100755 --- a/examples/Casrv3p1_example.sh +++ b/examples/Casrv3p1_example.sh @@ -33,7 +33,7 @@ echo "The current directory is: $(pwd)" ./extract-dataset.sh --dataset="casr" \ --dataset-dir="/home/scar700/data/ppp6/CaSRv3.1/postproc_casr4caspar_20250416/link2out4pilot_netcdf/" \ --output-dir="$HOME/scratch/casr31_output/" \ - --start-date="2015-01-01" \ + --start-date="2018-01-01" \ --end-date="2018-12-30" \ --lat-lims=49,54 \ --lon-lims=-120,-98 \ diff --git a/extract-dataset.sh b/extract-dataset.sh index f2558e5..38e5fce 100755 --- a/extract-dataset.sh +++ b/extract-dataset.sh @@ -773,11 +773,15 @@ case "${dataset,,}" in call_processing_func "$recipePath/eccc-rdrs/rdrs.sh" "6months" ;; - # ECCC RDRS + # ECCC CaSR "casr" | "casrv3.1") call_processing_func "$recipePath/eccc-casr/casr.sh" "3months" ;; + # ECCC Casr Rivers + "casrriv" | "casr_riv_v2.1") + call_processing_func "$recipePath/eccc-casrriv/casrriv.sh" "3months" + ;; # ==================== # Observation datasets # ==================== diff --git a/var/repos/builtin/recipes/eccc-casrriv/cassriv.sh b/var/repos/builtin/recipes/eccc-casrriv/casrriv.sh similarity index 70% rename from var/repos/builtin/recipes/eccc-casrriv/cassriv.sh rename to var/repos/builtin/recipes/eccc-casrriv/casrriv.sh index 8d19ccf..8b63b33 100755 --- a/var/repos/builtin/recipes/eccc-casrriv/cassriv.sh +++ b/var/repos/builtin/recipes/eccc-casrriv/casrriv.sh @@ -125,7 +125,7 @@ coordClosestIdxScript="$datatoolPath/etc/scripts/coord_closest_daymet_idx.ncl" # the structure of file names is as follows: "YYYYMMDD12.nc" rdrsFormat="%Y%m%d" # rdrs file date format exportFormat="%Y%m%d" # exported file date format -fileStruct="" # source dataset files' prefix constant +fileStruct="_MSC_CaSR-Rivers-Analysis_RiverDischarge_Sfc_LatLon0.00833_PT0H" # source dataset files' suffix constant latDim="rlat" lonDim="rlon" @@ -193,12 +193,12 @@ latLims="${minLat},${maxLat}" lonLims="${minLon},${maxLon}" # extract the associated indices corresponding to $latLims and $lonLims -coordIdx="$(ncl -nQ 'coord_file='\"$domainFile\" 'minlat='"$minLat" 'maxlat='"$maxLat" 'minlon='"$minLon" 'maxlon='"$maxLon" "$coordIdxScript")" +coordIdx="$(singularity exec $NCL_SINGULARITY_IMAGE ncl -nQ 'coord_file='\"$domainFile\" 'minlat='"$minLat" 'maxlat='"$maxLat" 'minlon='"$minLon" 'maxlon='"$maxLon" "$coordIdxScript")" # if spatial index out-of-bound, i.e., 'ERROR' is return if [[ "${coordIdx}" == "ERROR" ]]; then # extract the closest index values - coordIdx="$(ncl -nQ 'coord_file='\"$domainFile\" 'minlat='"$minLat" 'maxlat='"$maxLat" 'minlon='"$minLon" 'maxlon='"$maxLon" "$coordClosestIdxScript")" + coordIdx="$(singularity exec $NCL_SINGULARITY_IMAGE ncl -nQ 'coord_file='\"$domainFile\" 'minlat='"$minLat" 'maxlat='"$maxLat" 'minlon='"$minLon" 'maxlon='"$maxLon" "$coordClosestIdxScript")" fi # parse the output index for latitude and longitude @@ -223,7 +223,9 @@ fi # assign proper variables for dates startYear=$(date --date="$startDate" +"%Y") # start year (first folder) +startMonth=$(date --date="$startDate" +"%m") # start month (first folder) endYear=$(date --date="$endDate" +"%Y") # end year (last folder) +endMonth=$(date --date="$endDate" +"%m") # end month (last folder) yearsRange=$(seq $startYear $endYear) toDate="$startDate" @@ -232,79 +234,99 @@ endDateUnix="$(unix_epoch "$endDate")" # iterate over the years for yr in $yearsRange; do - # creating yearly directory - mkdir -p "$outputDir/$yr" # output directory - mkdir -p "$cache/$yr" # cache directory - - # setting the end point, either the end of current year, or the $endDate - # last time-step of the current year - endOfCurrentYearUnix=$(date --date="$yr-01-01 23:00:00 +1year -1day" "+%s") - if [[ $endOfCurrentYearUnix -le $endDateUnix ]]; then - endPointUnix=$endOfCurrentYearUnix - else - endPointUnix=$endDateUnix - fi - - # extract variables from the forcing data files - while [[ "$toDateUnix" -le "$endPointUnix" ]]; do - # date manipulations - # current timestamp formatted to conform to RDRS naming convention - toDateFormatted=$(date --date "$toDate" +"$rdrsFormat") - - # creating file name - file="${toDateFormatted}12.nc" # current file name - - # extracting spatial extents and variables - until cdo -z zip \ - -s -L \ - -sellonlatbox,"$lonLims","$latLims" \ - -selvar,"$variables" \ - "${datasetDir}/${yr}/${file}" \ - "${cache}/${yr}/${file}"; do - echo "$(logDate)$(basename $0): Process killed: restarting process in 10 sec" >&2 - echo "CDO [...] failed" >&2 - sleep 10; - done # until ncks - - # remove any left-over .tmp file - if [[ -e ${cache}/${yr}/${file}*.tmp ]]; then - rm -r "${cache}/${yr}/${file}*.tmp" - fi + + seqstart=1 + seqend=12 - # wait for any left-over processes to finish - # note to self: not sure this even does anything, but anyways - wait - - # change lon values so the extents are from ~-180 to 0 - # assuring the process finished using an `until` loop - until ncap2 -O -s 'where(lon>0) lon=lon-360' \ - "${cache}/${yr}/${file}" \ - "${outputDir}/${yr}/${prefix}${file}"; do - rm "${outputDir}/${yr}/${prefix}${file}" - echo "$(logDate)$(basename $0): Process killed: restarting process in 10 sec" >&2 - echo "$(logDate)$(basename $0): NCAP2 -s [...] failed" >&2 - sleep 10; - done - - # remove any left-over .tmp file - if [[ -e ${cache}/${yr}/${file}*.tmp ]]; then - rm -r "${cache}/${yr}/${file}*.tmp" + if [[ $yr == $startYear ]]; then + seqstart=$startMonth fi - # wait for any left-over processes to finish - # note to self: not sure this even does anything, but anyways - wait - - # increment time-step by one unit - toDate="$(date --date "$toDate 1day")" # current time-step - toDateUnix="$(unix_epoch "$toDate")" # current timestamp in unix EPOCH time - done - - # go to the next year if necessary - if [[ "$toDateUnix" == "$endOfCurrentYearUnix" ]]; then - toDate=$(date --date "$toDate 1day") - fi + + if [[ $yr == $endYear ]]; then + seqend=$endMonth + fi + monthseq=$(seq -w $seqstart $seqend) + + + for month in $monthseq; do + + ym=$yr$month + + # creating yearly directory + #mkdir -p "$outputDir/$ym" # output directory + mkdir -p "$cache/$ym" # cache directory + + # setting the end point, either the end of current year/mont, or the $endDate + # last time-step of the current year/mont + endOfCurrentYMonthUnix=$(date --date="$yr-$month-01 23:00:00 +1month -1day" "+%s") + if [[ $endOfCurrentYMonthUnix -le $endDateUnix ]]; then + endPointUnix=$endOfCurrentYMonthUnix + else + endPointUnix=$endDateUnix + fi + + # extract variables from the forcing data files + while [[ "$toDateUnix" -le "$endPointUnix" ]]; do + # date manipulations + # current timestamp formatted to conform to RDRS naming convention + toDateFormatted=$(date --date "$toDate" +"$rdrsFormat") + + # creating file name + file="${toDateFormatted}${fileStruct}.nc" # current file name + + # extracting spatial extents and variables + until cdo -z zip \ + -s -L \ + -sellonlatbox,"$lonLims","$latLims" \ + -selvar,"$variables" \ + "${datasetDir}/${ym}/${file}" \ + "${cache}/${ym}/${file}"; do + echo "$(logDate)$(basename $0): Process killed: restarting process in 10 sec" >&2 + echo "CDO [...] failed" >&2 + sleep 10; + done # until ncks + + # remove any left-over .tmp file + if [[ -e ${cache}/${ym}/${file}*.tmp ]]; then + rm -r "${cache}/${ym}/${file}*.tmp" + fi + + # wait for any left-over processes to finish + # note to self: not sure this even does anything, but anyways + wait + + # change lon values so the extents are from ~-180 to 0 + # assuring the process finished using an `until` loop + until ncap2 -O -s 'where(lon>0) lon=lon-360' \ + "${cache}/${ym}/${file}" \ + "${outputDir}/${prefix}${file}"; do + rm "${outputDir}/${prefix}${file}" + echo "$(logDate)$(basename $0): Process killed: restarting process in 10 sec" >&2 + echo "$(logDate)$(basename $0): NCAP2 -s [...] failed" >&2 + sleep 10; + done + + # remove any left-over .tmp file + if [[ -e ${cache}/${ym}/${file}*.tmp ]]; then + rm -r "${cache}/${ym}/${file}*.tmp" + fi + + # wait for any left-over processes to finish + # note to self: not sure this even does anything, but anyways + wait + + # increment time-step by one unit + toDate="$(date --date "$toDate 1day")" # current time-step + toDateUnix="$(unix_epoch "$toDate")" # current timestamp in unix EPOCH time + done + + # go to the next year if necessary + if [[ "$toDateUnix" == "$endOfCurrentYMonthUnix" ]]; then + toDate=$(date --date "$toDate 1day") + fi + done done mkdir -p "$HOME/empty_dir" From 649d37a5cfead7e6259885849baf2b09886f21a4 Mon Sep 17 00:00:00 2001 From: Joel Trubilowicz Date: Thu, 23 Oct 2025 13:57:57 -0600 Subject: [PATCH 5/5] Update Casr-Rivers recipe readme --- .../builtin/recipes/eccc-casrriv/README.md | 68 ++++++++----------- 1 file changed, 29 insertions(+), 39 deletions(-) diff --git a/var/repos/builtin/recipes/eccc-casrriv/README.md b/var/repos/builtin/recipes/eccc-casrriv/README.md index cf65495..675d0ef 100644 --- a/var/repos/builtin/recipes/eccc-casrriv/README.md +++ b/var/repos/builtin/recipes/eccc-casrriv/README.md @@ -1,79 +1,69 @@ -# ECCC `RDRS` v2.1 +# ECCC `CaSR-Rivers` v2.1 In this file, the details of the dataset is explained. ## Location of Dataset Files -The `RDRS` v2.1 dataset is located under the following directory accessible from Compute Canada (CC) Graham Cluster: +The `CaSR-Rivers` v2.1 dataset is located under the following directory accessible from GC Science ```console -/project/rpp-kshook/Climate_Forcing_Data/meteorological-data/rdrsv2.1 # rpp-kshook allocation -/project/rrg-mclark/data/meteorological-data/rdrsv2.1 # rrg-mclark allocation + /home/shyd500/data/ppp6/casr_rivers_v2p1_postproc/full_domain ``` -and the structure of the dataset hourly files is as following: +and the structure of the single-day hourly timestep data files is as follows: ```console -/project/rpp-kshook/Model_Output/RDRSv2.1 -├── 1980 -│ ├── 1980010112.nc -│ ├── 1980010212.nc -│ ├── 1980010312.nc + /home/shyd500/data/ppp6/casr_rivers_v2p1_postproc/full_domain + +├── 198001 +│ ├── 19800101_MSC_CaSR-Rivers-Analysis_RiverDischarge_Sfc_LatLon0.00833_PT0H.nc +│ ├── 19800102_MSC_CaSR-Rivers-Analysis_RiverDischarge_Sfc_LatLon0.00833_PT0H.nc +│ ├── 19800103_MSC_CaSR-Rivers-Analysis_RiverDischarge_Sfc_LatLon0.00833_PT0H.nc │ ├── . │ ├── . │ ├── . -│ └── 1980123112.nc +│ └── 19800131_MSC_CaSR-Rivers-Analysis_RiverDischarge_Sfc_LatLon0.00833_PT0H.nc . . . -├── %Y -│ ├── %Y010112.nc +├── %Y%m +│ ├── %Y0101_MSC_CaSR-Rivers-Analysis_RiverDischarge_Sfc_LatLon0.00833_PT0H.nc │ ├── . │ ├── . -│ ├── %Y%m%d12.nc +│ ├── %Y%m%d_MSC_CaSR-Rivers-Analysis_RiverDischarge_Sfc_LatLon0.00833_PT0H.nc │ ├── . │ ├── . -│ └── %Y123112.nc +│ └── %Y1231_MSC_CaSR-Rivers-Analysis_RiverDischarge_Sfc_LatLon0.00833_PT0H.nc . . . -└── 2018 - ├── 2018010112.nc +└── 201712 + ├── 20171201_MSC_CaSR-Rivers-Analysis_RiverDischarge_Sfc_LatLon0.00833_PT0H.nc ├── . ├── . ├── . - └── 2018123112.nc + └── 20171231_MSC_CaSR-Rivers-Analysis_RiverDischarge_Sfc_LatLon0.00833_PT0H.nc ``` ## Coordinate Variables and Time-stamps ### Coordinate Variables -The coordinate variables of the `ERA5` simulations are `lon` and `lat` representing the longitude and latitude points, respectively. +The coordinate variables of the `CaSR-Rivers` simulations are `lon` and `lat` representing the longitude and latitude points, respectively. ### Time-stamps The time-stamps are included in the original files. ## Dataset Variables -The NetCDF files of the dataset contain 28 variables. You may see a list of variables by using the `ncdump -h` command on one of the files: +The NetCDF files of the dataset contain only 1 variables (`disc`). You may see a list of variables by using the `ncdump -h` command on one of the files: ```console -foo@bar:~$ module load cdo/2.0.4 -foo@bar:~$ module load nco/5.0.6 -foo@bar:~$ ncdump -h /project/rpp-kshook/Model_Output/RDRSv2.1/1980/1980010112.nc +foo@bar:~$ ncdump -h /home/shyd500/data/ppp6/casr_rivers_v2p1_postproc/full_domain/201712/20171231_MSC_CaSR-Rivers-Analysis_RiverDischarge_Sfc_LatLon0.00833_PT0H.nc ``` ## Spatial Extent -The spatial extent of the `RDRS` v2.1 is on latitutes from `+5.75` to `+64.75` and longitudes from `-179.9925` to `179.9728` covering North America. The resolution is 0.09 degrees (~10km). +The spatial extent of the `CaSR-Rivers` v2.1 is ~1km ## Temporal Extent -The time-steps are hourly covering from `January 1980` to `December 2018`. +The time-steps are hourly covering from `January 1980` to `December 2017`. -## Short Description on `RDRS` v2.1 Variables +## Short Description on `CaSR-Rivers` v2.1 Variables In most hydrological modelling applications, usually 7 variables are needed detailed as following: 1) specific humidity (@1.5-2.0m or @40m), 2) surface pressure, 3) air temperature (@1.5m-2.0m or 40m), 4) wind speed (@10m or @40m), 5) precipitation (surface level), 6) downward short wave radiation (surface level), and 7) downward long wave radiation (surface level). These variables are available through `RDRS` v2.1 dataset and their details are described in the table below: -|Variable Name |RDRSv2.1 Variable |Unit |IPCC abbreviation|Comments | -|----------------------|---------------------|-----|-----------------|----------------------| -|surface pressure |RDRS_v2.1_P_P0_SFC |mb |ps | | -|specific humidity@1.5m|RDRS_v2.1_P_HU_1.5m |1 |huss | | -|air tempreature @1.5m |RDRS_v2.1_P_TT_1.5m |°C |tas | | -|wind speed @10m |RDRS_v2.1_P_UVC_10m |kts |wspd |WIND=SQRT(U102+V102)| -|precipitation |RDRS_v2.1_A_PR0_SFC |m/hr | |CaPA outputs | -|short wave radiation |RDRS_v2.1_P_FB_SFC |W m-2|rsds |Downward solar flux | -|long wave radiation |RDRS_v2.1_P_FI_SFC |W m-2|rlds |Downward infrared flux| -|specific humidity @40m|RDRS_v2.1_P_HU_09944 |1 |huss | | -|air temperature @40m |RDRS_v2.1_P_TT_09944 |°C |tas | | -|wind speed @40m |RDRS_v2.1_P_UVC_09944|kts |wspd | | +|Variable Name |CaSR-Rivers Varname |Unit |Long Name | +|----------------------|---------------------|-------|--------------------------------------------------------------------------------------------| +|Streamflow Discharge |disc |$m^3/s$|Mean discharge value exiting the river channel over the hour ending at the indicated time | + -Please visit the [official website](https://github.com/julemai/CaSPAr/wiki/Available-products) for the dataset for the most up-to-date information. +Please visit the [official website](https://goc-dx.science.gc.ca/~arg000/casr-webpages/casr_subpage_index.html) for the dataset for the most up-to-date information.