Skip to content
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

Undefined constructor. #153

Open
Gertian opened this issue Sep 26, 2024 · 4 comments
Open

Undefined constructor. #153

Gertian opened this issue Sep 26, 2024 · 4 comments

Comments

@Gertian
Copy link
Contributor

Gertian commented Sep 26, 2024

Hi,

I'm using the AD extension of TensorKit and ran into some problems due to this line :

∂t = TensorMap(unthunk(ΔA), codomain(t), domain(t); tol=Inf)

From what I understand the tol kwarg has been removed from the basic functionality of TensorKit ?

Probably it's fair to just remove this ?

@lkdvos
Copy link
Collaborator

lkdvos commented Sep 30, 2024

I did not really have the time to go into this in more detail, but I think you are getting a bit confused because of the versions. The master might not have this anymore, but the latest released version definitely does: see here

I did notice that it seems like that constructor only exists for ProductSpace arguments for codomain and domain, and does not have the automatic conversion behavior that the other constructors have to automatically turn a VectorSpace into a ProductSpace{S,1} etc. It might be that this is what is causing you issues? Alternatively, that function is definitely only defined for DenseArray subtypes, so that might also be what's going on.

For future reference, it is definitely useful to include additional information in your issues. If you just point at a single line, it is very hard to figure out what is going wrong, since I don't know what you were running, what the error message was, what the problems are etc. Basically, I am just wildly guessing what might have gone wrong, or what might have been overlooked, or what are common mistakes (on both our sides). Additionally, sometimes you might have an idea of where it is going wrong, but if this turns out to be not entirely true it becomes very hard to debug the issue 😉

@Gertian
Copy link
Contributor Author

Gertian commented Oct 1, 2024

Hi Lukas,

I was indeed running this on the master which might have caused the issue. I'll try this again on the latest release to see if the problem persists.

As for the remainder of your message. I'm sorry, I keep messing this up indeed. Should I make it a habbit of ALWAYS including a full stack trace ?

@lkdvos
Copy link
Collaborator

lkdvos commented Oct 1, 2024

I think this discourse post actually summarizes quite well how to get help asap 😉

@Jutho
Copy link
Owner

Jutho commented Oct 1, 2024

Maybe we should include this in the default text when opening new issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants