yade-dev team mailing list archive

[Bruno Chareyre <bruno.chareyre@xxxxxxxxxxxxxxx>]

I did not mention it explicitly but I think improving "How to ask" 
includes explaining "how to" avoid extra files in typical cases.
Otherwise it would just discourage people from asking.

I tried to address one possible situation in [1] (avoid saving 
simulation in one script then reloading in another) and this can be 
linked in the page.
For files with coordinates and radii I think the fix is to replace by 
makeCloud or hardcode (a limited number of) positions in the script.
The same works for clump members.

To summarize:
* reloading scenes in multi-script context -> can be avoided with [1]
* position files -> makeCloud(seed=..) or hardcode
* clumps -> same as above
* stl mesh -> solutionless (really?)

Do you see other situations? Other kind of solutions?

B

[1] 
https://github.com/yade/trunk/blob/master/examples/simple-scene/save-then-reload.py


On 06/29/2018 03:02 PM, Jan Stránský wrote:
> I agree too,
>
> I would add a note that the problem might be solved by the process of 
> creating MWE..
>
> > Jan is probably too kind for that ;-)
>
> well, it annoys me more and more, too, so I will at least answer with 
> delay :-)
>
> cheers
> Jan
>
>
> 2018-06-29 14:09 GMT+02:00 Jerome Duriez <jerome.duriez@xxxxxxxxx 
> <mailto:jerome.duriez@xxxxxxxxx>>:
>
>     Hi all,
>
>     I agree Bruno with your description of the annoying extra efforts
>     that are required to try to help with such questions. As far as I
>     am concerned, I do not try downloading things and help in these
>     cases...
>
>     My first suggestion would be to further push users to propose (for
>     real !!!) minimal working examples, but I think the only efficient
>     way to do this would be not answering many of the questions and
>     Jan is probably too kind for that ;-)
>
>     Anyway, I think myself it sounds realistic to ask users to avoid
>     extra files in their MWE, and do not have any other suggestions..
>
>
>     Jérôme
>
>     ------
>     Chargé de Recherche / Research Associate
>     Irstea, RECOVER
>     3275 route de Cezanne – CS 40061 13182 Aix-en-Provence Cedex 5 FRANCE
>     +33 (0)4 42 66 99 21
>
>     On 29/06/2018 12:33, Bruno Chareyre wrote:
> >     Hi Yade devs,
> >     When I try to save a few minutes to answer some questions I very
> >     ofen find myself clicking here and there to access a pastebin
> >     file which is needed for a given script to run. The
> >     [pastebin|whateve|...] file can't downloaded directly in many
> >     cases. I then have to copy - which can imply substantial
> >     scrooling, paste, save in the right place, go back to terminal, run.
> >     And sometimes it is just to find that the script itself will not
> >     run, even with the proper data file.
> >
> >     If you want to see this cycle in action you can have a look at
> >     [1] where four posts more or less are just to sort out the data
> >     files, implying than Jan had to repeatedly reproduce the cycle
> >     mentioned above. Worth mentioning, post #11 introduces additional
> >     links for the same filenames (same content? who knows?), so it is
> >     absolutely unclear now what someone is supposed to download to
> >     simply test a script and help someone else.
> >
> >     I was thinking that we could go deeper in the MWE part of
> >     https://yade-dem.org/wiki/Howtoask
> >     <https://yade-dem.org/wiki/Howtoask>, to push questionners toward
> >     self-contained scripts.
> >     An issue is that even among the devs I see this tendency to
> >     manipulate data files.
> >     There are a few cases where it can't be avoided, like stl mesh.
> >     But in most cases I think a data file is not needed MWE,
> >     specifically for sphere positions and clump data (which are just
> >     positions).
> >     What do you think? Does it sound realistic to ask users to avoid
> >     extra files in MWEs?
> >
> >     We could even provide a way to make sure that no "file not found"
> >     will occur. For instance, every mwe.py should be compatible with:
> >     mkdir MWE
> >     cp mwe.py ./MWE/mweTest.py
> >     cd MWE
> >     /path/to/yade mweTest.py
> >     rm -rf ../MWE
> >
> >     Other suggestions?
> >
> >     Bruno
> >
> >     [1] https://answers.launchpad.net/yade/+question/670501
> >     <https://answers.launchpad.net/yade/+question/670501>
>
>
>     _______________________________________________
>     Mailing list: https://launchpad.net/~yade-dev
>     <https://launchpad.net/%7Eyade-dev>
>     Post to     : yade-dev@xxxxxxxxxxxxxxxxxxx
>     <mailto:yade-dev@xxxxxxxxxxxxxxxxxxx>
>     Unsubscribe : https://launchpad.net/~yade-dev
>     <https://launchpad.net/%7Eyade-dev>
>     More help   : https://help.launchpad.net/ListHelp
>     <https://help.launchpad.net/ListHelp>
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~yade-dev
> Post to     : yade-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~yade-dev
> More help   : https://help.launchpad.net/ListHelp