Just in case it helps, with the latest version (2.0.1) I still see the same odd output with the test dataset. But with my own data (much larger, and just running on a small laptop for now) I see very nicely formatted output with expected times to completion that update (e.g. pasted below).
Cheers,
Rob
Mellisuga:DiscoSNP++-2.0.1-Source robertlanfear$ ./run_discoSnp++.sh -r "data_sample/M1a_index2_CGATGTAT_L003_R1_001.fastq.gz data_sample/M7a_index7_CAGATCAT_L006_R1_001.fastq.gz" -T
use read set: data_sample/M1a_index2_CGATGTAT_L003_R1_001.fastq.gz data_sample/M7a_index7_CAGATCAT_L006_R1_001.fastq.gz
Binaries in /Volumes/Lanfear_data/DiscoSNP++-2.0.1-Source/build/
Running discoSnp++ 1.0.0, in directory /Volumes/Lanfear_data/DiscoSNP++-2.0.1-Source with following parameters:
read_sets=data_sample/M1a_index2_CGATGTAT_L003_R1_001.fastq.gz data_sample/M7a_index7_CAGATCAT_L006_R1_001.fastq.gz
prefix=discoRes_k_31_c_4
c=4
C=2147483647
k=31
b=0
d=1
D=0
starting date=Fri 23 Jan 2015 14:14:03 AEDT
############################################################
#################### GRAPH CREATION #######################
############################################################
/Volumes/Lanfear_data/DiscoSNP++-2.0.1-Source/build//ext/gatb-core/bin/dbgh5 -in data_sample/M1a_index2_CGATGTAT_L003_R1_001.fastq.gz,data_sample/M7a_index7_CAGATCAT_L006_R1_001.fastq.gz -out discoRes_k_31_c_4 -kmer-size 31 -abundance-min 4 -abundance-max 2147483647 -solidity-kind max
[DSK: Collecting stats on read sample ] 100 % elapsed: 0 min 10 sec estimated remaining: 0 min 0 sec cpu: 180.1 % mem: [ 18, 18, 0] MB
[DSK: Pass 1/1, Step 2: counting kmers ] 100 % elapsed: 13 min 12 sec estimated remaining: 0 min 0 sec cpu: 146.2 % mem: [ 74, 1586, 0] MB
[Bloom: read solid kmers ] 100 % elapsed: 2 min 10 sec estimated remaining: 0 min 0 sec cpu: 93.7 % mem: [ 278, 278, 0] MB
[Debloom: build extension ] 7.14 % elapsed: 0 min 28 sec estimated remaining: 6 min 0 sec cpu: 143.8 % mem: [ 384, 384, 0] MB