search

beast-dev / tracer

Posterior summarisation in Bayesian phylogenetics
https://beast.community/tracer
GNU Lesser General Public License v2.1
52 stars 17 forks source link

cannot select multiple parameters in 1.7 #148

Closed wbsimey closed 6 years ago

wbsimey commented 6 years ago

Looking at a BEAST2.5 log file for a relaxed clock FBD analysis in Tracer 1.7, I am unable to view multiple parameters as I can in v1.6. I have attached screenshot of same log files in v1.6 and v1.7

on Win10 64-bit, Java 10. screenshot 2018-06-12 11 11 18 screenshot 2018-06-12 11 10 44

GuyBaele commented 6 years ago

This was indeed an issue when we first released the Tracer 1.7 files. Can you please try downloading Tracer 1.7 again to check if this is still an issue?

wbsimey commented 6 years ago

I downloaded Tracer1.7 again from https://github.com/beast-dev/tracer/releases/tag/v1.7. and I see the same behavior for all BEAST2 log files; I cannot visualize multiple traces simultaneously, but in v1.6 I can.

drelo commented 6 years ago

Sorry to post here but I didn't want to duplicate a question, I am having the same issue

I just downloaded the newest Tracer

I currently have 

java -version
openjdk version "1.8.0_171"
OpenJDK Runtime Environment (build 1.8.0_171-8u171-b11-0ubuntu0.16.04.1-b11)
OpenJDK 64-Bit Server VM (build 25.171-b11, mixed mode)
Ubuntu 16.04

I attached the log file. I just opened those 2 traces with Tracer 1.6 and it worked fine.

Thanks for your help

tracer17.log

walterxie commented 6 years ago

@drelo @wbsimey Thank you to report the bug. I just double-checked again by actually running primate-mtDNA XML in BEAST 2.5.0 and loaded the log to Tracer 1.7. I still could not replicate the issue in the Mac version, but I successfully replicated it when I ran the Linux version of Tracer 1.7 in Mac. I did not find a PC here, but I suspected it would be the same error in Windows version.

We are working to solve this at the moment.

walterxie commented 6 years ago

I do not think the current Java code was causing this issue after my investigation. This issue can be replicated by tracer.jar alone in the previous released Linux version. I tested the Linux release by myself using the latest development version, it was working well.

I presume the Linux version and Windows version might be interrupted during the release process, so that a new release would solve this problem (if assuming the Windows version had the same problem with Linux version).

wbsimey commented 6 years ago

I downloaded Tracer 1.7.1 for Windows and Linux (Ubuntu 16.04) and the issue has been resolved for both platforms. thank you.