Differenze

Queste sono le differenze tra la revisione selezionata e la versione attuale della pagina.

--- gvb [2014/01/31 20:35] – 1.3 pietro
+++ gvb [2014/11/14 13:42] (versione attuale) – typo pietro
@@ Linea 1: / Linea 1: @@
-{{:gvb:gvb-1.3.tar.gz|Click here to download version 1.3 of gvb.}}
+{{:gvb:gvb-1.4.tar.gz|Click here to download version 1.4 of gvb.}}
-{{:gvb:gvb_1.3-1_all.deb|Click here for the Debian/Ubuntu package.}}
+{{:gvb:gvb_1.4-1_all.deb|Click here for the Debian/Ubuntu package.}}
 ==== What is GVB? ====
@@ Linea 12: / Linea 13: @@
-==== Where can I get GVB? ====
+==== Where can I get it? ====
-On Launchpad.
-You can get last GVB release here: https://launchpad.net/gvb/trunk/
+You can always find the last version at the address http://pietrobattiston.it/gvb
 //OR// you can get last development GVB with git:
@@ Linea 35: / Linea 34: @@
   * **But Python is slow and GVB needs a lot of calculation!**
-GVB relies on scipy for the calculation, and scipy relies on Lapack and Blas, and Lapack and Blas **aren't** slow (and they are compiled C or Fortran, not Python). So don't worry. If GVB is slow, it's because the calculations to do //really// are hard (or eventually because I did a mistake). To spot the difference between "Python code" and "Python relying on scipy", see the performance improvements between "naif" (pure Python) and "matrix naif" (scipy) methods.
+GVB relies on scipy for the calculation, and scipy relies on Lapack and Blas, and Lapack and Blas **aren't** slow (and they are compiled C or Fortran, not Python). So don't worry. If GVB is slow, it's because the calculations to do //really// are hard (or eventually because I did a mistake). To spot the difference between "Python code" and "Python relying on scipy", see the performance improvements between "naif" (pure Python) and "matrix" (scipy) methods.
   * **I need a start position not provided / I need a rectangular (non square) grid / I need to set start speeds, not only positions.**
@@ Linea 41: / Linea 40: @@
   * **I dumped a lot of png frames. How do I create a movie with them?**
-If you have ffmpeg installed, move to the directory where the pngs are and (supposing there are only //those// png) give the following command:
+If you have avconv installed, move to the directory where the pngs are and (supposing there are only //those// png) give the following command:
-  ffmpeg -i %08d.png video.mp4
+  avconv -i %08d.png video.mp4
@@ Linea 59: / Linea 58: @@
   - The ability to apply masks (select a set of points in the 2D grid that are fixed) would allow observation of interesting (and, for example, more regular) vibrations.
   - The possibility to highlight nodes (points that do not move) would be nice.
-  - Some dampering could be allowed
+  - Some dampening could be allowed
   - Elasticity and mass could vary from point to point
   - At the moment, the editor allows the creation of nearly every conceivable 1D start position. Instead, something better could be implemented to create 2D start positions.
   - There should be the possibility to set rectangular (non square) grids.
   - Creation of start position and drawings could be optimized a lot.
-  - When dumping to png, plotting to screen should still be enabled.
+  - <del>When dumping to png, plotting to screen should still be enabled.</del>
   - The ability to output a .wav file to make you //hear// the vibration of a given point would be nice.
   - In the "eig" method, the operator matrix is very sparse. This could make the process of calculating its eigenvalues and eigenvectors much faster, but I'm not really sure and scipy released version still doesn't implement anything useful (as of March 2008)