-
Notifications
You must be signed in to change notification settings - Fork 180
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
Attribute omissions #1210
Comments
Thank you! @shaltielshmid and I are going to systematically go over these modules and make the attributes available. |
@shaltielshmid -- as we talk about the attribute (property) exposure, it reminds me that I started on an effort to move more of the module login into managed code. Could you take a look at my (draft) PR for that? It's not meant to be merged, just looked at. I think it may be a better starting point for this work (and avoids a lot of future merge conflicts). |
Will do! |
Will all attributes be made available in the future? |
Yes, we are working on an update which should make all the attributes available |
Yes, it is the intent to do that. Right now, my two priorties are:
The refactoring that will allow attributes to be exposed more consistently comes after. |
Thank you both very much for your efforts, I believe that TorchSharp will become even more powerful. |
Lately, I have been trying to migrate features from Thop to TorchSharp, and in the process, I have discovered several attribute omissions in specific model components:
The properties related to Convolutional layers, such as groups, among others, are currently not available.
Attributes inherent to Softmax layers, notably dim, are missing.
Features of Linear layers, including the in_features property, are also not included at this time.
ect
The text was updated successfully, but these errors were encountered: