filetools¶
This module provides features for handling the folder structure of HydPy projects as well as loading data from and storing data to files.
Module filetools
implements the following members:
Folder2Path
Map folder names to their path names.
FileManager
Base class forNetworkManager
,ControlManager
,ConditionManager
, andSequenceManager
.
NetworkManager
Manager for network files.
ControlManager
Manager for control parameter files.
ConditionManager
Manager for condition files.
SequenceManager
Manager for sequence files.
-
class
hydpy.core.filetools.
Folder2Path
(*args, **kwargs)[source]¶ Bases:
object
Map folder names to their path names.
You can both pass positional arguments and keyword arguments when initialising
Folder2Path
. For positional arguments, the folder and its path are assumed to be identical. For keyword arguments, the keyword corresponds to the folder name and its value to the path name:>>> from hydpy.core.filetools import Folder2Path >>> Folder2Path() Folder2Path() >>> f2p = Folder2Path( ... "folder1", "folder2", folder3="folder3", folder4="path4") >>> f2p Folder2Path(folder1, folder2, folder3, folder4=path4) >>> print(f2p) Folder2Path(folder1, folder2, folder3, folder4=path4)
To add folders after initialisation is supported:
>>> f2p.add("folder5") >>> f2p.add("folder6", "path6") >>> f2p Folder2Path(folder1, folder2, folder3, folder5, folder4=path4, folder6=path6)
Folder names are required to be valid Python identifiers:
>>> f2p.add("folder 7") Traceback (most recent call last): ... ValueError: The given name string `folder 7` does not define a valid variable identifier. Valid identifiers do not contain characters like `-` or empty spaces, do not start with numbers, cannot be mistaken with Python built-ins like `for`...)
You can query the folder and attribute names:
>>> f2p.folders ['folder1', 'folder2', 'folder3', 'folder4', 'folder5', 'folder6'] >>> f2p.paths ['folder1', 'folder2', 'folder3', 'path4', 'folder5', 'path6']
Attribute access and iteration are also supported:
>>> "folder1" in dir(f2p) True >>> f2p.folder1 'folder1' >>> f2p.folder4 'path4'
>>> for folder, path in f2p: ... print(folder, path) folder1 folder1 folder2 folder2 folder3 folder3 folder4 path4 folder5 folder5 folder6 path6
>>> len(f2p) 6 >>> bool(f2p) True >>> bool(Folder2Path()) False
-
add
(directory: str, path: Optional[str] = None) → None[source]¶ Add a directory and optionally its path.
-
property
folders
¶ The currently handled folder names.
-
property
paths
¶ The currently handled path names.
-
-
class
hydpy.core.filetools.
FileManager
[source]¶ Bases:
object
Base class for
NetworkManager
,ControlManager
,ConditionManager
, andSequenceManager
.-
projectdir
¶ The name of the main folder of a project.
For the LahnH example project,
projectdir
is (not surprisingly) LahnH, and is queried from thepub
module. However, you can define or changeprojectdir
interactively, which can be useful for more complex tasks like copying (parts of) projects:>>> from hydpy.core.filetools import FileManager >>> from hydpy import pub >>> pub.projectname = "project_A" >>> filemanager = FileManager() >>> filemanager.projectdir 'project_A'
>>> del filemanager.projectdir >>> filemanager.projectdir Traceback (most recent call last): ... hydpy.core.exceptiontools.AttributeNotReady: Attribute `projectdir` of object `filemanager` has not been prepared so far. >>> filemanager.projectdir = "project_B" >>> filemanager.projectdir 'project_B'
>>> del pub.projectname >>> FileManager().projectdir Traceback (most recent call last): ... hydpy.core.exceptiontools.AttributeNotReady: Attribute `projectdir` of object `filemanager` has not been prepared so far.
-
property
basepath
¶ The absolute path pointing to the available working directories.
>>> from hydpy.core.filetools import FileManager >>> filemanager = FileManager() >>> filemanager.BASEDIR = "basename" >>> filemanager.projectdir = "projectname" >>> from hydpy import repr_, TestIO >>> with TestIO(): ... repr_(filemanager.basepath) '...hydpy/tests/iotesting/projectname/basename'
-
property
availabledirs
¶ The names and paths of the available working directories.
All possible working directories must be availablein the base directory of the respective
FileManager
subclass. Folders with names starting with an underscore do not count (use this for directories handling additional data files, if you like), while zipped directories do count as available directories:>>> from hydpy.core.filetools import FileManager >>> filemanager = FileManager() >>> filemanager.BASEDIR = "basename" >>> filemanager.projectdir = "projectname" >>> import os >>> from hydpy import repr_, TestIO >>> TestIO.clear() >>> with TestIO(): ... os.makedirs("projectname/basename/folder1") ... os.makedirs("projectname/basename/folder2") ... open("projectname/basename/folder3.zip", "w").close() ... os.makedirs("projectname/basename/_folder4") ... open("projectname/basename/folder5.tar", "w").close() ... filemanager.availabledirs Folder2Path(folder1=.../projectname/basename/folder1, folder2=.../projectname/basename/folder2, folder3=.../projectname/basename/folder3.zip)
-
property
currentdir
¶ The name of the current working directory containing the relevant files.
To show most of the functionality of
property
currentdir
(we explain unpacking zipped files on the fly in the documentation on functionzip_currentdir()
), we first prepare aFileManager
object with the defaultbasepath
projectname/basename:>>> from hydpy.core.filetools import FileManager >>> filemanager = FileManager() >>> filemanager.BASEDIR = "basename" >>> filemanager.DEFAULTDIR = None >>> filemanager.projectdir = "projectname" >>> import os >>> from hydpy import repr_, TestIO >>> TestIO.clear() >>> with TestIO(): ... os.makedirs("projectname/basename") ... repr_(filemanager.basepath) '...hydpy/tests/iotesting/projectname/basename'
At first, the base directory is empty and asking for the current working directory results in the following error:
>>> with TestIO(): ... filemanager.currentdir Traceback (most recent call last): ... RuntimeError: The current working directory of the FileManager object has not been defined manually and cannot be determined automatically: `.../projectname/basename` does not contain any available directories.
If only one directory exists, it is considered as the current working directory automatically:
>>> with TestIO(): ... os.mkdir("projectname/basename/dir1") ... filemanager.currentdir 'dir1'
property
currentdir
memorises the name of the current working directory, even if another directory is added later to the base path:>>> with TestIO(): ... os.mkdir("projectname/basename/dir2") ... filemanager.currentdir 'dir1'
Set the value of
currentdir
toNone
to let it forget the memorised directory. After that, to try to query the current working directory results in another error, as it is not clear which directory to select:>>> with TestIO(): ... filemanager.currentdir = None ... filemanager.currentdir Traceback (most recent call last): ... RuntimeError: The current working directory of the FileManager object has not been defined manually and cannot be determined automatically: `....../projectname/basename` does contain multiple available directories (dir1 and dir2).
Setting
currentdir
manually solves the problem:>>> with TestIO(): ... filemanager.currentdir = "dir1" ... filemanager.currentdir 'dir1'
Remove the current working directory dir1 with the del statement:
>>> with TestIO(): ... del filemanager.currentdir ... os.path.exists("projectname/basename/dir1") False
FileManager
subclasses can define a default directory name. When many directories exist, and none is selected manually, the default directory is selected automatically. The following example shows an error message due to multiple directories without any having the default name:>>> with TestIO(): ... os.mkdir("projectname/basename/dir1") ... filemanager.DEFAULTDIR = "dir3" ... del filemanager.currentdir ... filemanager.currentdir Traceback (most recent call last): ... RuntimeError: The current working directory of the FileManager object has not been defined manually and cannot be determined automatically: The default directory (dir3) is not among the available directories (dir1 and dir2).
We can fix this by adding the required default directory manually:
>>> with TestIO(): ... os.mkdir("projectname/basename/dir3") ... filemanager.currentdir 'dir3'
Setting the
currentdir
to dir4 not only overwrites the default name but also creates the required folder:>>> with TestIO(): ... filemanager.currentdir = "dir4" ... filemanager.currentdir 'dir4' >>> with TestIO(): ... sorted(os.listdir("projectname/basename")) ['dir1', 'dir2', 'dir3', 'dir4']
Failed attempts in removing directories result in error messages like the following one:
>>> import shutil >>> from unittest.mock import patch >>> with patch.object(shutil, "rmtree", side_effect=AttributeError): ... with TestIO(): ... del filemanager.currentdir Traceback (most recent call last): ... AttributeError: While trying to delete the current working directory `.../projectname/basename/dir4` of the FileManager object, the following error occurred: ...
Then, the current working directory still exists and is remembered by property
currentdir
:>>> with TestIO(): ... filemanager.currentdir 'dir4' >>> with TestIO(): ... sorted(os.listdir("projectname/basename")) ['dir1', 'dir2', 'dir3', 'dir4']
-
property
currentpath
¶ The absolute path of the current working directory.
>>> from hydpy.core.filetools import FileManager >>> filemanager = FileManager() >>> filemanager.BASEDIR = "basename" >>> filemanager.projectdir = "projectname" >>> from hydpy import repr_, TestIO >>> with TestIO(): ... filemanager.currentdir = "testdir" ... repr_(filemanager.currentpath) '...hydpy/tests/iotesting/projectname/basename/testdir'
-
property
filenames
¶ The names of the files placed in the current working directory, except those starting with an underscore.
>>> from hydpy.core.filetools import FileManager >>> filemanager = FileManager() >>> filemanager.BASEDIR = "basename" >>> filemanager.projectdir = "projectname" >>> from hydpy import TestIO >>> with TestIO(): ... filemanager.currentdir = "testdir" ... open("projectname/basename/testdir/file1.txt", "w").close() ... open("projectname/basename/testdir/file2.npy", "w").close() ... open("projectname/basename/testdir/_file1.nc", "w").close() ... filemanager.filenames ['file1.txt', 'file2.npy']
-
property
filepaths
¶ The absolute path names of the files returned by property
filenames
.>>> from hydpy.core.filetools import FileManager >>> filemanager = FileManager() >>> filemanager.BASEDIR = "basename" >>> filemanager.projectdir = "projectname" >>> from hydpy import repr_, TestIO >>> with TestIO(): ... filemanager.currentdir = "testdir" ... open("projectname/basename/testdir/file1.txt", "w").close() ... open("projectname/basename/testdir/file2.npy", "w").close() ... open("projectname/basename/testdir/_file1.nc", "w").close() ... for filepath in filemanager.filepaths: ... repr_(filepath) '...hydpy/tests/iotesting/projectname/basename/testdir/file1.txt' '...hydpy/tests/iotesting/projectname/basename/testdir/file2.npy'
-
zip_currentdir
() → None[source]¶ Pack the current working directory in a zip file.
FileManager
subclasses allow for manual packing and automatic unpacking of working directories. The only supported format is “zip”. The original directories and zip files are removed after packing or unpacking, respectively, to avoid possible inconsistencies.As an example scenario, we prepare a
FileManager
object with the current working directory folder containing the files test1.txt and text2.txt:>>> from hydpy.core.filetools import FileManager >>> filemanager = FileManager() >>> filemanager.BASEDIR = "basename" >>> filemanager.DEFAULTDIR = None >>> filemanager.projectdir = "projectname" >>> import os >>> from hydpy import repr_, TestIO >>> TestIO.clear() >>> basepath = "projectname/basename" >>> with TestIO(): ... os.makedirs(basepath) ... filemanager.currentdir = "folder" ... open(f"{basepath}/folder/file1.txt", "w").close() ... open(f"{basepath}/folder/file2.txt", "w").close() ... filemanager.filenames ['file1.txt', 'file2.txt']
The directories existing under the base path are identical with the ones returned by property
availabledirs
:>>> with TestIO(): ... sorted(os.listdir(basepath)) ... filemanager.availabledirs ['folder'] Folder2Path(folder=.../projectname/basename/folder)
After packing the current working directory manually, it still counts as an available directory:
>>> with TestIO(): ... filemanager.zip_currentdir() ... sorted(os.listdir(basepath)) ... filemanager.availabledirs ['folder.zip'] Folder2Path(folder=.../projectname/basename/folder.zip)
Instead of the complete directory, only the contained files are packed:
>>> from zipfile import ZipFile >>> with TestIO(): ... with ZipFile("projectname/basename/folder.zip", "r") as zp: ... sorted(zp.namelist()) ['file1.txt', 'file2.txt']
The zip file is unpacked again, as soon as folder becomes the current working directory:
>>> with TestIO(): ... filemanager.currentdir = "folder" ... sorted(os.listdir(basepath)) ... filemanager.availabledirs ... filemanager.filenames ['folder'] Folder2Path(folder=.../projectname/basename/folder) ['file1.txt', 'file2.txt']
-
-
class
hydpy.core.filetools.
NetworkManager
[source]¶ Bases:
hydpy.core.filetools.FileManager
Manager for network files.
The base and default folder names of class
NetworkManager
are:>>> from hydpy.core.filetools import NetworkManager >>> NetworkManager.BASEDIR 'network' >>> NetworkManager.DEFAULTDIR 'default'
The documentation of base class
FileManager
explains most aspects of usingNetworkManager
objects. The following examples deal with the extended features of classNetworkManager
, which are reading, writing, and removing network files. For this purpose, we prepare the example project LahnH in the iotesting directory by calling functionprepare_full_example_1()
:>>> from hydpy.examples import prepare_full_example_1 >>> prepare_full_example_1()
You can define the complete network structure of an HydPy project by an arbitrary number of “network files”. These are valid Python files which define certain
Node
andElement
as well as their connections. Network files are allowed to overlap, meaning two or more files can define the same objects (in a consistent manner only, of course). The primary purpose of classNetworkManager
is to execute each network file individually and pass its content to aSelection
object, which is done by methodload_files()
:>>> networkmanager = NetworkManager() >>> from hydpy import TestIO >>> with TestIO(): ... networkmanager.projectdir = "LahnH" ... selections = networkmanager.load_files()
Method
load_files()
takes file names as selection names (without file endings). Additionally, it creates a “complete” selection, including the whole set ofNode
andElement
objects of the file specific selections:>>> selections Selections("complete", "headwaters", "nonheadwaters", "streams") >>> selections.headwaters Selection("headwaters", nodes=("dill", "lahn_1"), elements=("land_dill", "land_lahn_1")) >>> selections.complete Selection("complete", nodes=("dill", "lahn_1", "lahn_2", "lahn_3"), elements=("land_dill", "land_lahn_1", "land_lahn_2", "land_lahn_3", "stream_dill_lahn_2", "stream_lahn_1_lahn_2", "stream_lahn_2_lahn_3"))
Method
save_files()
writes allSelection
objects into separate files. We first change the current working directory to assure we do not overwrite already existing files:>>> import os >>> with TestIO(): ... networkmanager.currentdir = "testdir" ... networkmanager.save_files(selections) ... sorted(os.listdir("LahnH/network/testdir")) ['headwaters.py', 'nonheadwaters.py', 'streams.py']
Reloading and comparing with the still available
Selection
objects proves that the contents of the original and the new network files are equivalent:>>> with TestIO(): ... selections == networkmanager.load_files() True
Method
delete_files()
removes the network files of the givenSelection
objects:>>> selections -= selections.streams >>> with TestIO(): ... networkmanager.delete_files(selections) ... sorted(os.listdir("LahnH/network/testdir")) ['streams.py']
When defining network files, many things can go wrong. In the following, we list all specialised error messages, of what we hope to be concrete enough to aid in finding the relevant problems:
>>> with TestIO(): ... networkmanager.delete_files(["headwaters"]) Traceback (most recent call last): ... FileNotFoundError: While trying to remove the network files of selections `['headwaters']`, the following error occurred: ...
>>> with TestIO(): ... with open("LahnH/network/testdir/streams.py", "w") as wrongfile: ... _ = wrongfile.write("x = y") ... networkmanager.load_files() Traceback (most recent call last): ... NameError: While trying to load the network file `...streams.py`, the following error occurred: name 'y' is not defined
>>> with TestIO(): ... with open("LahnH/network/testdir/streams.py", "w") as wrongfile: ... _ = wrongfile.write("from hydpy import Node") ... networkmanager.load_files() Traceback (most recent call last): ... RuntimeError: The class Element cannot be loaded from the network file `...streams.py`.
>>> with TestIO(): ... with open("LahnH/network/testdir/streams.py", "w") as wrongfile: ... _ = wrongfile.write("from hydpy import Element") ... networkmanager.load_files() Traceback (most recent call last): ... RuntimeError: The class Node cannot be loaded from the network file `...streams.py`.
>>> import shutil >>> with TestIO(): ... shutil.rmtree("LahnH/network/testdir") ... networkmanager.save_files(selections) Traceback (most recent call last): ... FileNotFoundError: While trying to save the selections `Selections("complete", "headwaters", "nonheadwaters")` into network files, the following error occurred: ...
-
load_files
() → hydpy.core.selectiontools.Selections[source]¶ Read all network files of the current working directory, structure their contents in a
Selections
object, and return it.See the main documentation on class
NetworkManager
for further information.
-
save_files
(selections: Iterable[hydpy.core.selectiontools.Selection]) → None[source]¶ Save the
Selection
objects contained in the givenSelections
instance to separate network files.See the main documentation on class
NetworkManager
for further information.
-
delete_files
(selections: Iterable[hydpy.core.selectiontools.Selection]) → None[source]¶ Delete the network files corresponding to the given selections (e.g. a
list
ofstr
objects or aSelections
object).See the main documentation on class
NetworkManager
for further information.
-
-
class
hydpy.core.filetools.
ControlManager
[source]¶ Bases:
hydpy.core.filetools.FileManager
Manager for control parameter files.
The base and default folder names of class
ControlManager
are:>>> from hydpy.core.filetools import ControlManager >>> ControlManager.BASEDIR 'control' >>> ControlManager.DEFAULTDIR 'default'
Class
ControlManager
extends the functionalities of classFileManager
only slightly, which is why the documentation on classFileManager
should serve as a good starting point for understanding classControlManager
. Also see the documentation on methodprepare_models()
of classHydPy
, which relies on the functionalities of classControlManager
.-
load_file
(element: Optional[hydpy.core.devicetools.Element] = None, filename: Optional[str] = None, clear_registry: bool = True) → Dict[str, Any][source]¶ Return the namespace of the given file (and eventually of its corresponding auxiliary subfiles).
By default,
ControlManager
clears the internal registry when after having loaded a control file and all its corresponding auxiliary files. You can change this behaviour by passing False to the clear_registry argument, which might decrease model initialisation times significantly. However, then it is your own responsibility to call the methodclear_registry()
when necessary (usually, before reloading a changed control file).One advantage of using method
load_file()
directly is that it supports reading control files that are yet not correctly integrated into a complete HydPy project by passing its name:>>> from hydpy.examples import prepare_full_example_1 >>> prepare_full_example_1()
>>> from hydpy.core.filetools import ControlManager >>> controlmanager = ControlManager() >>> from hydpy import pub, round_, TestIO >>> pub.timegrids = "2000-01-01", "2001-01-01", "12h" >>> with TestIO(): ... controlmanager.projectdir = "LahnH" ... results = controlmanager.load_file(filename="land_dill")
>>> results["control"] area(692.3) nmbzones(12) zonetype(FIELD, FOREST, FIELD, FOREST, FIELD, FOREST, FIELD, FOREST, FIELD, FOREST, FIELD, FOREST) zonearea(14.41, 7.06, 70.83, 84.36, 70.97, 198.0, 27.75, 130.0, 27.28, 56.94, 1.09, 3.61) zonez(2.0, 2.0, 3.0, 3.0, 4.0, 4.0, 5.0, 5.0, 6.0, 6.0, 7.0, 7.0) zrelp(3.75) zrelt(3.75) zrele(3.665) pcorr(1.0) pcalt(0.1) rfcf(1.04283) sfcf(1.1) tcalt(0.6) ecorr(1.0) ecalt(0.0) epf(0.02) etf(0.1) ered(0.0) ttice(nan) icmax(field=1.0, forest=1.5) tt(0.55824) ttint(2.0) dttm(0.0) cfmax(field=4.55853, forest=2.735118) gmelt(nan) cfr(0.05) whc(0.1) fc(278.0) lp(0.9) beta(2.54011) percmax(1.39636) cflux(0.0) resparea(True) recstep(1200.0) alpha(1.0) k(0.005618) k4(0.05646) gamma(0.0) maxbaz(0.36728) abstr(0.0)
>>> results["percmax"].values 0.69818
Passing neither a filename nor an
Element
object raises the following error:>>> controlmanager.load_file() Traceback (most recent call last): ... RuntimeError: When trying to load a control file you must either pass its name or the responsible Element object.
-
classmethod
read2dict
(filename: str, info: Dict[str, Any]) → None[source]¶ Read the control parameters from the given path (and its auxiliary paths, where appropriate) and store them in the given
dict
object info.Note that`info` can be used to feed information into the execution of control files. Use this method only if you are entirely sure on how the control parameter import of HydPy works. Otherwise, you should most probably prefer to use the method
load_file()
.
-
-
class
hydpy.core.filetools.
ConditionManager
[source]¶ Bases:
hydpy.core.filetools.FileManager
Manager for condition files.
The base folder name of class
ConditionManager
is:>>> from hydpy.core.filetools import ConditionManager >>> ConditionManager.BASEDIR 'conditions'
Class
ConditionManager
generally works like classFileManager
. The following examples, based on the LahnH example project, explain the additional functionalities of theConditionManager
specific propertiesinputpath
andoutputpath
:>>> from hydpy.examples import prepare_full_example_2 >>> hp, pub, TestIO = prepare_full_example_2()
If the current directory named is not defined explicitly, both properties construct it following the actual simulation start or end date, respectively:
>>> from hydpy import repr_ >>> with TestIO(): ... repr_(pub.conditionmanager.inputpath) ... repr_(pub.conditionmanager.outputpath) '.../hydpy/tests/iotesting/LahnH/conditions/init_1996_01_01_00_00_00' '.../hydpy/tests/iotesting/LahnH/conditions/init_1996_01_05_00_00_00'
>>> pub.timegrids.sim.firstdate += "1d" >>> pub.timegrids.sim.lastdate -= "1d" >>> pub.timegrids Timegrids(init=Timegrid("1996-01-01 00:00:00", "1996-01-05 00:00:00", "1d"), sim=Timegrid("1996-01-02 00:00:00", "1996-01-04 00:00:00", "1d"), eval_=Timegrid("1996-01-01 00:00:00", "1996-01-05 00:00:00", "1d"))
>>> with TestIO(): ... repr_(pub.conditionmanager.inputpath) ... repr_(pub.conditionmanager.outputpath) '.../hydpy/tests/iotesting/LahnH/conditions/init_1996_01_02_00_00_00' '.../hydpy/tests/iotesting/LahnH/conditions/init_1996_01_04_00_00_00'
Use the property
currentdir
to change the values of both properties:>>> with TestIO(): ... pub.conditionmanager.currentdir = "test" ... repr_(pub.conditionmanager.inputpath) ... repr_(pub.conditionmanager.outputpath) '.../hydpy/tests/iotesting/LahnH/conditions/test' '.../hydpy/tests/iotesting/LahnH/conditions/test'
After deleting the custom value of property
currentdir
, both propertiesinputpath
andoutputpath
work as before:>>> with TestIO(): ... del pub.conditionmanager.currentdir ... repr_(pub.conditionmanager.inputpath) ... repr_(pub.conditionmanager.outputpath) '.../hydpy/tests/iotesting/LahnH/conditions/init_1996_01_02_00_00_00' '.../hydpy/tests/iotesting/LahnH/conditions/init_1996_01_04_00_00_00'
The date based construction of directory names requires a
Timegrids
object available in modulepub
:>>> del pub.timegrids >>> with TestIO(): ... repr_(pub.conditionmanager.inputpath) Traceback (most recent call last): ... hydpy.core.exceptiontools.AttributeNotReady: While trying to determine the currently relevant input path for loading conditions file, the following error occurred: Attribute timegrids of module `pub` is not defined at the moment.
>>> del pub.timegrids >>> with TestIO(): ... repr_(pub.conditionmanager.outputpath) Traceback (most recent call last): ... hydpy.core.exceptiontools.AttributeNotReady: While trying to determine the currently relevant output path for saving conditions file, the following error occurred: Attribute timegrids of module `pub` is not defined at the moment.
-
property
inputpath
¶ The directory path for loading initial conditions.
See the main documentation on class
ConditionManager
for further information.
-
property
outputpath
¶ The directory path actual for saving (final) conditions.
See the main documentation on class
ConditionManager
for further information.
-
property
-
class
hydpy.core.filetools.
SequenceManager
[source]¶ Bases:
hydpy.core.filetools.FileManager
Manager for sequence files.
Usually, there is only one
SequenceManager
used within each HydPy project, stored in modulepub
. This object is responsible for the actual I/O tasks related toIOSequence
objects.Working with a complete HydPy project, one often does not use the
SequenceManager
directly, except one wishes to load data from or store data to directories that differ from the default settings. In the following examples, we show the essential features of classSequenceManager
based on the example project configuration defined by functionprepare_io_example_1()
.We prepare the project and select one 0-dimensional sequence of type
Sim
and one 1-dimensional sequence of typeNKor
for the following examples:>>> from hydpy.examples import prepare_io_example_1 >>> nodes, elements = prepare_io_example_1() >>> sim = nodes.node2.sequences.sim >>> nkor = elements.element2.model.sequences.fluxes.nkor
We store the time series data of both sequences in ASCII files (Methods
save_file()
andsave_ext()
are interchangeable here. The last one is only a convenience function for the first one):>>> from hydpy import pub >>> pub.sequencemanager.generalfiletype = "asc" >>> from hydpy import TestIO >>> with TestIO(): ... pub.sequencemanager.save_file(sim) ... nkor.save_ext()
To check that this was successful, we can load the file content from the output directory defined by
prepare_io_example_1()
and print it:>>> import os >>> from hydpy import round_ >>> def print_file(path, filename): ... path = os.path.join(path, filename) ... with TestIO(): ... with open(path) as file_: ... lines = file_.readlines() ... print("".join(lines[:3]), end="") ... for line in lines[3:]: ... round_([float(x) for x in line.split()]) >>> print_file("nodepath", "node2_sim_t.asc") Timegrid("2000-01-01 00:00:00+01:00", "2000-01-05 00:00:00+01:00", "1d") 64.0 65.0 66.0 67.0 >>> print_file("outputpath", "element2_flux_nkor.asc") Timegrid("2000-01-01 00:00:00+01:00", "2000-01-05 00:00:00+01:00", "1d") 16.0, 17.0 18.0, 19.0 20.0, 21.0 22.0, 23.0
To show that reloading the data works, we set the values of the time series of both objects to zero and recover the original values afterwards:
>>> sim.series = 0.0 >>> sim.series InfoArray([ 0., 0., 0., 0.]) >>> nkor.series = 0.0 >>> nkor.series InfoArray([[ 0., 0.], [ 0., 0.], [ 0., 0.], [ 0., 0.]]) >>> with TestIO(): ... pub.sequencemanager.load_file(sim) ... nkor.load_ext() >>> sim.series InfoArray([ 64., 65., 66., 67.]) >>> nkor.series InfoArray([[ 16., 17.], [ 18., 19.], [ 20., 21.], [ 22., 23.]])
Wrongly formatted ASCII files and incomplete data should result in understandable error messages:
>>> path = os.path.join("nodepath", "node2_sim_t.asc") >>> with TestIO(): ... with open(path) as file_: ... right = file_.read() ... wrong = right.replace("Timegrid", "timegrid") ... with open(path, "w") as file_: ... _ = file_.write(wrong) >>> with TestIO(): ... pub.sequencemanager.load_file(sim) Traceback (most recent call last): ... NameError: While trying to load the external data of sequence `sim` of node `node2`, the following error occurred: name 'timegrid' is not defined
>>> sim_series = sim.series.copy() >>> with TestIO(): ... lines = right.split("\n") ... lines[5] = "nan" ... wrong = "\n".join(lines) ... with open(path, "w") as file_: ... _ = file_.write(wrong) >>> with TestIO(): ... pub.sequencemanager.load_file(sim) Traceback (most recent call last): ... RuntimeError: While trying to load the external data of sequence `sim` of node `node2`, the following error occurred: The series array of sequence `sim` of node `node2` contains 1 nan value. >>> sim.series = sim_series
By default, overwriting existing time series files is disabled:
>>> with TestIO(): ... sim.save_ext() Traceback (most recent call last): ... OSError: While trying to save the external data of sequence `sim` of node `node2`, the following error occurred: Sequence `sim` of node `node2` is not allowed to overwrite the existing file `...`. >>> pub.sequencemanager.generaloverwrite = True >>> with TestIO(): ... sim.save_ext()
When a sequence comes with a weighting parameter referenced by
property
refweights
, one can save the averaged time series by using the methodsave_mean()
:>>> with TestIO(): ... nkor.save_mean() >>> print_file("outputpath", "element2_flux_nkor_mean.asc") Timegrid("2000-01-01 00:00:00+01:00", "2000-01-05 00:00:00+01:00", "1d") 16.5 18.5 20.5 22.5
Method
save_mean()
is strongly related with methodaverage_series()
, meaning one can pass the same arguments. We show this by changing the land use classes of element2 (parameterLnk
) to field (ACKER
) and water (WASSER
), and averaging the values of sequenceNKor
for the single area of type field only:>>> from hydpy.models.lland_v1 import ACKER, WASSER >>> nkor.subseqs.seqs.model.parameters.control.lnk = ACKER, WASSER >>> with TestIO(): ... nkor.save_mean("acker") >>> print_file("outputpath", "element2_flux_nkor_mean.asc") Timegrid("2000-01-01 00:00:00+01:00", "2000-01-05 00:00:00+01:00", "1d") 16.0 18.0 20.0 22.0
Another option is to store data using
numpy
binary files, which is a good option for saving computation times, but possibly a problematic option for sharing data with colleagues:>>> pub.sequencemanager.generalfiletype = "npy" >>> with TestIO(): ... sim.save_ext() ... nkor.save_ext()
The time information (without time zone information) is available within the first thirteen entries:
>>> path = os.path.join("nodepath", "node2_sim_t.npy") >>> from hydpy import numpy, print_values >>> with TestIO(): ... print_values(numpy.load(path)) 2000.0, 1.0, 1.0, 0.0, 0.0, 0.0, 2000.0, 1.0, 5.0, 0.0, 0.0, 0.0, 86400.0, 64.0, 65.0, 66.0, 67.0
Reloading the data works as expected:
>>> sim.series = 0.0 >>> nkor.series = 0.0 >>> with TestIO(): ... sim.load_ext() ... nkor.load_ext() >>> sim.series InfoArray([ 64., 65., 66., 67.]) >>> nkor.series InfoArray([[ 16., 17.], [ 18., 19.], [ 20., 21.], [ 22., 23.]])
Writing mean values into
numpy
binary files is also supported:>>> import numpy >>> with TestIO(): ... nkor.save_mean("wasser") ... numpy.load(os.path.join("outputpath", ... "element2_flux_nkor_mean.npy"))[-4:] array([ 17., 19., 21., 23.])
Generally, trying to load data for “deactivated” sequences results in the following error message:
>>> nkor.deactivate_ram() >>> with TestIO(clear_all=True): ... pub.sequencemanager.save_file(nkor) Traceback (most recent call last): ... AttributeError: Sequence `nkor` of element `element2` is not requested to make any internal data available.
The third option is to store data in netCDF files, which is explained separately in the documentation on class
NetCDFInterface
.In the examples above, we used some of the special configuration attributes of class
SequenceManager
, which we now elaborate by taking the “overwrite” attributes as an example.All special attributes can be used to configure
SequenceManager
different for different types of sequences:>>> pub.sequencemanager.inputoverwrite True >>> pub.sequencemanager.fluxoverwrite True >>> pub.sequencemanager.stateoverwrite True >>> pub.sequencemanager.nodeoverwrite True >>> pub.sequencemanager.tempoverwrite True
However, there is also a “general” attribute, covering all specific ones:
>>> pub.sequencemanager.generaloverwrite True
We can delete those attributes (which resets them to their default state) or assign alternative values:
>>> del pub.sequencemanager.inputoverwrite >>> pub.sequencemanager.fluxoverwrite = False >>> pub.sequencemanager.inputoverwrite False >>> pub.sequencemanager.fluxoverwrite False >>> pub.sequencemanager.generaloverwrite (False, True)
Use the “general” attribute to change all special ones at once:
>>> del pub.sequencemanager.generaloverwrite >>> pub.sequencemanager.inputoverwrite False >>> pub.sequencemanager.fluxoverwrite False >>> pub.sequencemanager.stateoverwrite False >>> pub.sequencemanager.nodeoverwrite False >>> pub.sequencemanager.tempoverwrite False
All other special configuration attributes do not return and except booleans but strings instead:
>>> pub.sequencemanager.generalaggregation 'none' >>> pub.sequencemanager.fluxaggregation = "mean" >>> pub.sequencemanager.generalaggregation ('mean', 'none')
>>> pub.sequencemanager.fluxaggregation = "wrong" Traceback (most recent call last): ... ValueError: The given mode `wrong` for aggregating time series is not available. Select one of the following modes: none and mean.
-
SUPPORTED_MODES
= ('npy', 'asc', 'nc')¶
-
inputfiletype
¶ Currently selected type of the input sequence files.
-
fluxfiletype
¶ Currently selected type of the flux sequence files.
-
statefiletype
¶ Currently selected type of the state sequence files.
-
nodefiletype
¶ Currently selected type of the node sequence files.
-
tempfiletype
¶ Currently selected type of the temporary sequence files.
-
generalfiletype
¶ >>> from hydpy.core.filetools import SequenceManager, _GeneralDescriptor >>> isinstance(SequenceManager.generaloverwrite, _GeneralDescriptor) True
-
inputoverwrite
¶ Currently selected overwrite flag of the input sequence files.
-
fluxoverwrite
¶ Currently selected overwrite flag of the flux sequence files.
-
stateoverwrite
¶ Currently selected overwrite flag of the state sequence files.
-
nodeoverwrite
¶ Currently selected overwrite flag of the node sequence files.
-
tempoverwrite
¶ Currently selected overwrite flag of the temporary sequence files.
-
generaloverwrite
¶ >>> from hydpy.core.filetools import SequenceManager, _GeneralDescriptor >>> isinstance(SequenceManager.generaloverwrite, _GeneralDescriptor) True
-
inputdirpath
¶ Path of the input sequence directory.
-
fluxdirpath
¶ Path of the flux sequence directory.
-
statedirpath
¶ Path of the state sequence directory.
-
nodedirpath
¶ Path of the node sequence directory.
-
tempdirpath
¶ Path of the temporary sequence directory.
-
generaldirpath
¶ >>> from hydpy.core.filetools import SequenceManager, _GeneralDescriptor >>> isinstance(SequenceManager.generaloverwrite, _GeneralDescriptor) True
-
inputaggregation
¶ Mode of aggregation for writing input time series data to files.
-
fluxaggregation
¶ Mode of aggregation for writing flux time series data to files.
-
stateaggregation
¶ Mode of aggregation for writing state time series data to files.
-
nodeaggregation
¶ Mode of aggregation for writing node time series data to files.
-
generalaggregation
¶ >>> from hydpy.core.filetools import SequenceManager, _GeneralDescriptor >>> isinstance(SequenceManager.generaloverwrite, _GeneralDescriptor) True
-
load_file
(sequence: sequencetools.IOSequence) → None[source]¶ Load data from an “external” data file and pass it to the given
IOSequence
.
-
save_file
(sequence: sequencetools.IOSequence, array: Optional[numpy.ndarray] = None) → None[source]¶ Write the data stored in the
series
property of the givenIOSequence
into an “external” data file.
-
property
netcdfreader
¶ A
NetCDFInterface
object prepared by methodopen_netcdfreader()
and to be finalised by methodclose_netcdfreader()
.>>> from hydpy.core.filetools import SequenceManager >>> sm = SequenceManager() >>> sm.netcdfreader Traceback (most recent call last): ... RuntimeError: The sequence file manager does currently handle no NetCDF reader object.
>>> sm.open_netcdfreader() >>> from hydpy import classname >>> classname(sm.netcdfreader) 'NetCDFInterface'
>>> sm.close_netcdfreader() >>> sm.netcdfreader Traceback (most recent call last): ... RuntimeError: The sequence file manager does currently handle no NetCDF reader object.
-
open_netcdfreader
(flatten: Optional[bool] = None, isolate: Optional[bool] = None, timeaxis: Optional[int] = None) → None[source]¶ Prepare a new
NetCDFInterface
object for reading data.
-
close_netcdfreader
() → None[source]¶ Read data with a prepared
NetCDFInterface
object and delete it afterwards.
-
property
netcdfwriter
¶ A
NetCDFInterface
object prepared by methodopen_netcdfwriter()
and to be finalised by methodclose_netcdfwriter()
.>>> from hydpy.core.filetools import SequenceManager >>> sm = SequenceManager() >>> sm.netcdfwriter Traceback (most recent call last): ... RuntimeError: The sequence file manager does currently handle no NetCDF writer object.
>>> sm.open_netcdfwriter() >>> from hydpy import classname >>> classname(sm.netcdfwriter) 'NetCDFInterface'
>>> sm.close_netcdfwriter() >>> sm.netcdfwriter Traceback (most recent call last): ... RuntimeError: The sequence file manager does currently handle no NetCDF writer object.
-
open_netcdfwriter
(flatten: Optional[bool] = None, isolate: Optional[bool] = None, timeaxis: Optional[int] = None) → None[source]¶ Prepare a new
NetCDFInterface
object for writing data.
-
close_netcdfwriter
() → None[source]¶ Write data with a prepared
NetCDFInterface
object and delete it afterwards.
-