Port IDL PDF functionality

[peterfpeterson]

This issue was originally TRAC 7378

To improve the PDFs generated by mantid, port missing functionality as appropriate from the attached IDL programs/methods/functions.

An excerpt from the email that came with the files:

This is how G(r) is defined in idl (file creategr.pro). what Joerg is using to make 
FT with Lorch function is described in fteqs.pro.

I think the correction is basically the same as in the paper I attached, expect 
instead of sin functions he uses Bessel ones.

Two programs have comments, but I will be glad to help if you need to ‘decode’ them.

Best,
Mikhail

[peterfpeterson]

@NickDraper (2013-07-26T13:55:01):
Moved to backlog at the code freeze for R2.6

---

@wdzhou (2013-11-13T19:37:45):
First round of refactoring. Refs http://trac.mantidproject.org/mantid/ticket/7378.

d609181

---

@wdzhou (2013-11-13T19:49:03):
Cleaned the code in minor change. Refs http://trac.mantidproject.org/mantid/ticket/7378.

f208d30

---

@wdzhou (2013-11-15T02:03:07):
Added 2 new equations in wiki. Refs http://trac.mantidproject.org/mantid/ticket/7378.

09ae53c

---

@wdzhou (2013-11-15T02:03:07):
Added g(r) FT code. Refs http://trac.mantidproject.org/mantid/ticket/7378.

30f7e19

---

@NickDraper (2014-02-02T15:34:44):
Moved to backlog at the end of Release 3.1

---

@NickDraper (2014-12-08T10:25:31):
Moved to the backlog at the code freeze of R3.3

[peterfpeterson]

http://trac.mantidproject.org/mantid/raw-attachment/ticket/7378/creategr.pro
(uploaded by @peterfpeterson on 2013-06-27T17:43:43)

---

http://trac.mantidproject.org/mantid/raw-attachment/ticket/7378/fteqs.pro
(uploaded by @peterfpeterson on 2013-06-27T17:43:56)

---

http://trac.mantidproject.org/mantid/raw-attachment/ticket/7378/Lorch.pdf
(uploaded by @peterfpeterson on 2013-06-27T17:44:10)

---

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. If you feel this is incorrect please comment to keep it alive, with a reason why.

To prevent closure, e.g. for long-term planning issues, add the "Never Stale" label.

[stale]

This issue has been closed automatically. If this still affects you please re-open this issue with a comment so we can look into resolving it.