Yade

fixing examples and scripts

Asked by Christian Jakob

Starting with the examples folder i detected the first error in rotating-cyclinder.py

Welcome to Yade bzr3041
TCP python prompt on localhost:9001, auth cookie `yuasse'
XMLRPC info provider on http://localhost:21001
Running script rotating-cylinder.py
Traceback (most recent call last):
  File "/home/me/YADE/YADE3041/bin/yade-bzr3041", line 182, in runScriptexecfile(script,globals())
  File "rotating-cylinder.py", line 36, in <module>cylIds=O.bodies.append(pack.gtsSurface2Facets(cyl.faces()))
  File "/home/me/YADE/YADE3041/lib/yade-bzr3041/py/yade/pack.py", line 179, in gtsSurface2Facets
    return [utils.facet([v.coords() for v in face.vertices()],**kw) for face in surf.faces()]
AttributeError: 'tuple' object has no attribute 'faces'

Whats the problem here?

Question information

Language:
English Edit question
Status:
Answered
For:
Yade Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Anton Gladky (gladky-anton) said : 		#1

I will take a look.

Anton

Revision history for this message
Bruno Chareyre (bruno-chareyre) said : 		#2

I suggest to copy/paste [script name , error message] in a text file that can be left in the "not working folder". Or maybe paste the eroor message in a comment at the begining of the script itself.
If you start asking questions for each broken scripts it will take a lot of time. We dont want to kill you. ;)

Revision history for this message
Christian Jakob (jakob-ifgt) said : 		#3

I think there should be a more clear structure in scripts and examples.

I would suggest, that we copy ALL model examples into examples folder. Any other scripts like default-test.py, erskine3.py and so on should stay in the script folder.

Is that ok, or are there complications, when we do so?

Regards,

Christian

Revision history for this message
Bruno Chareyre (bruno-chareyre) said : 		#4

It is perfect Christian, but there are a few exceptions which are not
examples:
- scripts/test/checks/ must not move. It contains scripts used by the
build robot to check if results are correct after each commit. They are
really "tests" and not examples.
- similarly (but less importantly), a few other benchmark and speed
tests could stay in test/: scripts/test/triax-perf/triax-perf.py,
scripts/test/collider-perf/, compare-identical.py,
scripts/test/law-test.py, etc.
- also a few scripts used only for development: e.g.
scripts/test/dispatcher-torture.py,
scripts/test/serialization-benchmark.py,

Could you please move at least /checks back to its original position,
because currently the built system returns error due to that.

Bruno

Revision history for this message
Anton Gladky (gladky-anton) said : 		#5

> Could you please move at least /checks  back to its original position,
> because currently the built system returns error due to that.

I fixed that. Please, do not commit for the moment, I am moving a repo....

Anton

Can you help with this problem?

Provide an answer of your own, or ask Christian Jakob for more information if necessary.

To post a message you must log in.