Read and display Core 17 (Zeta) .json files

[jcoffland]

Trac	Data
Ticket	980
Reported by	@Jesse-V
Status	closed
Component	FAHClient
Priority	4
Milestone	v7.3.11
Keywords	core 17, zeta, .tpr, .xyz, viewerFrameX.json

There have been multiple reports by the Core 17 testers on IRC of FAHViewer not displaying the WUs processed by FahCore 17, currently in alpha testing. Pin in particular reports that in the Current Work Unit section, FahCore shows "FahCore: UNKNOWN_ENUM 0x17". In the Status section, Connection is set to "Connected" and the Protein field is set to "Loading", but the protein does not display and all that the user sees is the map. Perhaps FAHViewer should handle the situation in a much more descriptive way, but the problem may be with the core.

Apparently there are no .tpr or .xyz files in the work folder, but there is a viewerFrameX.json file. The core ought to produce these files for FAHViewer. This incompatibility is not critical now, but will become much more obvious once FahCore 17 becomes commonplace.

[jcoffland]

Comment by @Jesse-V Replying to [ticket:980 Jesse_V]:

in the Current Work Unit section, FahCore shows I meant FAHViewer, not FahCore. My mistake.

[jcoffland]

Comment by @jcoffland This is a known issue. FAHViewer needs to be modified to read the .json files Zeta core writes.

[jcoffland]

Comment by @Jesse-V "FAHClient will read core 0x17 trajectory files in the next release." -jcoffland https://github.com/Jesse-V/Folding-Atomata/issues/13#issuecomment-22129483

[jcoffland]

Comment by @Jesse-V Can this be put into 7.3.11 or similar then?

I am looking forward to FAHClient's capability to do this. Also, if you move the bond-length filter from FAHViewer to FAHClient, I can fix the protein split glitch in my viewer and you can port the fix if you like.

[jcoffland]

Comment by @jcoffland Fixed in v7.3.11