search

OutlierVentures / QTM-Interface

GNU General Public License v3.0
28 stars 18 forks source link

Timestamp Data Issues #24

Closed BlockBoy32 closed 1 year ago

BlockBoy32 commented 1 year ago

In order to line up all my data properly for the user adoption I have to have the policy start at prev_state['timestep'] == 2. The first row of data is the initalized values and then the real data starts on that second row. Do you know why that might be happening? For your vesting did you need to start at 2? have you verified the data for that section? The reason I ask is because as I start verifying the data for the business assumptions I need to line it up with the user adoption numbers. Let me know what you think

achimstruve commented 1 year ago

What do you mean by row? Do you mean substep? There are several substeps within one timestep in cadCAD.

BlockBoy32 commented 1 year ago

I mean timestep. It won't hold me back from developing so I will just continue with how it is and we can sync on it during our next call if I am still confused by then. Have fun at Ethcc

achimstruve commented 1 year ago

This error occurred due to a misplaced continue keyword in a loop inside of the vesting.py. It should be fixed now and all vesting numbers are now matching the data tables in the QTM spreadsheet version.