Posts: 3
Threads: 1
Likes Received: 0 in 0 posts
Likes Given: 2
Joined: Jan 2025
Hello everyone,
I'm trying to understand the definitions of the columns in the ~TFM_PSets sets table.
Could someone please explain what the following columns mean?
- t_pos_andor_forsets
- t_pos_andor
- t_neg_andor_forsets
- t_neg_andor
Any help would be greatly appreciated.
Thank you
Posts: 2,175
Threads: 26
Likes Received: 113 in 99 posts
Likes Given: 37
Joined: Jun 2010
11-09-2025, 03:24 PM
(This post was last modified: 11-09-2025, 03:25 PM by Antti-L.)
I found the following explanations in my archives:
The following fields can be used to control how declarations across fields are joined:
T_Pos_AndOr – AND/OR in this column applies to the positive (include) conditions for technology (Process) filter
T_Neg_AndOr – Applies to the negative (exclude) filters for technology filter
C_Pos_AndOr – For positive filters on commodities
C_Neg_AndOr – For negative filters on commodities
The default value for all these is AND. Lets take an example -
Filter setting: PSet_SET=ELE; PSet_PN=E*,-EGAS*; PSet_CI=ELC*,-ELCGAS
Default Interpretation: Include all techs which have set = ELE and name like E* and input commodity=ELC*; from these, exclude techs with name like EGAS* and input=ELCGAS
I think the default for *_Neg_* should be changed to OR.
This was the documentation for VEDA-FE. Possibly the default for *_Neg_* has been changed in VEDA2.
Posts: 3
Threads: 1
Likes Received: 0 in 0 posts
Likes Given: 2
Joined: Jan 2025
11-09-2025, 03:31 PM
(This post was last modified: 11-09-2025, 03:31 PM by Alain Tran.)
Thank you @Antti-L , your explanation is clear.
Do you have any idea about the "_forsets" suffix?
Posts: 1,091
Threads: 43
Likes Received:
26 in 22 posts
Likes Given: 43
Joined: May 2010
Reputation:
26
in case you want to put an "OR" between the sets and name/topology filters.
Posts: 3
Threads: 1
Likes Received: 0 in 0 posts
Likes Given: 2
Joined: Jan 2025
Thank you @AKanudia, this is all clear!