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
18mm Q-jets are listed under manufacturer "Quest".
24mm Q-jets are listed under manufacturer "AeroTech".
All these motors are of course manufactured by AeroTech, but they are sold as part of the Quest product line. It is annoying that they are not all grouped together accordingly in the motor selection table. I went looking for the 24mm Q-jets and was baffled why they were not listed under Quest, until it eventually occurred to me to look under AeroTech.
I realize all this comes from thrustcurve.org but wonder if there's a way we can clean it up on our end to make it more straightforward for the user.
The text was updated successfully, but these errors were encountered:
The Manufacturer.java file seems to be loaded with heuristics for trying to figure out what different manufacturer names are really the same manufacturer. I took a look once, and decided I had better rabbit holes to explore...
For this issue the responsibility probably lies with thrustcurve.org, but if John can't fix it on his end then we should think about doing it on our end... even if we have to have an enumerated list of motors that get the manufacturer field change. Let's wait and see how that plays out.
18mm Q-jets are listed under manufacturer "Quest".
24mm Q-jets are listed under manufacturer "AeroTech".
All these motors are of course manufactured by AeroTech, but they are sold as part of the Quest product line. It is annoying that they are not all grouped together accordingly in the motor selection table. I went looking for the 24mm Q-jets and was baffled why they were not listed under Quest, until it eventually occurred to me to look under AeroTech.
I realize all this comes from thrustcurve.org but wonder if there's a way we can clean it up on our end to make it more straightforward for the user.
The text was updated successfully, but these errors were encountered: