HJoin ADAFs

../../../../../_images/hjoin_adaf.svg

Horizontal join of a list of ADAFs into one ADAF. This means that all systems in each ADAF is are congregated into one ADAF with many systems. Using the option ‘Use index as prefix’ will result in columns and systems results in systems’ names getting the list index of the ADAF as a prefix to keep systems with the same names. Meta data and results will be joined horizontally with the same prefixing. Unchecking the option results in the same behaviour as Hjoin ADAFs where all but the latest instance are discarded.

Ports:

Inputs:

port1:

[adaf]

ADAFs list

Outputs:

port1:

adaf

Joined ADAFs

Configuration:

merge
If rasters have the same name, merge them

The horisontal join, or the HJoin, of ADAF objects has the purpose to merge data that has been simultaneously collected by different measurement systems and been imported into different ADAFs. The output of the operation is a new ADAF, where each data container is the result of a horisontal join between the two corresponding data containers of the incoming ADAFs.

The content of the metadata and the result containers are tables and the horisontal join of these containers follows the procedure described in HJoin Table.

The timeseries container has the structure of a dictionary, where the keys at the first instance/level are the names of the systems from which the time resolved data is collected from. The result of a horisontal join operation upon two timeseries containers will become a new container to which the content of the initial containers have been added. In this process it is important to remember that a system in the outgoing container will be overwritten if one adds a new system with the same name.

In other terms, HJoining an ADAF with another will horisontally join the Meta and Result sections in the same way as HJoin Table, and add the systems to the list of system. The systems themselves will not be horisontally joined. The column names in Meta and Res must have different names, or else the latest instance will overwrite the previous. The same holds true for the systems.

class node_hjoin_adaf.HJoinADAFsList[source]