Freely Jointed Chain function

[GoogleCodeExporter]

Not really an issue, but more a suggestion what could be added:

What steps will reproduce the problem?
It would be great to have a freely jointed chain (fjc) fit in hooke. 

What is the expected output? What do you see instead?
Unfortunately, my python experiences are not good enough to write one on my
own. Maybe the wlc model can easily be rewritten for fjc? (Although the fjc
is a x(y) fit.)

What version of the product are you using? On what operating system?
version 0.8.3_devel
Windows XP
Python 2.5.2

Please provide any additional information below.
Maybe not only the committers, but also other users are able to write such
a script. I think, with wlc and fjc the most used models are included.

Original issue reported on code.google.com by albedomanu@googlemail.com on 16 Oct 2009 at 5:31

[GoogleCodeExporter]

This is a good suggestion which is in the (long) "todo" queue. I guess there is 
at
least another guy (illysam) who was working on that, but I didn't hear him in 
the
last few weeks.

Original comment by devicera...@gmail.com on 20 Oct 2009 at 11:00

[GoogleCodeExporter]

I begun working on it. There are some weird errors in the drawing etc. but it 
seems
numbers are reasonable. 

Original comment by devicera...@gmail.com on 31 Oct 2009 at 9:40

[GoogleCodeExporter]

Original comment by devicera...@gmail.com on 31 Oct 2009 at 9:40

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Original comment by devicera...@gmail.com on 31 Oct 2009 at 9:41

[GoogleCodeExporter]

Ok, there should be FJC support now. Main changes are:

- A new environment variable, "fit_function", decides of the function to use 
for the
fits. It can be set as "fjc" or "wlc". Default is "wlc".

- The *wlc* command has been renamed *fit*. *wlc* and *fjc* exist as aliases of
*fit*, but (now) they are mere alternate names -using fjc does not make the fit 
a fjc
if the fit_function is set as "wlc"! The command anyway says what fit function 
you
are using.

- fjc is supported by itself and also within autopeak: it uses the fit_function
variable to decide what fit to use.

Please test it thoroughly and report bugs!

Original comment by devicera...@gmail.com on 1 Nov 2009 at 5:49

• Changed state: Fixed