yade-dev team mailing list archive

[Bruno Chareyre <1160501@xxxxxxxxxxxxxxxxxx>]

You may look for a way to "flush" to the file since it looks like a buffer problem.
I would not call this a bug in Yade itself, more an unfortunate combination of different things.

-- 
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1160501

Title:
  --performance output disrupted by /proc/cpuinfo

Status in Yet Another Dynamic Engine:
  New

Bug description:
  Hi, I think there is a bug in the /examples/test/performance/checkPerf.py script.
  I'm using the following script to iterate over a given number of cpu cores with the --performance:
  <code>
  #!/bin/bash
  #start script via "bash yadeBuiltInPerformanceTest.sh MIN MAX >> ~/yadeBuiltInPerformance.log" starten
  # MIN: number of cores to start with
  # MAX: maximum number of cores to test
  echo "Beginning Yade Performance Test"

  BEGIN=$1
  END=$2

  for (( I=$BEGIN; $I <= $END; I++ )); do
  	DATE=$(date)
  	echo $I" core(s); beginning: "$DATE
  	yade-daily -j$I --performance >> ~/yadelogBuiltInPerformance_j$I.log
  done

  DATE=$(date)
  echo "Ende: "$DATE
  </code>

  But if I look at the yadelogBuiltInPerformance_j$I.log files, my output is messed up.
  Instead of showing up at the very end of the file, the CPU info produced by this line of code in checkPerf.py
  <code>print "CPU info", os.system('cat /proc/cpuinfo')</code>
  disruptes the performance output. I.e. from line 200 to 1031 you'll find CPU info.
  I'm using Yade 3+3463+44~precise1 but the source code I looked at was the latest one.

  Thanks, Eugen

To manage notifications about this bug go to:
https://bugs.launchpad.net/yade/+bug/1160501/+subscriptions