Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

remote api for trajectory not working in client 7.6.13 #1536

Open
ChristianVirtual opened this issue Jul 7, 2020 · 3 comments
Open

remote api for trajectory not working in client 7.6.13 #1536

ChristianVirtual opened this issue Jul 7, 2020 · 3 comments
Labels
1.Type - Defect Reported issue is a defect. 3.Component - API Reported issue relates to 3rd party APIs. 4.OS - All Reported issue occurs on all supported OS platforms.

Comments

@ChristianVirtual
Copy link

Your Environment

  • F@H Software version: 7.6.13
  • Operating System: CentOS 8
  • Browser: n/a

Expected Behavior

Normally when using the API to get the trajectory relevant for viewer the command "trajectory " will be executed and the information about contained atoms, their bonds and coordinated are provided.


Current Behavior

The network connection get terminated (easy to be reproduced via telnet)

the json files in the working directory are created. Both the top-version as well as the frames. But the information is not routed through the client to the receiving site of the connection. M


Possible Solution (Optional)

No idea as the internal structure of the code is not known. Maybe the parsing of the slot argument fail. Maybe authorization issue when the FAHClient try to read the JSON files. No information in the log file


Steps To Reproduce

  1. call telnet localhost 36330
  2. queue-info to get a slot
  3. trajectory

Context

The protein viewer can't how any data any longer (neither default viewer nor 3rd party like in my case


@ChristianVirtual
Copy link
Author

Some more information here:
https://foldingforum.org/viewtopic.php?f=108&t=35745
When scheduled via periodic processing that data stream is send ; but single execution disconnect the client

@bradchristie
Copy link

Workaround/solution:
If you first enter the 'hello' command then the trajectory commands work.

@ChristianVirtual
Copy link
Author

ok; that is valid for 7.6.13; "hello" as first command would work and get me the trajectory
problem: that command don't exists in 7.5.1

> hello

ERROR: unknown command or variable 'hello'

@PantherX PantherX added 1.Type - Defect Reported issue is a defect. 3.Component - API Reported issue relates to 3rd party APIs. 4.OS - All Reported issue occurs on all supported OS platforms. labels Aug 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.Type - Defect Reported issue is a defect. 3.Component - API Reported issue relates to 3rd party APIs. 4.OS - All Reported issue occurs on all supported OS platforms.
Projects
None yet
Development

No branches or pull requests

3 participants