simple and easy installation of SfePy onto Windows

[tone....@gmail.com]

A new wiki page has been created to focus on simple and easy installation of SfePy onto Windows using only python(x,y) as using EPD results in many failures.

http://code.google.com/p/sfepy/wiki/Simple_Windows_Installation

** detailed and advanced instructions of windows installation is at http://code.google.com/p/sfepy/wiki/PythonXYWindowsInstall

[Logan Sorenson]

Nice work! Thanks for the help!

Logan

> --
> You received this message because you are subscribed to the Google Groups
> "sfepy-devel" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/sfepy-devel/-/27yko5b_4WoJ.
> To post to this group, send email to sfepy...@googlegroups.com.
> To unsubscribe from this group, send email to
> sfepy-devel...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/sfepy-devel?hl=en.
>

[Robert Cimrman]

On 07/08/11 22:37, Logan Sorenson wrote:
> Nice work! Thanks for the help!

+1

I will merge this into the sphinx docs as well. Is the step 3 (pyparsing)
needed with the latest Python(x,y)? It's now listed among additional plugins.

Thanks,
r.

[tone....@gmail.com]

hi,

from http://code.google.com/p/pythonxy/wiki/AdditionalPlugins -

Installation notes

Plugins available on this page are not included in Python(x,y) distributions.

Note that each Python(x,y) plugin is compatible with a standard Python installation (i.e. you may install them on top of any Python installation, even without installing Python(x,y)).

- so one need to download it seperately either from python(x,y) or from pyparsing's project site.

[Robert Cimrman]

I see, thanks!

r.

On 07/11/11 15:56, tone....@gmail.com wrote:
> hi,
>
> from http://code.google.com/p/pythonxy/wiki/AdditionalPlugins -
> Installation notes
>

> Plugins available on this page are *not* included in *Python(x,y)*
> distributions.
>
> Note that each *Python(x,y)* plugin is compatible with a standard Python

> installation (i.e. you may install them on top of any Python installation,

> even without installing *Python(x,y)*).

[tone....@gmail.com]

i have few questions about the capability of sfepy.

can it handle 3D coupled heat and mass transfer problems?

and can we make the folder structure of sfepy more simpler?? 

[Robert Cimrman]

On 07/11/11 16:02, tone....@gmail.com wrote:
> i have few questions about the capability of sfepy.
>
> can it handle 3D coupled heat and mass transfer problems?

IMHO yes, but to be sure, I would need to see the equations.

> and can we make the folder structure of sfepy more simpler??

What do you propose?

r.

[tone....@gmail.com]

I've been playing with sfepy for somedays, but still confused about what file/folder does what. 

My proposal is, there can be two top level  folder inside the sfepy source folder => sfepy folder and setup folder.

just like-

/sfepy-2011.2/ -- (extracted sfepy source folder)

/sfepy-2011.2/setup/ -- (inside will be doc folder, setup+license folder, example folder, tests folder - total four (4) folder)

/sfepy-2011.2/sfepy/ -- (inside will be input folder, sfepy program folder, output folder- total three (3) folder)

input folder will be for both the problem definition file+mesh file (input file and mesh file must have to reside in the same folder, in this case its input folder or anywhere in the hard disk), and the file name of both the problem definition file+mesh file will be same, so that sfepy can automatically load the mesh file once the input file has been loaded.

in this way, the main sfepy program can be kept simple and easy to understand & use for advanced users. The setup folder will help the new comers to learn and exercise, and slowly move on to sfepy folder for advanced use.

let me know what do you think.

cheers!

[Robert Cimrman]

Well, I did not expect the top-level structure to be a problem, more than the
structure under sfepy/ :)

There is a standard Python package structure that most packages adhere to, and
that includes:

build/ for generated files (created by the build process - setup.py)
doc/ for documentation
examples/
bin/ for executables (we have script/ instead, as Python "executables" are not
binary)

then the files like README, VERSION, LICENSE, INSTALL etc. all should be in the
main directory, etc.

So what we have more are:
meshes, output, output-tests

As for meshes, the current way allows to reuse a single mesh in several
examples, and I myself use heavily the possibility to change simply a mesh that
is used in an input file (e.g. to switch between a coarse mesh for debugging
and a fine mesh for actual computations).

I agree that for a newcomer the structure might seem too complex, but it has a
reason. What could be improved is the organization and naming of the examples
and meshes, as the current state is a result more of an organic evolution than
of a careful planning :)

So to conclude: think of examples/ as a beginner's playground, and sfepy/ as
"advanced user's/developer's" territory. The other directories can be mostly
ignored...

Is that ok?
r.

On 07/11/11 19:08, tone....@gmail.com wrote:
> I've been playing with sfepy for somedays, but still confused about what
> file/folder does what.
> My proposal is, there can be two top level folder inside the sfepy source
> folder => sfepy folder and setup folder.
> just like-
>
> /sfepy-2011.2/ -- (extracted sfepy source folder)
>
> /sfepy-2011.2/setup/ -- (inside will be doc folder, setup+license folder,
> example folder, tests folder - total four (4) folder)
>
> /sfepy-2011.2/sfepy/ -- (inside will be input folder, sfepy program folder,
> output folder- total three (3) folder)
>
> input folder will be for both the problem definition file+mesh file (input
> file and mesh file must have to reside in the same folder, in this case its
> input folder or anywhere in the hard disk), and the file name of both
> the problem definition file+mesh file will be same, so that sfepy can
> automatically load the mesh file once the input file has been loaded.
>
> in this way, the main sfepy program can be kept simple and easy to

> understand& use for advanced users. The setup folder will help the new

[tone....@gmail.com]

understood, BTW can you give me a sneak-peak idea of the sfepy/ ? there are a lot of folder there, what does what??

[Robert Cimrman]

On 07/12/11 20:43, tone....@gmail.com wrote:
>
> understood, BTW can you give me a sneak-peak idea of the sfepy/ ? there are
> a lot of folder there, what does what??

Sure. Check out [1], I added this information to the docs. Let me know if you
need refinement :)

r.
[1] http://docs.sfepy.org/doc-devel/developer_guide.html

[Md. Golam Rashed]

Great! now things getting clear, will ask you if stumbled on anything :-)

BTW, I'm the tone.n.tune, this is my new account.

[Md. Golam Rashed]

remove the tone.n.tune@gmail.com member from the sfepy project and add rashed...@gmail.com please.

1. rashed...@gmail.com

1. rashed...@gmail.com

1. rashed...@gmail.com

[Md. Golam Rashed]

Since most dependencies of sfepy are now ported to python 2.7, umfpackpy has also been made available in python 2.7 platform.

see at- http://code.google.com/p/umfpackpy/

..............................................................................................

For simple installation of sfepy on windows-

http://code.google.com/p/sfepy/wiki/Simple_Windows_Installation