You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looks like in the current calc_normalized_import_bids, the import bids remain zero if the desired_exports < max_exports. This value is then used to get the gross import, so this seems pretty damaging to trading:
Furthermore, the import_tariff actions seem to be delayed by a timestep. Both calc_trade_sanctions and calc_welfloss_multiplier, get the action from the prev_state. Is this intentional?
Looks like in the current
calc_normalized_import_bids
, the import bids remain zero if thedesired_exports
<max_exports
. This value is then used to get the gross import, so this seems pretty damaging to trading:climate-cooperation-competition/rice.py
Lines 1249 to 1275 in f743956
Furthermore, the import_tariff actions seem to be delayed by a timestep. Both
calc_trade_sanctions
andcalc_welfloss_multiplier
, get the action from the prev_state. Is this intentional?climate-cooperation-competition/rice.py
Lines 767 to 768 in f743956
climate-cooperation-competition/rice.py
Lines 797 to 815 in f743956
The text was updated successfully, but these errors were encountered: