Community driven support forum for Folding@home
https://foldingforum.org/
That was the bug I was motivated to fix, but as I said in this comment it looks like the bug was fixed last year, after the 7.5.1 release.Quantize wrote: Hi! I'm not yet completely sure what you're referring to here. What did you go in to fix?
In the last release the viewer only works on demo mode.
Yep, given the development history of the project this makes sense. It's just a case of now triaging the influx of users and their requests, and pointing them in the right direction. Fortunately GitHub has added tooling that improves the UX around this (fah-issues PR, fah-viewer PR).bruce wrote:The same guy has to priorities all the bugs, compare with his available time, and pick the most important one(s).
You're up.rixon wrote:Meerteen, if you do that, I'll send you some (detailed/constructive) bug reports!
Looking at that comment: It's funny how things can be left unfixed for years and years, everyone complaining and begging, zero dev activity whatsoever.str4d wrote:That was the bug I was motivated to fix, but as I said in this comment it looks like the bug was fixed last year, after the 7.5.1 release.
Yes that makes total sense but it doesn't seem to fully answer the question:bruce wrote:The same guy has to priorities all the bugs, compare with his available time, and pick the most important one(s).
True, but the data it's showing is incorrect. @Quantize, you may want to correct me if I'm wrong, but Core_22 seems to be putting broken data into the json files which the viewer uses for its trajectory calculations. My best bet is that the cloud of purple atoms forming a cube consist of these "unknown" atoms with a question mark. Below is a comparison of the working Gromacs A7 data and the broken Core_22 data.dfgirl12 wrote:There was a workaround mentioned recently: by using the previous viewer executable (and a required dll) file with the current FAH v7.5.1 installation for viewing Core_22 on Windows
Code: Select all
"units": "ANGSTROM", "atoms": [
["N", 0.0017, 0.155, 14.01, 7, "GLU"],
["H1", 0.2391, 0.13, 1.008, 1, "GLU"],
["H2", 0.2391, 0.13, 1.008, 1, "GLU"],
["H3", 0.2391, 0.13, 1.008, 1, "GLU"],
["CA", 0.0588, 0.17, 12.01, 6, "GLU"],
["HA", 0.1202, 0.12, 1.008, 1, "GLU"],
["CB", 0.0909, 0.17, 12.01, 6, "GLU"],
["HB1", -0.0232, 0.12, 1.008, 1, "GLU"],
["HB2", -0.0232, 0.12, 1.008, 1, "GLU"],
["CG", -0.0236, 0.17, 12.01, 6, "GLU"],
["HG1", -0.0315, 0.12, 1.008, 1, "GLU"]Code: Select all
"units": "A","atoms": [
["?",0,0,0,3],
["C",0,0,0,6],
["O",0,0,0,8],
["?",0,0,0,4],
["?",0,0,0,4],
["?",0,0,0,4],
["?",0,0,0,11],
["?",0,0,0,9],
["C",0,0,0,6],
["O",0,0,0,8],
["?",0,0,0,6],
["S",0,0,0,16]
I think you are right. Bruce also said in another thread that they are water surrounding the protein. Now that I looked closer, they are in groups of three atoms, most likely H2O just like you said. They should not be visible at all.dfgirl12 wrote:My guess without looking into it much: I think the layout of the atoms is correct, but the colors and the sizes of the purple atoms is not correct (probably due to the '?' in the json).
I'm pretty sure the cube of atoms is a lot of water molecules (like the protein is moving in moisture/water, like in your lungs).
So those should be like a medium sized red atom with a pair of smaller light gray atoms, instead of purple and all the same size.
I compiled your fork and unfortunately by no means did it resolve the issue.Jorgeminator wrote: I forked the repo and made a quick and dirty change to the code to make the purple particles fully transparent, but I'm unable to set up a compiling environment. If someone would like to try compiling it the repo is here: https://github.com/Jorgeminator/fah-viewer.
The protein will be missing its hydrogen atoms, but it should at least look a lot better than before, while we wait for a proper fix.
Most times the viewer tries to open the GPU slot and I have to restart it to view the CPU project. Trying to switch slots inside the viewer works now and then.Quantize wrote:Just now I have committed a pull request on GitHub:
https://github.com/FoldingAtHome/fah-viewer/pull/19
Everyone who wants to test please do so now:
http://meertronix.com/FAHViewer.exe
Re-reading this thread, I misread that you were talking about the viewer. I had bug reports for the client. That said, great work with this so far! I'll give it a try some day when I have access to a Windows system.Quantize wrote:You're up.rixon wrote:Meerteen, if you do that, I'll send you some (detailed/constructive) bug reports!
Most people don't know how to change slots. So what's relevant for this promo is: have you waited long enough?Jorgeminator wrote: Most times the viewer tries to open the GPU slot and I have to restart it to view the CPU project. Trying to switch slots inside the viewer works now and then.