All the functions in Tomopy are now global and the docstring format is standard. In VTTools, we have a scraper to generate modules from existing libraries to VisTrails when it starts. It is very helpful to add Tomopy to existing libraries and import functions automatically.

@tacaswell

https://github.com/lmfit/lmfit-py/blob/master/lmfit/asteval.py

See lmfit Interpreter class as a more extensible interpreter and parser for the expressions to be passed through this function.

The functions in wrap_lib.py are now rather intricately tied together. Need to create a set of unit tests to confirm functionality (and continued functionality) the included functions.

Add more functions, such as Lorentzian or Lorentzian squared to VisTrails framework.
Provide end-to-end workflow analysis.

Figure out how/where to incorporate default parameters into wrap_lib

See title...

Have to fix -
VTTools/vttools/vtmods/utils.py

from bubblegum.xrf.model.xrf_model import XRF
commenting out bubulgum/xrf.model part from VTTools/vttools/vtmods/utils.py due it gave errors when try to conda build and install Nikea stack in CSX servers

(to Get the CSX servers up and running #18 (issue 18 in Nikea/internal)
to install NSLS2 metapackage into clean conda environment #20
(issue 20 in Nikea/internal))

1. Need a tool to merge run headers.
2. Need to be able to arbitrarily slice run headers.
3. Need to be able to combine sliced run headers.

bin_edges_to_centers
bin_image_to_1D

Description

In order to more effectively present our modules to users and/or larger communities (diffraction, imaging, fluorescence, etc...) one solution would be to add searchable tags to modules. This would allow the user to type in something like 'diffraction' and have only diffraction relevant modules pop up. It would also allow significantly more advanced sorting techniques to be used.

Notes

searching actually happens on line 214 of \VisTrails\vistrails\gui\common_widgets.py. From a quick glance, it looks like the searching is done on the name of the QItem that each module is represented as. The search signal/slot chain goes:

1. QSearchBox line 556 of common_widgets.py emits an executeSearch signal or an executeIncrementalSearch signal
2. Those signals are captured by QSearchTreeWindow on line 288 of \VisTrails\vistrails\gui\common_widgets.py and connected to the searchItemName method of that class.
3. searchItemName performs the search based on the name of the QItem

Potential Solution

This problem might be solved by adding another QSearchBox to the QSearchTreeWindow that does searches on tags and can have multiple tags separated by a comma, or something along those lines. Somewhere the tags need to get added to the QItems so that they can be searched.

The scraper could be very useful for other systems (eg streamz)

Figure out how/where to incorporate self.get_input_list() to wrap_lib