US model Aliases #741
Replies: 1 comment 3 replies
-
I don't see any forked repository on your github profile. https://github.com/alvinchen1?tab=repositories. Currently the supported_models.md reads all the model.json files from the data directory. This needs to be altered to also read aliases, but than we don't have name information. I will figure something out for this in the future as we are adding more aliases lately and it will make sense that users can also find the is the supported list. I cannot find much information about LCF001 and LCF002 on google, so I also don't know how to know if they are similar yet. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Howdy! I was looking over the changes in #738 and that seems to have opened up a lot of supported models for me. Awesome work! A few questions:
I am attempting to understand the mapping in aliases.py, and I think I comprehend it, but my read of it is that there are models like LCA005 which map to LCA001, right (ref: line 92)? If that's the case, then would it not also make sense to update supported_models.md to include LCA005, for example? I'd like to contribute. I tried to create a forked repository and branch, edited the file with all the US aliases but couldn't commit it. I think I need a basic GitHub 101 lesson (obviously not for this forum to resolve my education issues).
I have a model LCF001 which I believe can be aliased to the LCF002 (Hue Calla Outdoor Pedestal). What information do you need to approve an alias like this? I'll be happy to dig up whatever I can to help contribute and expand to include this model.
Awesome work as always, sorry I'm not more contributing. I did try to submit a branch/pull request for 1), but I must be doing something stupid.
Beta Was this translation helpful? Give feedback.
All reactions