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
We should define formally what arguments the objects accept
name: any valid python/julia identifier without a double underscore ?
date: signed integer (for now)
subscripts: list of names
As for the normalized string, initial proposal is: {}__{}__{}'.format(name, (str(date) if date>=0 else 'm'+str(date), str.join('_', subscripts)
So, currently, there is an implementation for 1.->2. under python only. I am not checking the tickbox though until we are sure about the definition/normalization.
Variables, with optional time subscripts and indices should have three equivalent representations:
Symbol(name='β', subscripts=['i'], date=1)
β__1__i
)\beta_{i,t+1}
)We can define the expected correspondences in https://github.com/EconForge/dolang/blob/master/tests/symbols.yaml .
We should define formally what arguments the objects accept
As for the normalized string, initial proposal is:
{}__{}__{}'.format(name, (str(date) if date>=0 else 'm'+str(date), str.join('_', subscripts)
So, currently, there is an implementation for 1.->2. under python only. I am not checking the tickbox though until we are sure about the definition/normalization.
[] python: 1.->2.
[] python: 1.->3.
[] python: 2.->1.
[] python: 3.->1. (not urgent)
[] julia: 1.->2.
[] julia: 1.->3.
[] julia: 2.->1.
[] julia: 3.->1. (not urgent)
The text was updated successfully, but these errors were encountered: