nleroy917
commented
3 years ago Hey! Thanks for pointing this out. I found this as an error when dockerizing the app a bit ago - thought I fixed it. But Travis-CI build failed and thus it never got deployed! I think it's because the API itself was broken and the build requires the API to function.
Anyways - it should be fixed now? I made it so that serverside all sequences are converted to lowercase.
whitman103
The example program is outdated at the moment; one must replace the "optipyzer" objects with the "results" api object if you want it to run. But more importantly, the server bounces requests for optimization with a 400 code, with the following error message.
{"error":{"code":400,"message":"Invalid base found in query: c"},"invalid_base":"c","seq":"ctg"}
I'm not sure what's going on. I checked the source for the server side script and all it has is a check if the bases are in "actg", which all of my sequences pass elementwise. I would love to use this program in my work, but at the moment, it seems like it is suffering some crosstalk. Please let me know if I can help get this up and running again, or if I have fundamentally messed up the procedure for an optimization. The code I'm attempting to run is just the example code from the Dev site, but with the "optipyzer" calls replaced with the api calls, since there is no method on optipyzer called search or optimize.