protein viewer for 7.6.13 not working, no data via API

[ChristianVirtual]

With the FAHClient 7.6.13 (CentOS 8 in my case) I can't get the trajectory information relevant for default protein viewer or via 3rd party API into my mobile application.
It works under 7.5.1

When try to replicate via simple TELNET command I get simply disconnected

Code: Select all

Welcome to the FAHClient command server.
> simulation-info 01

PyON 1 simulation-info
{"user": "ChristianVirtual", "team": "33", "project": 16804, "run": 25, "clone": 360, "gen": 75, "core_type": 167, "core": "GRO_A7", "total_iterations": 100, "iterations_done": 64, "energy": 0, "temperature": 0, "start_time": "2020-07-07T12:16:38Z", "timeout": 0, "deadline": 1594487078, "eta": 4464, "progress": 0.6428, "slot": 1}
---
> trajectory 01
Connection closed by foreign host.

json files for viewer are written in the working folder.

GitHub issue raised https://github.com/FoldingAtHome/fah-issues/issues/1536

[bruce]

Hmmm. FAHClient 7.6.13 for windows does support viewing the active WUs on each GPU. I don't know if the stand-alone FAHViewer can do that as I'm using the FAHViewer that's activated from FAHControl.

[ChristianVirtual]

Hmmm. FAHClient 7.6.13 for windows does support viewing the active WUs on each GPU. I don't know if the stand-alone FAHViewer can do that as I'm using the FAHViewer that's activated from FAHControl.

Could you please try the telnet way against your Windows version ?

[Brad_C]

FAHViewer gets the trajectory using the updates command, as in

Code: Select all

updates add 4 5 $(trajectory 1)

which seems to work (more or less). I do get your result with the bare trajectory command, that is the client closes the connection.

[ChristianVirtual]

FAHViewer gets the trajectory using the updates command, as in

Code: Select all

updates add 4 5 $(trajectory 1)

which seems to work (more or less). I do get your result with the bare trajectory command, that is the client closes the connection.

Interesting, can try that later. But having the trajectory periodically downloaded from the client is not really working for a mobile user in mind. Would be only ok in wifi but even then I worry to overload the fachclient with serving that data instead of folding some proteins. But yes, for further investigations that’s for the hint.

Update: ok, was too curious and it actually works also with the Linux client 7.6.13 when scheduled in this way via periodical job. That should be hopefully useful for the investigation in the code.

[Brad_C]

Actually it only sends the trajectory when it has new data, which is 100x per WU. The increment in the updates command just tells it how often to check.

[Brad_C]

I experimented some more and found another workaround / solution: if you first enter the 'hello' command then the trajectory commands work. I updated the issue in GitHub.

[ChristianVirtual]

Thank; tried that and it works for 7.6.13. This command seems new as I can't find it in 7.5.1.
Wonder why it come in ...