1. 10 Apr, 2014 1 commit
  2. 08 Apr, 2014 1 commit
  3. 02 Apr, 2014 2 commits
  4. 01 Apr, 2014 3 commits
  5. 31 Mar, 2014 1 commit
  6. 20 Mar, 2014 1 commit
  7. 19 Mar, 2014 2 commits
  8. 18 Mar, 2014 1 commit
    • Ruth Sabariego's avatar
      Modifications linked to multi-harmonics... HBFE · fe1be9d8
      Ruth Sabariego authored
      Max num of harmonics limited to 20... originally 40 but it crashes without apparent reason. @cg: ann idea?
      Checking stuff... always useful :-)
      Slight modification of syntax for coherence:
      Old: MHJacNL[ dhdb ]{MH_SamplesJac, FreqOffSet}
      New: MHJacNL[ dhdb[{d a}] ]{MH_SamplesJac, FreqOffSet}
      
      fe1be9d8
  9. 14 Mar, 2014 3 commits
  10. 28 Feb, 2014 1 commit
  11. 20 Feb, 2014 1 commit
  12. 07 Feb, 2014 1 commit
  13. 25 Jan, 2014 1 commit
  14. 14 Jan, 2014 1 commit
  15. 06 Jan, 2014 1 commit
  16. 03 Dec, 2013 3 commits
    • Christophe Geuzaine's avatar
      Changed behaviour of DefineConstant & co for better symmetry between GetDP/Gmsh · 7616c416
      Christophe Geuzaine authored
      and Python onelab clients.
      
      WARNING WARNING WARNING: This is a major change -- all our onelab-enabled .geo
      and .pro files will need to be (slightly...) modified.
      
      What's new:
      
      1. The name of a onelab variable (in the onelab database) is no more constructed
         from the name of the corresponding GetDP/Gmsh variable. One now needs to
         specify the onelab name explicitely, using the "Name" attribute. The "Name"
         is the actual name of the parameter in the onelab database, i.e., it also
         includes the path.
         
         This makes the "Path" attribute obsolete (it has no effect anymore). The
         "Legend" attribute can still be used (and it can be useful in edge cases,
         e.g. when you want a "/" in the name of a onelab paramater), but in most
         cases it's not necessary.
      
      2. When a DefineConstant[] & co is used and no Name is given
         (e.g. DefineConstant[a=2]), no onelab parameter is created. This allows to
         provide default values to internal parameters without polluting the database.
      
      Why did we change?
      
      1. The new syntax matches what we do in Python, where specifying a name is
         mandatory (there's no way around this in Python, as onelab cannot guess the
         name of a Python variable to which a onelab parameter value will be assigned).
         
         The change will prevent common mistakes where two parameters with the same
         label actually correspond to 2 different onelab parameters, due to a change
         in local getdp/gmsh variable name (which would change the onelab name
         automatically)
      
      2. The new syntax allows to nicely decouple onelab parameters from internal
         variables with default values, that we don't want in the onelab database.
      
      
      7616c416
    • Alexandre Vion's avatar
      Fix broadcastFields · ec22c172
      Alexandre Vion authored
      ec22c172
    • Christophe Geuzaine's avatar
  17. 29 Nov, 2013 2 commits
  18. 26 Nov, 2013 1 commit
  19. 25 Nov, 2013 1 commit
  20. 31 Oct, 2013 2 commits
  21. 21 Oct, 2013 1 commit
  22. 16 Oct, 2013 1 commit
  23. 02 Oct, 2013 1 commit
  24. 26 Sep, 2013 1 commit
  25. 24 Sep, 2013 1 commit
  26. 23 Sep, 2013 1 commit
  27. 02 Sep, 2013 1 commit
  28. 01 Sep, 2013 1 commit
  29. 12 Jul, 2013 1 commit
  30. 04 Jul, 2013 1 commit