-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create mapping of pyttb-TTB functionality #180
Comments
I believe https://github.com/sandialabs/pyttb/wiki/Development-Plans already has moderate coverage here (in case this wasn't already what you were thinking about). |
Yes, I was going to start from there (which is incomplete) and then consider moving it to RTD as a new section. We're past the original intent of dev plans, but this will provide the basis for the MATLAB->pyttb mappings. |
This is related to: As part of the RTD docs, I suggest we add a subsection of Getting Started called, "pyttb for MATLAB Users" |
I saw @jeremy-myers started to work on this already by writing up tables in restructured text (which looks great so far!). I would really like something that fails loudly when we continue to updated pyttb and potentially diverge from the MATLAB. We could probably setup the MATLAB getting started stuff as Jupyter notebooks rendered to our read the docs as well. Then if we change and interface that breaks it won't be allowed to check in. There are probably other ways. Alternatively I think we can just add doctests to sphinx/RST if we think that would be easier. I'm not sure if the ability to interact with a jupyter notebook is as relevant for users coming from MATLAB. |
I've been quiet the last few weeks but expect to see some commits ones this PR this upcoming week. |
Zero rush on my side. I was on a variety of flights this week so I was much more active. Just wanted to weigh in to reduce a large refactor after this was 100% complete. |
To assist transitions from the Tensor Toolbox for MATLAB to pyttb, create some reference documentation of the mapping of methods and any important differences.
The text was updated successfully, but these errors were encountered: