thegooglecodearchive / sfepy

Automatically exported from code.google.com/p/sfepy
0 stars 0 forks source link

sfepy-release-2010.1\gen does not exist #108

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Hi, I am still a beginner with python, and this is my first attempt at
adding a module to those I got with EPD, so I am probably doing something
obviously wrong.  I'm using Windows XP.  I downloaded
http://sfepy.googlecode.com/files/sfepy-release-2010.1.tgz and unzipped it
to my C:\ directory.  Then I ran cmd and went to C:\sfepy-release-2010.1
and ran "python setup.py install"  A ton of text is generated the last line
of which is "error: file 'C:\sfepy-release-2010.1\gen' does not exist"  I
look in my Python directory and I don't find sfepy so this error must have
interrupted the whole installation.  What am I doing wrong?  What do I need
to do get sfepy to install?

Original issue reported on code.google.com by willsha...@gmail.com on 23 Mar 2010 at 7:38

GoogleCodeExporter commented 9 years ago
I looked around some more and discovered that that gen and genDocs.py are 
absent from
the main directory of sfepy-release-2010.1.tgz but are in the top directory of
sfepy-release-2009.4.tgz.  I copied the files from 2009.4 into 2010.1 and the
installation seemed to complete itself.  Maybe these files should be added back 
in?

I have a sfepy directory in Lib/site-packages now.  When I run runTests.py now, 
I get
44 failed tests out of 51.  I guess I still have some installation problems?  
I'm not
even sure where to begin with so many failures.

Original comment by willsha...@gmail.com on 23 Mar 2010 at 8:42

GoogleCodeExporter commented 9 years ago
Hi Will,

Thanks for trying out SfePy! Sorry that you are encountering so many errors. 
Which
version of EPD are you using?

I believe the gen and genDocs.py scripts are legacy scripts that were removed 
from
version 2010.1, but apparently weren't removed from the install script. 
Actually, you
should be able to run SfePy without installation in the source directory where 
you
unzipped SfePy. Could you try:

python setup.py build_ext --inplace
python runTests.py

I will try downloading EPD and installing from the 2010.1 release to see if I
experience similar issues.

Also, if there are any areas of the documentation that are not clear or could 
use
improvement, please feel free to ask for clarifications or suggest improvements.

Thanks!
Logan

Original comment by logan.so...@gmail.com on 23 Mar 2010 at 9:00

GoogleCodeExporter commented 9 years ago
Thanks for the reply, Logan.

Your suggestions seem to work.  I don't get an error when I do python setup.py
build_ext --inplace and when I call python runTests.py I see many tests passed 
(and
none failed).  Python seems to hang up on test_input_linear_elastic_mM.py.  
It's been
stuck on that one for half an hour.  Should it take a long time to complete 
this test?

Also, what is the best way to work sfepy?  Should I try rerunning the 
installation
with gen and genDocs.py commented out of the install script?

I have EPD 6.1.

Thanks!

Will

Original comment by willsha...@gmail.com on 23 Mar 2010 at 9:47

GoogleCodeExporter commented 9 years ago
Ok, I tried installing EPD 6.1 on a Windows machine and am seeing the same 
errors
with the installation as you were. You are correct; the lines with gen and 
genDocs.py
should be removed from setup.py. 

I notice the issue with tests_input_linear_elastic_mM.py also. This seems to be 
a
convergence error with that particular test. For reference, on Linux, the 
entire test
suite runs in a few minutes. There may also be an issue with
test_elasticity_small_strain.py. Probably we'll have to investigate these 
further.

For the installation, it seems to be an issue with the paths on Windows. 
Actually, it
looks like the data files the tests need (meshes, etc.) are installed to
"C:\share\sfepy", while SfePy is looking for them in
"C:\Python26\Lib\site-packages\sfepy". For now, you can just copy the contents 
of the
first directory into the second, but we should fix the install script to handle 
this
case.

Actually, I usually don't install, just run "python setup.py build_ext 
--inplace" in
the source directory and run everything from there. But you are right, the 
install
should still work correctly. I think most of us are using Linux, so it's good 
to get
some Windows testers/devs. ;)

To get started, you can look at the tutorial on solving Poisson's equation:
<http://docs.sfepy.org/doc/tutorial.html>. I guess you need to prepend python to
those command lines on Windows, e.g., "./simple.py 
examples/diffusion/poisson.py" ->
"python ./simple.py examples/diffusion/poisson.py". You can run everything from 
the
source dir.

HTH, feel free to ask anything else!

Logan

Summary:
1. Issues with setup.py
    a. remove 'gen' and 'genDocs.py' from main_scripts
    b. data directory paths on Windows
2. Performance issues on Windows with:
    a. tests_input_linear_elastic_mM.py
    b. test_elasticity_small_strain.py

Original comment by logan.so...@gmail.com on 23 Mar 2010 at 10:31

GoogleCodeExporter commented 9 years ago
Hi Will,

sorry for your inconvenience. I noticed those issues just after the 2010.1 
release.
Like Logan, I use the code inplace...

The bugs should be fixed in the git repository though. Could you try the latest 
git
version tarball [1] and report any further problems here? Thanks!

[1] http://git.sympy.org/?p=sfepy.git;a=snapshot;h=HEAD;sf=tgz

Original comment by robert.c...@gmail.com on 29 Mar 2010 at 8:19

GoogleCodeExporter commented 9 years ago
Hi Robert,

I tried the latest git version.  I was able to get through all of runTests.py 
without
hanging up anywhere.  I got a bunch of warnings about deprecations and some 
syntax
things, but nothing that stopped the tests.

I tried installing the latest git version, too.  I still had to remove gen and
genDocs.py from main_scripts for it to work.

Also, I have some really basic questions about using sfepy.  Where is the 
appropriate
place to ask them?  They are not issues with sfepy but with my understanding of 
to
use it.

Original comment by willsha...@gmail.com on 2 Apr 2010 at 7:24

GoogleCodeExporter commented 9 years ago
Yes, the warnings appear beacause scipy progresses quite fast and we want to 
support
several common versions. You can safely ignore them.

The best place for asking questions is our mailing list [1] (there is a link 
here at
the main page too). I am usually also avalaible at #sfepy irc channel, when I 
am at
the lab...

In case you have problems with joining the list, send me your e-mail address to
robert cimrman at gmail com and I will add you manually. 

[1] http://groups.google.com/group/sfepy-devel

Original comment by robert.c...@gmail.com on 4 Apr 2010 at 12:24

GoogleCodeExporter commented 9 years ago
I guess we can close this, as 2010.2 is out.

Original comment by robert.c...@gmail.com on 12 May 2010 at 10:32

GoogleCodeExporter commented 9 years ago
Migrated to http://github.com/sfepy/sfepy/issues/110

Original comment by robert.c...@gmail.com on 30 Jan 2012 at 10:26