Repository navigation
Ambiguous spec expressions #14
Description
In the joint tour frequency and composition component, we have (for example):
This expression is summarized as (bool * bool) + (bool * bool). The two parenthetical terms each neatly and correctly resolves to a binary value regardless of whether the operands are treated as literal boolean values or their (0,1) numerical equivalent. However, + operator is not so clean; if both operands are True, we could arrive at different results:
- Interpret as numeric, so
1 + 1 = 2, or - Interpret as boolean, so
True + True = True.
The numexpr engine of pandas.eval will (with arguably good reason) punt on solving this, throwing a NotImplementedError. Pandas can fall back to numpy logic, which will solve the expression based on the logic (2) and get True. Sharrow converts the booleans to numbers, using logic (1).
It would be better to write expressions so they are less ambiguous, and (obviously) so they resolve the same with or without sharrow. Based on context clues from the rest of the spec, it appears the intention of these expressions is following logic (1). @dhensle can you (or whomever at RSG crafted this spec) confirm the preferred interpretation?
Activity
i-am-sijia commentedon May 6, 2024
I can answer this since I worked on the initial conversion of joint tour frequency composition model.
This is what's coded in the BayDAG CT-RAMP UEC for the joint tour frequency composition model:
In CT-RAMP, expressions are returned in numeric.
A==Breturns either numeric 1 or 0, which means this expression should return 0, 1, or 2.So this expression should be rewritten to follow logic (1).
@dhensle do you agree? If we correct the expressions, it will cause abm3 results to change in the sharrow off mode, perhaps slightly, depending on how many 2+ joint tour households are there.
dhensle commentedon May 6, 2024
Yes, agreed. We should be replicating the original CT-RAMP logic/results.
cc: @aletzdy