VistrailsWiki - User contributions [en]

Development

2016-08-17T14:54:00Z

Tommy: /* 2016 */

<div class="nonumtoc toclimit-1">
__TOC__
</div>

See also the [https://github.com/VisTrails/VisTrails/wiki/Development Github wiki]

== 2016 ==
=== August 17, 2016 ===

'''Updates'''
* [TE] Fixed [https://github.com/VisTrails/VisTrails/commit/2cd42d156243067a7663bb0bf0156e5d87188c2f parameter order upgrade bug] that breaks VTK examples.
* [TE] Matplotlib and sklearn are exportable using module-to-script api
* [TE] Need to add to_python_script to pythonfunction.py to get bokeh and numpy export working.

'''Items to Discuss'''
* Version checks: Please use a method instead of hard-coded `try: int(v) except ValueError: ...` logic!
* Mashups: why do they share the same id scope?? (see MashupsManager.createMashupController)
* [TE] Wrap-up notes

=== August 10, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Python Wrapper and scripting
** All changes merged into python-wrapper branch
*** Tests pass
*** Still need to update sub-branches
** Minor fixes
*** vtkPlot3DReader upgrade bug
*** Added tuple exporting
** Most of vtk examples can be exported [https://gist.github.com/rexissimus/5ac7374cde8525d84f9443f019d234e2 example]
*** Sometimes connections are wrong, executing workflow sometimes works, otherwise copy/pasting is necessary
**** Could be a bug in the old vistrail, but not sure
* [DK] Subworkflows and uuids

=== August 3, 2016 ===

'''Updates'''

'''Items to Discuss'''

* [TE] Wrapper patches now stored as [https://github.com/VisTrails/VisTrails/blob/python-wrapper-script-patches/vistrails/packages/vtk/vtk_wrapper/vtk_patch.py python code]
** Connection variables now lowercase
** Can we use code as output variables?
*** E.g. "vtk_dataset_mapper.GetOutput(0)"
*** Could mutate output when output method is only supposed to be called once
*** Need to be able to rename output port as python code(e.g. when there are 2 "vtk_dataset_mapper"s)

=== July 27, 2016 ===

'''Updates'''

* [DK] DB bundle serialization implemented

'''Items to Discuss'''
* [TE] Finished using patch in script [https://github.com/VisTrails/VisTrails/tree/python-wrapper-script-patches python-wrapper-script-patches]
** locale?
** [https://gist.github.com/rexissimus/f0d6b026aa5a2a770847f3321744645d new patching example] vs [https://gist.github.com/rexissimus/b28d83ae516a519167f5751bb8ab3739 old patching example]
** [https://github.com/VisTrails/VisTrails/blob/python-wrapper-script-patches/vistrails/packages/vtk/vtk_wrapper/parse.py#L135-L273 Example of new patches]
** Legacy '.vtkInstance' is now added as a patch "self.vtkInstance=self" (see new patching example)
** [https://github.com/VisTrails/VisTrails/blob/python-wrapper-script-patches/vistrails/core/scripting/api.py New api for executing standalone modules]
*** Accessing module was disabled for core/api, but a different api for this is probably better anyway.
*** api.Package now gives [https://gist.github.com/rexissimus/f0d6b026aa5a2a770847f3321744645d#file-new_patching-py-L26 directly callable module compute functions]
*** Only works on modules not using interpreter functionality ('.interpreter', etc.)
**** for zip file modules and others that need temp files and use the interpreter for this, need to modify the module, but could work around with python libraries for managing temp files
** Fixed more renaming issues - [https://github.com/VisTrails/VisTrails/blob/python-wrapper-script-patches/vistrails/core/scripting/scripts.py#L63-L64 function argument names should not be replaced]
** Still need to do something nicer for the patch formatting
*** patch keys currently contain non-python-variable characters but this can be fixed
*** Need to replace string template with python variables that is replacable using RedBaron
**** Patches could then look like:

def vtkInstance():
self.vtkInstance = self

=== July 20, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] New patch method for python-wrapper [https://gist.github.com/rexissimus/009b303e4cadcd4b8f2fec6cf848cb2b example]
** A patch is a string template with self/input/output variables for patching a class method
** Patches are stored in xml specification
** Patches are assigned to methods in ClassSpec's
** Used both for execution in vistrails and when exporting as script
*** Executed with "exec" when run in vistrails
*** Turns patches into natural calls in script
** Wrapping VTK library no longer needed
*** Removes ".vtkInstance" (Automatically removed from PythonSources and vtkInteractionHandlers)
** Removed fix_classes.py (Subclassing of VTK classes to patch methods directly)
** Also used for port translations (With patch names like "basic:Color#input") (No more ugly input_t method definitions)
** TODO's
*** Add to export_as_script
*** Patch Modules that represent Python functions as well

* [vistrails-users] Read data from SQL example?

=== July 13, 2016 ===

'''Updates'''

* [DK] bundles on sql-alchemy branch
** Bundle, BundleMapping, and BundleSerializer
** New BaseSerializers to deal with versions of directory, zip, db serializers
** Can register the BundleSerializers with the base serializers
** Translation between bundle versions
** Bundle.add_object "just works" if an appropriate mapping was registered

'''Items to Discuss'''
* [TE] Simplified running module using API for scripting [https://gist.github.com/rexissimus/b28d83ae516a519167f5751bb8ab3739 example]
** API Module can be executed using '''compute''' method
*** Takes list of outputs to compute + inputs as keyword arguments
* Status of general cell synchronization (vistrails-users)

=== July 6, 2016 ===

'''Updates'''

* [DK] Working on bundles

'''Items to Discuss'''
* [TE] Using vistrails API in scripting [https://gist.github.com/rexissimus/034d9c4dedc3299a079e84981dedd8c7 example 1 (API with VTK)] [https://gist.github.com/rexissimus/a4a9ca6c08d4058c64967d2b35415fd5 example 2 (DownloadFile only)]
** Call module in script using vistrails API
** Can be used when no export method is defined.
* [TE] [https://github.com/VisTrails/VisTrails/commit/c76c109349769fee1280f85c22678380a2f9cd39 Server news bug] Critical?
**[RR] No, unreleased
* [DK] New bundle organization
** BundleMapping contains individual mappings from raw objects to BundleObj
** Must be separate in order to have in-memory, separate from serializer settings

=== June 29, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Export VTK as python script
** Works on Terminator (Isosurface, Volume Rendering, clipping plane, combined rendering) [https://gist.github.com/rexissimus/16caf5200802e150296f62a0c7844c5a example]
** Preludes (imports) still need improvements
** Works with vtkInteractionHandler (clipping plane)
** Resulting clipping plane is incorrect? (supposed to hide one side of the plane)
** vtkRendererOutput Uses VTKRenderWindow as output
*** Should support different output modes?
*** Does not work with multiple outputs (Next cell is displayed when current is closed)
*** Uses wrapped vtkInstance (as vvtk)
**** Create new patch system with code that can be used both in vistrails and in a python script?

=== June 22, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Fix for upgraded analogies (PR [https://github.com/VisTrails/VisTrails/pull/1177 #1177])
** Uses module location to find module remap (The best we can do right now?)
** Also fixes remapped port names for connections to existing modules
** May still fail on complex upgrades like adding a function on an upgraded module that has a different port name

* [TE] Working on exporting wrapped libraries (VTK)

=== June 15, 2016 ===

'''Updates'''
* [TE] Added depth logic to python script exporter ([https://github.com/VisTrails/VisTrails/commit/50f220e4f6abe5a7bb8689f73f456f43df2dbc12 full commit])
** Fully implements connection merging and list looping

'''Items to Discuss'''

* [TE] Making analogy work on upgraded workflows ([https://github.com/VisTrails/VisTrails/issues/1175 #1175])
** Analogy only works We need to use the non-upgraded action chain
** But pipelines need to be valid (matcher uses module portspecs)
** Tried to get upgrade remap from upgrade action, but this seems impossible
** Use module location instead?
*** Location should be identical for one-to-one module upgrades

=== June 1, 2016 ===

'''Updates'''
* VisTrails 2.2.4 announced (finally)
** 5 survey replies
** 47 downloads last week

'''Items to Discuss'''
* [TE] Export VTK as script (python-wrapper)
** to_python_script
*** needs the pipeline (or at least the connections)
**** Should not generate code for any possible VTK method (exporter detects which ports is used in the source)
**** VTK needs to know connection order
**** Adding functions directly to the script results in nicer code
** Add support for multiple input connections
** Add support for list looping

=== May 25, 2016 ===

'''Updates'''
* Mailing-list fixed
* Getting stats from the "server news" mechanism (via [https://github.com/remram44/apache-log-info parser])

'''Items to Discuss'''
* [RR] Alexis doing writeup on VisTrails, curious about interesting streaming use-cases (and potential future users)
* [TE] Union ports
** Show union ports in pipeline (DEMO)

=== May 18, 2016 ===

'''Items to Discuss'''
* [TE] mailing list still down - Julio working on it
* [TE] Improved union port
** New schema 1.0.5 adds portitem.union string attribute
** Works with pipeline view, parameter exploration view, and mashup view
** Should work well for matplotlib
** Use with VTK ports?
*** It uses [item_1,item_2] style ports usually with different tuple length.
* [TE] Remove emacs dependency from db generate [https://github.com/VisTrails/VisTrails/issues/1173 #1173]

=== May 11, 2016 ===

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]
** GUI-based solution [https://github.com/VisTrails/VisTrails/tree/union-port Branch union-port] Demo?
*** Shows single port for all ports with same sort_key
*** Select specific type when adding/showing
*** Only one type should be visible on the module at any time
*** Making tuple parameters union types is probably too complicated
*** Should work with alternate specs like matplotlib (if sort_key is defined correctly)

* [TE] Feature suggestion: Let connections connect to functions/parameters
** Show functions and parameters as ports and toggle port visibility directly for functions and parameters
** Use separate views for ports and functions (like before)
*** Allow rearranging of functions
** Pros:
*** Supports ordered connections. Create 2 functions, make them visible as ports, make connections to them.
**** We can also have, e.g., a line joining the ports on the module to indicate they are part of a list.
**** Makes List module simpler
*** Connect to parameter in tuple
*** Functions that are visible on the module can connect to an actual function, and not just to the first one it finds.
*** Can replace operation modules (in python-wrapper) in some cases for, e.g., numpy.
** Cons:
*** Interface more complicated and crowded
*** More difficult for users to grasp?
*** No immediate use case
*** Makes no union type for tuple parameters a bigger problem.

* [TE] Publish user survey?
** No response from vistrails release yet
** Not announced on vistrails-users yet.

=== May 4, 2016 ===
'''Updates'''
* VisTrails 2.2.4 released

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]

=== April 27, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Wrapping Bokeh
** New method type "operation"
*** Transforms Figure->Glyph->Output into Glyph->Figure->Output
**** Glyph sets function name and arguments as output
***** Not serializable, but should always be computed together with the subject of the operation.
**** Figure applies Glyph operation on itself
*** Useful for matplotlib?
**** matplotlib currently find actors by searching upstream?
**** But this is more difficult since matplotlib is not function-based.
** New "union" port type
*** Turns "x(float), x(list)" into "x (float, list)" and uses first set value
**** Uses only first value in tuple
**** Bokeh have many properties that support (list, string, Float)
*** Does not work with depth=1 types (e.g. Float of depth 1)
**** Turn Depth 1 types with known type into lists?

* [TE] New bugfix release
** Finalize survey

=== April 20, 2016 ===
'''Updates'''
* Merged upgrade fixes
** Now has infinite loop test
** loop test now correctly loops 5 times
*** remap_module used wrong (current) package version when creating ModuleDescriptor
* Fixed multi-step group upgrades (PR: [https://github.com/VisTrails/VisTrails/issues/1168 #1168])

'''Items to Discuss'''
* New bugfix release
** Merge usagestats
** Need to finalize survey

=== April 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Chaining upgrades done ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Replace "Upgrade" description annotation with "upgraded_from" annotation to identify which tags to hide?

* [TE] Iterating handle_invalid_pipeline ([https://github.com/VisTrails/VisTrails/pull/1165 #1165])
** Not based on [https://github.com/VisTrails/VisTrails/tree/chain-upgrades-loop chain-upgrades-loop]
** Cherry-pick test to preserve source?
** Need maxPipelineFixAttempts option?
*** The code is now smarter about recursion, so max attempts will "probably" never be reached.
** Need [https://github.com/VisTrails/VisTrails/commit/0ef0667426937eddb1d1c1e397f0657ffec039a9 debug messages]?
*** Would need to be moved into handle_invalid_pipeline

=== April 6, 2016 ===
'''Updates'''
* [TE] Query View improvements
** Done except for displaying "Version Info" and #1164
* [RR] Working on finishing new interpreter (finally!)

'''Items to Discuss'''
* [TE] Chaining upgrades ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Try latest upgrade first, then previous.
** If all fail, select latest upgrade?

=== March 30, 2016 ===
'''Updates'''

'''Items to Discuss'''

* [TE] Query View improvements
** Unified do_version_switch and get_upgrades as validate_version()
** Problems with query view using its own controller
*** Fixed module info not being displayed for query results
*** Still no version info for query results
*** Still an issue with version query view not being updated

=== March 23, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Usage reporting almost ready to go
** Need to record whether specific features are used: paramexpore, mashup, query
*** [DK] Record if LaTeX extension is used? But hard to distinguish from direct batch invocation
** How to record size of vistrail?
*** [DK] IdScope already walks over vistrail, use that
*** but total number of modules and versions doesn't give an idea of average size of individual pipelines

=== March 16, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Upgrades in Query Mode
** Now using code similar to do_version_switch
*** Uses handle_invalid_pipeline
*** Differences: Not using current_pipeline, flushes changes
*** New controller method get_pipeline optimized using cached pipelines (but not current_pipeline)
*** Integrate to avoid repeated code?
*** Use this for query mode?
* [TE] VisTrails 2.2.4 ready for release?
** tej package updated. Others?
* [JF] upgrades and the version tree
* [JF] provenance in Jupyter
* [DK] bundles: [https://github.com/VisTrails/VisTrails/pull/1092 #1092]

=== March 9, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixing search mode
** String query now matches all by default
*** This caused pipeline queries to never match
** String query can search: User/Notes/Tagname/Time/Module name
*** Should we search module names by default? (Disabled by default because it is expensive)
*** Fixed notes search
** '>' parameter queries in documentation but has been removed
** Fixed module matches for upgraded pipelines (By not upgrading pipeline)
*** Upgrades still a problem
*** Add "Upgrade all menu option?" (Or upgrade all on open when `hideUpgrades`)
*** [JF] Allow search on past tags

* [TE] Create new bugfix release
** Finish querying
** Path issue on windows

* [DK] Look into sqlalchemy and new bundle branches

=== March 2, 2016 ===
'''Updates'''
* [TE] Fixed cache bug with port specs
* [TE] VisTrails Next
** Most packages now work
** No qgis for Python 3

'''Items to Discuss'''
** Always dereference symlinks? [https://github.com/VisTrails/VisTrails/issues/1146 #1146]

=== February 23, 2016 ===
'''Updates'''
* [TE] Fixed PythonSource 100% CPU bug
* [TE] VisTrails Next
** Updated [http://opendap.co-ops.nos.noaa.gov/axis/webservices/wind/ NOAA Web Service] examples
*** Now uses REST service, tabledata, and Google Maps
*** Web Service replaced with DownloadFile

'''Items to Discuss'''
* [RR] Couple of fixes are in for API, and tej&reprounzip on the Mac binary. Also new release of tej, and working on anonymous usage reports.
** New 2.2 release soon?
* [RR] Anonymous usage reports
** Sends out info like number of modules & versions, packages used, Python & libs versions, execution time, specific features [https://github.com/VisTrails/VisTrails/pull/1154 #1154]
* [JF] Bring in noWorkflow to track variable dependencies, for the considered Jupyter integration?
* noWorkflow - provenance for python scripts
** Recent work on tracking dependencies
* Also integrates ReproZip with Jupyter
** [http://mybinder.org mybinder]
*** Use with ReproZip to automatically build Jupyter notebook interfaces
* Daves comments on Jupyter integration
** It is possible to identify cell order on the server side
** Not trivial to track order of cells on client side
* How does Galaxy workflows relate to VisTrails?
** Packaging in Galaxy is hard
** Galaxy for biomedical workflows, difficulty making it general
* Action items
** How difficult to track cell dependencies in Jupyter notebooks?
** Use noWorkflow to track cell dependencies?
** How difficult to modify mybinder to use ReproZip packages?

=== February 17, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixed Group memory usage
** Modules in groups are supposed to be freed when done executing
*** Prevented by logger that stored references to the modules (fixed, now using id(module))
*** Prevented by list iterator bug that stored list of modules on the 'self' port bug (fixed)
* [TE] VisTrails Next
** Removed deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** PythonSources will be upgraded
*** Fixes for Python < 3
*** fixes for VTK < 6
** TODOs
*** Remove RemoteQ
**** Port Hadoop to tej (Already have pbs)
*** Merge package wrapper
*** Finish SQLAlchemy branch
*** Finish new bundle branch
** [JF] Will contact Jeff and Matthias about moving to Python 3
* [JF] Query by Example is broken
* [JF] VisTrails Data Cleaning Project
** Use VisTrails to process and explore task-specific data while keeping provenance.
** Remi's Idea
*** Use VisTrails as the backend in a Jupyter notebook
*** Overcome problems with executing cells in random order
**** Interesting research topic, but little interest has yet been noted
*** Interesting to study how such a notebook would be used (Is there notebook usage data available?)
*** Impose restrictions to notebook cell boundaries
*** It will only work for functional operations
*** Can we fix, or detect, non-functional (mutating) operations?
*** Analyse code and data flow and see if it mutates data in unexpected ways?
*** Mutable operations can be created in many ways in Python
* Next meeting Tuesday 11:30

=== February 10, 2016 ===
'''Updates'''

'''Items to Discuss'''
* VisTrails Next
** Test suite passes
*** Python 3 less deterministic, module upgrade order random.
** [RR] updating packages: Reprounzip (pushed), tej, persistent_archive, ...
** All of our packages should run fine :)
** VTK thumbnail comparison works
*** Rendering bug on some systems
**** QVTKCell now inherits QGLWidget
*** Old thumbnails had wrong height due to spreadsheetwindow being too small
**** Fixed by regenerating thumbnails
*** Silenced deprecation messages when generating modules
*** Many new classes in VTK 7
** Remove deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** Will break existing PythonSources
**** Try to upgrade?
*** Old-style packages
**** Or only allow a new style, like __init__.py renamed to info.py? (merge with identifiers.py?)
***** Read info.py without importing package?
*** Fixes for Python < 3
*** Fixes for Qt < 5
*** fixes for VTK < 7
*** Remove self port?

=== February 3, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] [http://lists.vistrails.org/pipermail/vistrails-users/2016-January/000402.html Rendering a .pvd (ParaView) file?]

* VisTrails Next
** All tests but thumbnail comparison passes
** Still issues with gui and more packages needs to be tested
** PythonSource and MplSource upgraded with lib2to3
** Keep contrib packages? Update?
** [https://blog.kitware.com/vtk-7-0-0/ VTK 7 is released]
*** Supports Python 3
*** Will hopefully get into conda and others soon
*** Deprecates a bunch of modules

* [https://travis-ci.org/VisTrails/VisTrails/builds/106743348 Travis builder] for VisTrails Next
** Runs!
** Uses conda
*** Many levels of requirements
**** apt packages
**** conda packages
**** python packages in requirements.txt
**** python packages in setup.py
*** Can probably drop conda. Default builder does not have Qt5, but beta builder do!
*** But useful if we want to use conda in our own build process.
** Lots of errors I do not get locally?

* [http://goo.gl/forms/Z4HBrwaBWL User Survey]
** Have you used any alternatives to vistrails?
*** Relevant? More options?
** How often do you use any of these particular features in VisTrails?
*** Add/Remove alternatives?
** How important would you rank the following potential improvements to VisTrails?
*** Add alternatives?

=== January 27, 2016 ===
'''Updates'''
* New interpreter
** Working prototype soon
** Looping not completely done (and port combination mode: pairwise/cartesian...)
** Need to integrate with VisTrails
*** Compatibility with existing modules
*** Use log controller
*** Want to cache at multiple levels (whole stream/single element of stream)
*** Non-runtime attributes of modules (cache check, automatic conversion check, constant from/to string)

'''Items to Discuss'''
* User Survey

* ZMQ failing on windows (vistrails-users)

* [TE] [https://github.com/VisTrails/VisTrails/pull/1143 Python 3 branch]
** Testsuite almost passes
*** Failing are unicode filenames, some users guide examples, and thumbnail comparisons.
** Fixed issues
*** Signatures are now bytes (convert to string to show in widget)
*** Cannot compare different types, e.g., (None < 1)
**** PortSpec.depth and min/maxConn could be None. (Backport!)
**** cell.row could be None
*** Lots of unicode/bytes fixes to serializations
**** We have encryption implementations in the code! (keychain)
*** Lots of small fixes to package method differences
** Current issues
*** logging widget empty?
*** version tree signals messed up
*** provenance view legend icons black
*** Text do not fit in some widgets
*** VTK thumbnail comparison fails
**** VTK Cells have some faces in wrong direction?
**** Because running in VM?
** Installing on Ubuntu LTS/Latest Mint
*** Install latest matplotlib from pip
*** Install VTK 7.0.0rc2 from source
*** No QtWebEngine binary (controversial) (Must install sip/PyQt5/Qt5 from source)

=== January 20, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Backporting features from Python 3 + PyQt5 + Qt5
** Merged unicode with master ([https://github.com/VisTrails/VisTrails/tree/unicode unicode])
*** One unicode test failing
*** Problem saving to xml
** Used [http://python-future.org/ python-future] to run futurize stage 1 to update legacy (pre 2.6) code ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized unicode-futurized])
*** Updates print to functions 'from __future__ import print_function'
*** Updates exception calls to use 'as'
*** removes most usages of 'long' (mostly used unnecessarily)
**** Only needed for 32-bit support
*** Fixes relative imports (from __future__ import absolute_import)
** Fixing code that is deprecated in Qt 4.8 and removed in Qt 5 ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized-qt5 unicode-futurized-qt5])
*** Updated all signals to new-style
* If we go 2 to 3, this could break packages
** means we should schedule any package format changes for the same time
** e.g., imports should be unrelated to code path (function to load module from package identifier?) (take them out of vistrails.* [https://github.com/VisTrails/VisTrails/pull/1002 #1002])
** any structural changes (e.g. the __init__ versus init thing) (RR thinks it makes sense, though having both named "init" is unfortunate)
** putting package identifier as xml?
*** Python not so bad, plus some stuff in there is Python code (checking dependencies)
** version the APIs?
*** RR planning on versioning vistrails_module.Module, no point versioning the whole package?
* file formats on 2 to 3:
** no real translation/upgrade, but non-ascii values that work on 3 won't load in 2

=== January 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://gist.github.com/rexissimus/dfd27e466427529c385c Porting to Python 3 / PyQt5]
** Basic GUI and execution works
** Minimal work to support 2to3
** Hard to support both PyQt4 and PyQt5

=== January 6, 2016 ===
'''Updates'''
'''Items to Discuss'''
* Updating VisTrails dependencies
** Successfully built [https://gist.github.com/rexissimus/f1a1aada7de1c00a57c7 Win7-64/Python3/PyQt5/Qt5/WebEngine/VTK7]
*** VTK 7 is the first supporting Python 3 but is only in release candidate phase.
**** Next version of VTK 6 is rumored to support Python 3
**** There is a development branch of VTK 6 supporting Python 3
*** Can travis build this?
**** We can skip tests for WebEngine and VTK if needed
** Python 3 [https://python3wos.appspot.com/ showstoppers]
*** No MySQL-python (sqlalchemy supports mysql through other drivers)
*** No suds (there are active forks but we could also drop support?)
* Options for python2/3 support:
** Interpreter could be python2/python3 based on packages
** six layer works but not the easiest to maintain (e.g. in reprozip)
* Drop support for win-64
* Update copyright headers to 2016

== 2015 ==

=== December 30, 2015 ===
'''Updates'''
* Bokeh package finished
** Can output to Browser/IPython/Spreadsheet (Limited functionality in spreadsheet)
'''Items to Discuss'''
* Updating VisTrails dependencies
** Bokeh needs QWebEngine (Chromium) in Qt5 which requires PyQt5
*** Many plotting libraries only work in browsers
*** But Chromium may be a big and controversial dependency
*** Or create a browser version of the spreadsheet?
** Some users have requested Python 3
** Not backwards compatible?
** Target for VisTrails 3.0 with new interpreter?

=== December 16, 2015 ===
'''Updates'''
'''Items to Discuss'''
* Users list question
* [TE] Wrapping Bokeh
** Added bokeh property parser
*** complements numpydoc parser
*** Not all attributes are available, partially because I am using a pre-release version.
** Wrapped modules
*** bokeh.plotting finished (Backwards like matplotlib: Create plot then draw on it)
*** bokeh.charts mostly done (Missing arguments)
** QWebView mostly works (but no zooming or buttons)
*** It would be better to use external browser or QWebEngineView
** Added improvements to wrapper
*** Generalized port translations (Color/Path to native types)
*** Can use multiple docstring/property parsers simultaneously

=== December 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Looking into wrapper
** Will port TensorFlow
** Doing a pass on the wrapper code & doc
*** UX improvements
** Factorize high-level docstring parsers into core.wrapper? (sphinx, numpy, google)
** Problem with name vs module_name (fails sklearn tests because class_by_name() is broken)
** Looking into compressing specs, lazy registration of modules

=== December 2, 2015 ===
'''Updates'''
* [TE] Package wrapping
** Wrapped most of numpy/scipy using __all__
** Added class attribute and method access for classes (Can add to class or to separate inspector module)
** TODO: Document wrapping procedure

'''Items to Discuss'''

=== November 25, 2015 ===
'''Updates'''
* [RR] New interpreter is coming along
** Everything is a stream
** Task system, eventually work-stealing parallelism
** Streams no longer advance in lock-step
*** Allows for constructions like filter, join, sorted-merge
** depth>1 still to be tested, no current plan to allow this through the module interface
*** Through looping though, can do streams of streams

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapped most numpy functions (no polynomials)
** and half of scipy classes and functions
** Added functions manually from documentation (no parseable lists?)
** Focusing on data flow constructs (no property/method access for classes)
*** Using spec diff (empty for now) and dynamic parser (stores spec in .vistrails/)
** Python class/function wrapper now stable
** Add google doc parser?
*** Is there a parser available?

=== November 18, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Numpy class wrapping works
*** Basic type is List, since most types are array_likes.
*** TODO: More classes and functions
*** Some operations are in-place and some aren't, and docstring not super clear
*** [RR] It seems only methods mutate, and most have a numpy.xx function equivalent; just manually go through the methods and remove the mutating ones?
** Class wrapper is modular
*** Docstring parser and type string parser can be customized
*** Classes can have optional attribute/method ports
**** Inspectors and attribute/method modules can be created separately
** Use PythonCalc as an example
*** Can be re-implemented as a function with a parseable docstring
*** [RR] PythonCalc is just an example, and it might actually make sense to get rid of it, or do a proper math package with scalar operations (as separate modules, no combobox)
** [RR] TensorFlow to use wrapping as well
*** Very simple (only types 'tensor' & 'variable')

=== November 11, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapping numpy's classes using numpydoc (ndarray)
*** Wrapping constructor arguments, attribute getters/setters as module ports
**** Then how to access attributes afterwards?
***** Use input value port to class modules?
*** Wrap methods as modules? E.g., `ndarray.shape`.
*** Function wrapping is almost a subset of class wrapping
**** May be able to use the same parsing/execution methods
** VTK's non-getter/setter methods could be wrapped as modules
*** We could then remove extra logic in interpreter for keeping function order
** Bokeh uses autogenerated docstrings
*** We may be able to read the specification directly

* [RR] [https://github.com/VisTrails/VisTrails/pull/1138 TensorFlow package]
** Basic setup working, can execute the Mandelbrot example
** Will autogenerate the operations

=== November 4, 2015 ===
'''Updates'''
* [RR] Interpreter work requires a fix for [https://github.com/VisTrails/VisTrails/issues/1137 DB issue #1137]
* [DK] Kitware's Resonant [http://www.kitware.com/source/home/post/173]
** [https://github.com/girder/girder Girder]: data management system
** [https://github.com/Kitware/romanesco Romanesco]: execution engine, uses [http://www.celeryproject.org/ Celery] for task management
** Resonant Flow: web app for editing and executing workflows

'''Items to Discuss'''
* [TE] Added OSX Lion (10.7) VM on build machine using vagrant (seems ok with license?)
** New builds works on Lion
** Change the minimum requirement to 10.7?
* [TE] Package wrapping
* Added upgrade suggestions using 2 spec versions ([http://pastebin.com/30XUU8Gp example])
** using name edit distance to find matches
** Could use something better like port similarity for modules, and type similarity for ports
** Should write python upgrade code?
** Added spec to sklearn package
*** Can now diff spec versions and keep the spec static
*** There will be problems with downgrades and package versions

=== October 29, 2015 ===
'''Updates'''
* [TE] nightly-build-mac fixed (Needed to approve xcode license)

'''Items to Discuss'''
* [TE] matplotlib wrapper
** ported to general spec
** Diff can be used on general spec
*** Only needed minor changes
*** Fixed indexing bug that corrupted specs
*** Can now move diff tools to core/wrapper
** Add new plots?
*** New plots in mpl 1.3: eventplot
*** New plots in mpl 1.4: angle_spectrum, magnitude_spectrum, phase_spectrum', violinplot
*** No new plots in mpl 1.5 (from looking at boilerplate.py)

=== October 21, 2015 ===
'''Updates'''
* [RR] Alexis has arrived, will be working with [RR] on a more efficient interpreter

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package]
** Supporting multiple package versions
*** Check which version can be loaded [https://github.com/VisTrails/VisTrails/pull/1135 #1135]
*** We cannot show version requirements in the list of packages because old packages are loaded when importing the codepath
** Visual diff does not work well, but we can use the spec differ to see differences.
** Unifying vtk and matplotlib wrapping specs (WIP)
*** And porting matplotlibs spec differ to work on the general spec
*** Spec differ can then be used on vtk and other packages in the future
*** Will enable automatic upgrade generation
* [RR] Rework interpreter
** restore abstraction between interpreter/module code
** build looping, streaming, caching into the interpreter
** rework cache
** look into parallelism once basic functionality is there

=== October 14, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package] (adding numpydoc parser)

=== October 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/tree/fix-matplotlib-parser New matplotlib parser] (adding numpydoc parser)
** Added numpydoc attribute parser for plots.
*** TODO: Need better port spec reconciliation with call signature parser.
*** We can create a general numpydoc parser, but attribute types are unique to matplotlib.
** Needs package versioning
*** New spec will not support matplotlib < v1.4 due to changed path to axes classes.
*** Load spec version corresponding to installed matplotlib version?
*** Need version downgrades?

=== September 30, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Updating Matplotlib parser
** Matplotlib docstring parser fails on numpy docstrings
** I have [https://github.com/VisTrails/VisTrails/commit/eae8b0c16260810587e47c41cab53552cbb3cf0a added basic numpydoc parsing]
*** Only used by a few docstrings so far
*** Parsing uses many sources (class tables, signatures, ACCEPTS, method docstrings, definition parsing).
** Caswell said they were thinking about moving to traitlets, but this is not ready yet

=== September 23, 2015 ===
'''Updates'''
* [TE] VisTrails 2.2.3 released
** Also have pushed to PyPI, binstar, etc.
** Sourceforge vs. GitHub
*** should be able to host releases on GitHub
*** nightly binaries pushed to sf each night
*** old binaries?
* [TE] Re-wrapping MatPlotlib
** Keep static generation - Docstrings are brittle beween matplotlib versions
** Keep generating the executable classes - but create functions, not vistrails Modules
*** Why is there so much patching?
** Re-implemented Alternate PortSpec for InputPortSpec
*** It will now inherit specs from parent (No need to reimplement)
** Module upgrades?

'''Items to Discuss'''

=== September 16, 2015 ===
'''Updates'''
* [TE] Job Monitor tests and documentation done
** OK to leave document package in packages directory?

'''Items to Discuss'''
* [TE] Library wrapping: How to do code patching? [https://docs.google.com/drawings/d/1Sh3eOXot6v2y880jHKQrqXqAwr-0aoqYligg3z8G8MY/edit?usp=sharing Wrapping diagram]
** Insert code into module template (Old VTK code)
** Patch the library that is called (New VTK code)
** Somehow store code in spec and apply when executed?
*** Executed code needs at a minimum access to inputs, outputs, current class
*** Use standard input/output dict and obj reference that the code operates on?
*** Can this be done while keeping the execution abstract?

* Do new release now?

=== September 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* New release?
** [RR] wants reprounzip
** tej changes & doc
** job monitor & jobmixin fixes
** mongodb
** reprounzip
** warning: MplFigure type is int
** tabledata: add Reshape, DictoToTable & ListToTable, fix ListToTable with numpy arrays
** PythonSource can have same name for an input & output
** don't show spreadsheet at exit

=== September 2, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Limit autosaves? [https://github.com/VisTrails/VisTrails/pull/1126 #1126]

=== August 26, 2015 ===
'''Updates'''
* [TE] Added Job support to Parameter Explorations (Requested by Colin), and Mashups
** specify job ids, need to specify different ids for parameter explorations since they have the same version id
** how to deal with parameters passed in on command line
* [General] provenance: should be creating a new version when we execute workflow with changed parameters?
** currently, custom_params annotation stores this in provenance currently
** [RR] API doesn't record provenance if passing in parameters: http://git.io/vsAA5
'''Items to Discuss'''

=== August 19, 2015 ===
'''Updates'''
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [TE] Working on Job Monitor documentation

'''Items to Discuss'''
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [TE] Stop testing VisTrails 2.0?

=== August 12, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Build broken on Travis; because of IPython 4 released today? ([https://travis-ci.org/VisTrails/VisTrails/builds/75279795 build 992]; [https://github.com/VisTrails/VisTrails/issues/1123 #1123])

=== August 5, 2015 ===
'''Updates'''
* [TE] Fixes to Jobs
** Could not delete jobs
** Could not run job in group
** Job not reset when calling ModuleSuspended
** Added deleting job from context menu
* [RR] Writing documentation for everything [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

'''Items to Discuss'''

=== July 29, 2015 ===
'''Updates'''
* RR still looking into new interpreter thing
** Goal is to take out scheduling logic from Module so it can be split in multiple processes, and so that smarter strategies can be added in time
** This means some work on packages
** Spreadsheet can live in kernel process? Still some UI stuff that will take work (changing configuration, persistent archive's viewer, ...)
* [TE] Problems running examples [https://github.com/VisTrails/VisTrails/pull/1111 #1111]
** Testing of more examples requires additional packages on the test machines.
** Fixed faulty line-ending in PythonSource:s failing on Python 2.6.
** Test suite now testing SUDSWebServices (If web service is down, test suite will fail)
** preferences.py test failed reloading 'dialogs' package, switched to using 'URL'.

'''Items to Discuss'''

=== July 22, 2015 ===
'''Updates'''
* [TE] mailing lists back online
* [TE] Working on [https://github.com/VisTrails/VisTrails/issues/1107 #1107]
* [RR] Working on ReproZip package

'''Items to Discuss'''
* [RR] MongoDB package [https://github.com/VisTrails/VisTrails/pull/1106 #1106]
* [RR] Example for tej docs? [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

=== July 15, 2015 ===
'''Updates'''
* 2.2.2 released

'''Items to Discuss'''
* RR is considering executing everything in an IPython kernel (i.e. separate Python interpreter, like the one spawned for a notebook)
** It's a separate process that we can restart without restarting the app/gui
** We can isolate the execution environment (e.g. for the server)
** We can run the whole thing remotely (if your data is elsewhere, just run VisTrails locally and the pipeline elsewhere)
** Pipeline execution no longer makes the interface hang, it just makes the kernel hang (but that's fine)
** We can use notebooks as modules (probably way nicer than the PythonSource module)
** We can run multiple kernels so long as the ports carry things that are serializable
*** meaning we can put the multithreaded-interpreter without all the hacky parts it has now
*** we can run IPython kernels in all the languages IPython supports, [https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages currently 46]

=== July 8, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Buildbot github hook not working after IP address change
* [TE] No reference to VistrailsApplication ([https://github.com/VisTrails/VisTrails/issues/1103 #1103])
** [RR] Added PR [https://github.com/VisTrails/VisTrails/pull/1104 #1104]
* [TE] Reopening VT file after saving with bundled subworkflow won't offer subworkflow upgrade ([https://github.com/VisTrails/VisTrails/issues/1102 #1102])
** allow manual delete to fix right now
** fix this on top of the use-uuid branch
* [TE] Release VisTrails 2.2.1? ([https://github.com/VisTrails/VisTrails/blob/v2.2/CHANGELOG CHANGELOG])
** [https://github.com/VisTrails/VisTrails/pull/1093 output-modules-use-global-dir]
** [https://github.com/VisTrails/VisTrails/milestones/version%202.2 Current issues for 2.2]

=== July 1, 2015 ===
'''Updates'''
* [TE] PROV fixed
* [TE] Working on subworkflow issues
* [RR] Considering reworking the controller (log vs exception problem, retained upgrades causing interferences) and also the interpreter (IPython?)

'''Items to Discuss'''

=== June 24, 2015 ===
'''Updates'''

'''Items to Discuss'''
* UV-CDAT
* [TE] Can a cyclic workflow be valid? ([https://github.com/VisTrails/VisTrails/issues/1097 #1097])
** focus on disabling the ability to create cyclic pipelines because more things break than just this with a cyclic pipeline
* [RR] Relative paths ([https://github.com/VisTrails/VisTrails/pull/1057 #1057])
** This interacts with the new bundle; how do handle packing files inside the VT bundle?

=== June 17, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] current_version and reusing existing upgrades are broken ([https://github.com/VisTrails/VisTrails/issues/1095 ticket #1095])
** Could be that export to PROV is using an unflushed upgrade pipeline?
** current_version would then be correct.
** It may work to flush the actions before exporting?

=== June 10, 2015 ===
'''Updates'''
* DAT: fixed VTK issue on Linux and Mac
* Still crashes on Windows. Need help! Reminder: this works in the VisTrails spreadsheet (QCellPresenter), although no widget get changed there during a drag
** Is it a VTK bug?
** Is it simply impossible to change widgets during the drag, should we do it a different way?
** Did I miss something that is done in VisTrails but somehow not in DAT?
** Low prio, UV-CDAT doesn't run on Windows anyway

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 Updated pull request])
* Single instance code and batch mode

=== June 3, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 pr])
** Requires fixes to command line parameters, Output modules, and batch mode
** How to test this
** Updated missing/outdated flags
** Fixed view issues when generating graphs
* [TE] batch mode
** SpreadsheetOutput not enabled in batch mode. Should we check is_running_gui instead?
** Other instance setting flags from caller
** Is graphsAsPdf replacing spreadsheetDumpPdf?
** graphsAsPdf true by Default?
** Batch mode executing by default (Not needed when generating graphs)
** Re-added workflowInfo as withWorkflowInfo for writing graph and xml workflow
** [DK] batch mode should be outputting to files or stdout, shouldn't always trigger SpreadsheetMode
** execute flag, maybe make execution the default and allow a "--no-execute" if you only want to capture graphs, for example

=== May 27, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] API question
** http://lists.vistrails.org/pipermail/vistrails-users/2015-May/000357.html
* Status of DAT
** Can add VCS plot to DAT but need to work on configuration windows
** Documentation for graphics templates for UV-CDAT/vcs?
* Qt support?

=== May 20, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Reviving the DAT, integrating scripting & porting UV-CDAT!
** On [https://github.com/VisTrails/DAT GitHub] ([https://github.com/VisTrails/DAT/issues issues])
** Merging 2 years of development taking longer than expected, but getting there. The plan is to get the patches in VisTrails and never fork again, we never want to get in UV-CDAT's situation (and don't need to).
** VTK cell works fine on Linux but there was flickering on Mac & Windows before; still issues on Mac (Windows status unknown)
** Can get a VCS plot soon (but will need VTK cell fix)
** Integrate in UV-CDAT's build system (so we have cdms, VCS, ...) -> RR can do this, low priority
** How do we integrate scripting?
*** We want to be able to seamlessly make changes to a plot by changing Python code
*** Define new plots by entering Python code without writing modules/packages?
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 13, 2015 ===
'''Updates'''
* [RR] Test skipping whitelist ([https://github.com/VisTrails/VisTrails/pull/1069 #1069]) -- low priority
* [RR] Custom matplotlib modules can't be compatible with both 2.1 and 2.2 ([https://github.com/VisTrails/VisTrails/issues/1067 #1067]); should be fixed for ALPS ([https://github.com/VisTrails/VisTrails/issues/1070 #1070])

'''Items to Discuss'''
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 7, 2015 ===
'''Updates'''
* [RR] Export/import workflow to Python working!

'''Items to Discuss'''
* [Claudio] UV-CDAT
** The UV-CDAT project is the biggest user base of VisTrails
** VisTrails package management provides a lot of friction towards people plugging in their code
** Need to make it easy to integrate your random Python scripts in the system without having to deal with all the boilerplate, at least in the first step
** [RR] argues that modules are still good; UV-CDAT shouldn't move towards a purely script-based backend
** [RR] export/import with Python could reduce a lot of that friction by allowing 1) to edit workflow as Python 2) to open up boxes automatically if needed code doesn't match actual modules
** ...

=== April 29, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] <strike>Abstractions</strike> subworkflows status ([https://github.com/VisTrails/VisTrails/labels/subworkflows tickets])
* [RR] matplotlib compatibility (2.1 & 2.2), [https://github.com/VisTrails/VisTrails/issues/1067 #1067]
** RR to try and fix ALPS matplotlib modules

=== April 22, 2015 ===
'''Updates'''
* 2.2.0 has been released!
* Windows issue (via email from Ryan)
** issue with manifest file (may be a new file in VTK6?)
** Tommy has regenerated new Windows builds
* Binaries, pypi, and conda released
* [RR] Export as script
* Python sources using VTK need to switch to SetInputData (users should be aware of this)

=== April 15, 2015 ===
'''Updates'''
* Ready for 2.2.0 (apart from binary/deps issues)
** Missing some libs (scikit-learn, tej, tdparser, SQLAlchemy+connectors
** Windows: runvistrails.py is no longer used, so the PATH is wrong
** Windows: pip is broken, but it probably wouldn't work anyway because of permission issues (disable this?)
* Queries, upgrades and getPipeline() usage ([https://github.com/VisTrails/VisTrails/issues/1054 #1054])
** Getting a pipeline with getPipeline() is not safe: it might return an invalid pipeline
** This is used in many places throughout the code, like queries
** Upgrading would require going through the controller, but that creates new actions
* [TC] Avoid copying a module's output if it's used as input by exactly one downstream module ([https://github.com/VisTrails/VisTrails/issues/1060 #1060]) (useful for big numpy arrays you can update in-place)

=== April 8, 2015 ===
'''Updates'''
* [DK] Merged RR's changes for output modules (1012 and 1013)
** RR will merge remaining changes, then create v2.2 branch!

'''Items to Discuss'''
* BNL need numpy array to VTK image
** Looks like VTK has some helpers for this
** We will help if issues arise
** Will contribute back to VisTrails package
* Upgrade issue: [https://github.com/VisTrails/VisTrails/issues/1017 #1017]
** Automatic upgrades should happen between versions of provided upgrades
** Our existing upgrades work around this so it doesn't need to be 2.2.0
* Corner-case VTK modules
** No longer need VTKCell input port, so don't interfere with registry and API anymore
** Still work weirdly, people probably shouldn't use them
** But we have lots of clunky modules since we wrap the whole of VTK; some people might rely on this and know how to use them, let's keep them anyway
** Ready for 2.2.0

=== April 1, 2015 ===
'''Updates'''
* [RR] UV-CDAT: bugfixing for 2.2, long-term plans: implement scripting import/export in VisTrails, port to UV-CDAT
* Possibly, try to move to regular VisTrails to use new features

'''Items to Discuss'''
* 2.2 release: nothing much is pending anymore, release next week?
** [TE] vtkExporter classes [https://github.com/VisTrails/VisTrails/issues/1032 #1032]
** [RR] Hiding upgrades in version tree might make it (or might be 2.2.1 so we can test it out) [https://github.com/VisTrails/VisTrails/issues/949 #949]
** Output modules changes to go in
* add note to documentation about order of parameters in VTK
* add issue about exporter upgrades if not already there

=== March 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* 2.2 release
** Checklist on Github: https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist
** Review output modules
** RR has a couple more issues to fix
** Ready to go -- sign app package for OSX? [https://github.com/VisTrails/VisTrails/issues/984 #984] We need access to the Apple Membership team

=== March 18, 2015 ===
'''Updates'''
* [TE] VTK6 works

'''Items to Discuss'''
* [RR] Release v2.1.5 with backported tabledata?
** MTA example needs updated tabledata (for JoinTables)
** Google Maps package still not available
* [RR] Work torward v2.2.0?
** changes:
*** new persistence
*** API changes
*** output module changes (upgrades?), maintain cells but try to upgrade
*** not wrapping stuff
*** VTK6? yes
*** JobSubmission stuff?
*** relabeling for upgrades [https://github.com/VisTrails/VisTrails/issues/949 #949]
** makes sense, needs the tree view code to be updated, check selection
** See [https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist 2.2 checklist]
* Discussion of [https://github.com/VisTrails/VisTrails/issues/1016 #1016]
** plumbing between outputs and output modes, how to define a mode that works for many outputs without writing for each output?

=== March 11, 2015 ===
'''Updates'''
* [RR] persistent_archive done; merge? ([https://github.com/VisTrails/VisTrails/pull/755 #755])
** note about the focus events for widgets
** TE be aware of file_archive for future binaries that include persistent_archive
* [TE] [https://github.com/VisTrails/VisTrails/pull/998 New VTK package] finished

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails? (see last week; decision needed)
** RR email to JF about this
** yes; email sent to Github
* [RR] Switching order of output ports ([https://github.com/VisTrails/VisTrails/pull/1006 #1006])
** added port specs are sorted at a separate spot (Module.*_port_specs properties) than those in the registry (which are sorted in the registry), but those two lists are just combined without respect to sort keys
** need to determine whether the two lists should be merged or remain distinct
** should make sure that order of input ports and output ports makes parallel connections for things with same order
** DK suggests breaking backward compatibility here: workflows still run, can fix easily if a problem in an existing package.
* [RR] Question about output modes ([https://github.com/VisTrails/VisTrails/pull/1007 #1007]), how to integrate in API ([https://github.com/VisTrails/VisTrails/pull/24 #24])
** Should ImageFileMode be removed? ("image" is not a mode, "file" is)
** ImageOutput missing?
** Feel free to change how formats works
* [TE] Test suite segfaults on Fedora 17 virtualbox. Install newer version? (Support ended in 2013)

=== March 4, 2015 ===
'''Updates'''
* [TE] VTK wrapper
** Works on VTK 5.10
** Still need to test VTK 6
** New general wrappers for python functions and classes

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails?
** When [http://i.imgur.com/UTY2qfg.png filing a pull request] from UV-CDAT/VisTrails, VisTrails/VisTrails is selected by default
** People keep forgetting to change the default ([https://github.com/VisTrails/VisTrails/pull/956 #956] [https://github.com/VisTrails/VisTrails/pull/968 #968] [https://github.com/VisTrails/VisTrails/pull/999 #999] [https://github.com/VisTrails/VisTrails/pull/1000 #1000] [https://github.com/VisTrails/VisTrails/pull/1003 #1003] [https://github.com/VisTrails/VisTrails/pull/1004 #1004] [https://github.com/VisTrails/VisTrails/pull/1005 #1005])
** Only way to change that is to not have it marked as a fork of VisTrails/VisTrails
** Github staff [https://gist.github.com/remram44/b364c24ef1e462ce6e2f can make that change for us]; should we do it?
** Juliana: comments on this? visibility vs. convenience/annoyance for developers
* [RR] What about [https://github.com/VisTrails/VisTrails/issues/991 #991]?

=== February 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] vtkviewcell for infovis support, can we unify with VTKCell?
** need to test this
* [TE] vtk wrapping
** Mostly finished
** VTK 5.10 produce incorrect results with old wrapping
*** Old wrapper is based mostly on VTK 4
*** Most vtk_examples affected
*** [http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Replacement_of_SetInput]
*** should be able to upgrade from SetInput to SetInputData (need to drop GetOutput and replace with self ports)
*** can we change vtkInstance to just return self and not wrap things
** terminator example not working under 5.8?
* How does VTK wrapping fit into general wrapping framework?
* [RR] new persistence package

=== February 18, 2015 ===
'''Updates'''
* [RR] New VisTrails API and IPython integration ([https://github.com/VisTrails/VisTrails/pull/24 #24])

'''Items to Discuss'''
* [TE] VTK wrapping
** [https://gist.github.com/rexissimus/16b74693545b5e7c1035 Benchmarking vtk package]
*** Old: 24.7 seconds
*** New: 10.5 seconds (Except first time that adds 8 sec)
**** The parsing that calls is_abstract (that tries to instanciate all vtk classes) is now only run the first time.
**** get_items_from_sigstring takes 2 seconds, maybe we can use a lookup dict for already computed sigstrings?
** Now using a general python function wrapper
*** VTK classes are wrapped into python function that does not depend on vistrails
*** VTK functions can be executed without vistrails
*** The spec maps functions into vistrails modules, but can also describe wrapping
*** A general python function wrapper that supports
**** kwarg inputs
**** single, list, dict outputs
**** callback for progress reporting
**** temporary file generator for using FilePool
**** optional output generation
*** Creating specs:
***** Create spec by hand
***** Auto-create spec outline (TODO) and manually finish it
***** Dynamically create spec (VTK)
***** Implement documentation wrappers (Can use scikitlearn wrapper to wrap numpydoc) (TODO)
***** Classes as bad functions needs to be wrapped in new functions before they are wrapped. This is different for each package.
****** Classes is hard: Like VTK, and matplotlib. Scikit-learn does still not wrap classes
***** Spec diffing and patching could be done using code from matplotlib.
** Still needs upgrades from old VTK package
*** Is it possible to dynamically wrap functions, e.g, you see a SetFunc and just remove the 'Set' prefix. Or do you need to create a complete mapping?

=== February 11, 2015 ===
'''Updates'''
* Update from Friday's meeting
** discussed VisTrails internals
** discussed wrapping
*** xml discussion, hard to modify because tied to db code
*** TE has made it possible to add the schema-defined attributes to the intermediate representation
*** higher-level operations on the port specs
** make sure the simple case works
*** [JF] take a simple package with documentation and figure out what the base case for wrapping is

'''Items to Discuss'''
* [TE] VTK wrapping
** Dynamic loading works
** Reading XML is fast enough, but [https://gist.github.com/rexissimus/8272d3c776ccfa115d82 unserializing data is slow]
** Working on patterns for patching
** Matplotlib has many advanced patterns like argument ordering, nested arguments, alternateSpecs, output types.
*** Having all this in a general wrapper might confuse users?
** [RR] Delay module (except for identifiers) until you need it---e.g. don't deal with port specs, etc. until necessary
* Scripting Support [https://github.com/VisTrails/VisTrails/pull/950 #950]
** [RR] Issue with getting code from modules
** Design a simple solution
** [JF] Couldn't you use modules as black boxes without conversion, just to call into modules/subworkflows easily from e.g. IPython?
*** [RR] This is a job for the API, and a very separate use case. See [https://github.com/VisTrails/VisTrails/pull/24 #24]

=== February 4, 2015 ===
'''Updates'''

'''Items to Discuss'''
* Wrapping
** Format to use? Currently XML (like current matplotlib)
*** JSON and YAML have simple "to python dictionary" methods
*** But don't stream
*** YAML a lot easier for humans
** [DK] vtk-new-package also changes parameter names, creates enumerations
*** intermediate schema needs to be extensible
*** packages will want to store there specific infos for compute() method generation
*** also might have specs-altering info, like matplotlib's alternateSpec
** representation to code , registry already has schema for some aspects
** [RR] We might want to see if Module subclasses can be created lazily
*** no need to create all the classes just to register them in the registry and never actually use most of them
*** future effort
* [RR] Where should VisTrails packages live?
** tej installs as 'vistrailspkg.tej', TE installed it as 'userpackages.tej'
** Currently, standard packages are 'vistrails.packages.', user packages are 'userpackages.' and packages loaded through pkg_resources might be anything
** [RR] Use 'vistrailspkg.' everywhere?
** Long-term effort to simplify package distribution/installation (and have VisTrails get them automatically?)

=== January 28, 2015 ===
'''Updates'''
* T. Caswell to come visit on Fri 6 to discuss wrapping work

'''Items to Discuss'''
* [TE] New VTK wrapping
** Current code by DK seems a good deal faster
** Generates XML that can be patched/tweaked, generates Python code from it, VisTrails only loads generated Python code
** RR would rather have VisTrails load intermediate representation (= XML) directly, wants to make sure this is not slower
** The goal is to turn the intermediate step into something generic that would be used for every wrapped package (vtk, numpy, matplotlib, sklearn, java) instead of each having its own
** TC has its own code at [https://github.com/Nikea/VTTools/blob/master/vttools/wrap_lib.py github:VTTools] which parses numpy docstrings and generates modules, doesn't yet handle classes or persist anything
* Web crawler
** Right now, TE starts jobs for "start crawler", "stop crawler", "install classifier"
** RR would rather have the crawling be a job as far as VisTrails and tej are concerned
** The whole thing would be one pipeline: load examples, train classifier, start crawler [check for job, kill previous one, upload model, start processes], get snapshot, visualize
*** Need some support in tej and job submission system: long-running jobs, stop a job (wait for it to finish?), restart a job even though results are cached

=== January 21, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Unified wrapping method discussion [https://github.com/VisTrails/VisTrails/issues/991 #991]
** TE to work on reusable method with intermediate representation, starting with VTK
* [RR] Examples for scikit-learn: JF has an old example using Weka with parameter exploration (not currently in source tree)
** AM's examples are enough
* [AM] scikit-learn package is done, merge it in? [https://github.com/VisTrails/VisTrails/pull/955#issuecomment-70286788 #955]
** RR will merge
* [RR] What should copyright headers say? [https://github.com/VisTrails/VisTrails/pull/994#issuecomment-70173935 #994]
** Let's keep everything in there: Utah/Poly/NYU

=== January 14, 2015 ===
'''Updates'''
* [TE] Working on classifier
* [RR] Scripting integration, work in progress

'''Items to Discuss'''
* [RR] Unified wrapping method discussion ([https://github.com/VisTrails/VisTrails/issues/991 #991])
** Let's talk next week, [AM] and [DK] are not here

=== January 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* make sure that we address critical issues, questions, and pending review branches in a timely manner
* scripting support
** [RR] no issues if we want to just keep annotations in the generated code to allow the link back to a workflow
** [RR] can translate from workflow to script, working on script to workflow
** will work for parameter value changes, structural changes require changes to the annotations
** need to publish best practices here
** would be cool to do looping in scripts (easier interface than with workflows)
* notebook support (convert form notebook to workflow)
** RR will sync with FC on this
* Issue with console in built-from-scratch
** [TC] iPython rearranged some of the completion stuff in 2.2 and 2.3
** binary has old version of iPython -> 1.0.0, should we update?
* [TC] automated wrapping of numpy and scipy
** discovered a bunch of malformed documentation in numpy and scipy
** has github repo for vistrails tools
** example modules wrap a bunch of R stuff (not baked in, just how things are)
** will be pushing wrapping logic up
** port names forbidden (window and domain)
** have an import hook to get from yaml directly to VisTrails Modules
** should work for any python modules with well-formed numpy docstrings.
* [Action] should make it clear in documentation that Constant now means serializable not that the value doesn't change (e.g. List)
* [TC] might be interesting to try to build components of matplotlib and accumulate in figure (long-term project, but thinking about how this might work)
* [TE] build and build scripts
** completely automatic, buildbot
** need to set the build machines for the environment we want for the binary
** would virtualenv work here?
** [TC] anaconda can pin versions, potential path to test different configurations
** Q: upload nightly binary builds? A: makes sense, make sure they are well-labeled
* sourceforge stats: e.g. http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07
* package issues (see Remi's message)
* [TE] Scope of tej
** Support single ssh commands?
** Queue can be used as a remote machine (crawler is using queue.call*)
* SourceForge stats: http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07

== Older meetings ==
* [[Development/2014]]
* [[Development/2013]]
* [[Development/2012]]
* [[Development/2011]]
* [[Development/2010]]

Development

2016-08-10T15:00:18Z

Tommy: /* August 3, 2016 */

<div class="nonumtoc toclimit-1">
__TOC__
</div>

See also the [https://github.com/VisTrails/VisTrails/wiki/Development Github wiki]

== 2016 ==
=== August 10, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Python Wrapper and scripting
** All changes merged into python-wrapper branch
*** Tests pass
*** Still need to update sub-branches
** Minor fixes
*** vtkPlot3DReader upgrade bug
*** Added tuple exporting
** Most of vtk examples can be exported [https://gist.github.com/rexissimus/5ac7374cde8525d84f9443f019d234e2 example]
*** Sometimes connections are wrong, executing workflow sometimes works, otherwise copy/pasting is necessary
**** Could be a bug in the old vistrail, but not sure
* [DK] Subworkflows and uuids

=== August 3, 2016 ===

'''Updates'''

'''Items to Discuss'''

* [TE] Wrapper patches now stored as [https://github.com/VisTrails/VisTrails/blob/python-wrapper-script-patches/vistrails/packages/vtk/vtk_wrapper/vtk_patch.py python code]
** Connection variables now lowercase
** Can we use code as output variables?
*** E.g. "vtk_dataset_mapper.GetOutput(0)"
*** Could mutate output when output method is only supposed to be called once
*** Need to be able to rename output port as python code(e.g. when there are 2 "vtk_dataset_mapper"s)

=== July 27, 2016 ===

'''Updates'''

* [DK] DB bundle serialization implemented

'''Items to Discuss'''
* [TE] Finished using patch in script [https://github.com/VisTrails/VisTrails/tree/python-wrapper-script-patches python-wrapper-script-patches]
** locale?
** [https://gist.github.com/rexissimus/f0d6b026aa5a2a770847f3321744645d new patching example] vs [https://gist.github.com/rexissimus/b28d83ae516a519167f5751bb8ab3739 old patching example]
** [https://github.com/VisTrails/VisTrails/blob/python-wrapper-script-patches/vistrails/packages/vtk/vtk_wrapper/parse.py#L135-L273 Example of new patches]
** Legacy '.vtkInstance' is now added as a patch "self.vtkInstance=self" (see new patching example)
** [https://github.com/VisTrails/VisTrails/blob/python-wrapper-script-patches/vistrails/core/scripting/api.py New api for executing standalone modules]
*** Accessing module was disabled for core/api, but a different api for this is probably better anyway.
*** api.Package now gives [https://gist.github.com/rexissimus/f0d6b026aa5a2a770847f3321744645d#file-new_patching-py-L26 directly callable module compute functions]
*** Only works on modules not using interpreter functionality ('.interpreter', etc.)
**** for zip file modules and others that need temp files and use the interpreter for this, need to modify the module, but could work around with python libraries for managing temp files
** Fixed more renaming issues - [https://github.com/VisTrails/VisTrails/blob/python-wrapper-script-patches/vistrails/core/scripting/scripts.py#L63-L64 function argument names should not be replaced]
** Still need to do something nicer for the patch formatting
*** patch keys currently contain non-python-variable characters but this can be fixed
*** Need to replace string template with python variables that is replacable using RedBaron
**** Patches could then look like:

def vtkInstance():
self.vtkInstance = self

=== July 20, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] New patch method for python-wrapper [https://gist.github.com/rexissimus/009b303e4cadcd4b8f2fec6cf848cb2b example]
** A patch is a string template with self/input/output variables for patching a class method
** Patches are stored in xml specification
** Patches are assigned to methods in ClassSpec's
** Used both for execution in vistrails and when exporting as script
*** Executed with "exec" when run in vistrails
*** Turns patches into natural calls in script
** Wrapping VTK library no longer needed
*** Removes ".vtkInstance" (Automatically removed from PythonSources and vtkInteractionHandlers)
** Removed fix_classes.py (Subclassing of VTK classes to patch methods directly)
** Also used for port translations (With patch names like "basic:Color#input") (No more ugly input_t method definitions)
** TODO's
*** Add to export_as_script
*** Patch Modules that represent Python functions as well

* [vistrails-users] Read data from SQL example?

=== July 13, 2016 ===

'''Updates'''

* [DK] bundles on sql-alchemy branch
** Bundle, BundleMapping, and BundleSerializer
** New BaseSerializers to deal with versions of directory, zip, db serializers
** Can register the BundleSerializers with the base serializers
** Translation between bundle versions
** Bundle.add_object "just works" if an appropriate mapping was registered

'''Items to Discuss'''
* [TE] Simplified running module using API for scripting [https://gist.github.com/rexissimus/b28d83ae516a519167f5751bb8ab3739 example]
** API Module can be executed using '''compute''' method
*** Takes list of outputs to compute + inputs as keyword arguments
* Status of general cell synchronization (vistrails-users)

=== July 6, 2016 ===

'''Updates'''

* [DK] Working on bundles

'''Items to Discuss'''
* [TE] Using vistrails API in scripting [https://gist.github.com/rexissimus/034d9c4dedc3299a079e84981dedd8c7 example 1 (API with VTK)] [https://gist.github.com/rexissimus/a4a9ca6c08d4058c64967d2b35415fd5 example 2 (DownloadFile only)]
** Call module in script using vistrails API
** Can be used when no export method is defined.
* [TE] [https://github.com/VisTrails/VisTrails/commit/c76c109349769fee1280f85c22678380a2f9cd39 Server news bug] Critical?
**[RR] No, unreleased
* [DK] New bundle organization
** BundleMapping contains individual mappings from raw objects to BundleObj
** Must be separate in order to have in-memory, separate from serializer settings

=== June 29, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Export VTK as python script
** Works on Terminator (Isosurface, Volume Rendering, clipping plane, combined rendering) [https://gist.github.com/rexissimus/16caf5200802e150296f62a0c7844c5a example]
** Preludes (imports) still need improvements
** Works with vtkInteractionHandler (clipping plane)
** Resulting clipping plane is incorrect? (supposed to hide one side of the plane)
** vtkRendererOutput Uses VTKRenderWindow as output
*** Should support different output modes?
*** Does not work with multiple outputs (Next cell is displayed when current is closed)
*** Uses wrapped vtkInstance (as vvtk)
**** Create new patch system with code that can be used both in vistrails and in a python script?

=== June 22, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Fix for upgraded analogies (PR [https://github.com/VisTrails/VisTrails/pull/1177 #1177])
** Uses module location to find module remap (The best we can do right now?)
** Also fixes remapped port names for connections to existing modules
** May still fail on complex upgrades like adding a function on an upgraded module that has a different port name

* [TE] Working on exporting wrapped libraries (VTK)

=== June 15, 2016 ===

'''Updates'''
* [TE] Added depth logic to python script exporter ([https://github.com/VisTrails/VisTrails/commit/50f220e4f6abe5a7bb8689f73f456f43df2dbc12 full commit])
** Fully implements connection merging and list looping

'''Items to Discuss'''

* [TE] Making analogy work on upgraded workflows ([https://github.com/VisTrails/VisTrails/issues/1175 #1175])
** Analogy only works We need to use the non-upgraded action chain
** But pipelines need to be valid (matcher uses module portspecs)
** Tried to get upgrade remap from upgrade action, but this seems impossible
** Use module location instead?
*** Location should be identical for one-to-one module upgrades

=== June 1, 2016 ===

'''Updates'''
* VisTrails 2.2.4 announced (finally)
** 5 survey replies
** 47 downloads last week

'''Items to Discuss'''
* [TE] Export VTK as script (python-wrapper)
** to_python_script
*** needs the pipeline (or at least the connections)
**** Should not generate code for any possible VTK method (exporter detects which ports is used in the source)
**** VTK needs to know connection order
**** Adding functions directly to the script results in nicer code
** Add support for multiple input connections
** Add support for list looping

=== May 25, 2016 ===

'''Updates'''
* Mailing-list fixed
* Getting stats from the "server news" mechanism (via [https://github.com/remram44/apache-log-info parser])

'''Items to Discuss'''
* [RR] Alexis doing writeup on VisTrails, curious about interesting streaming use-cases (and potential future users)
* [TE] Union ports
** Show union ports in pipeline (DEMO)

=== May 18, 2016 ===

'''Items to Discuss'''
* [TE] mailing list still down - Julio working on it
* [TE] Improved union port
** New schema 1.0.5 adds portitem.union string attribute
** Works with pipeline view, parameter exploration view, and mashup view
** Should work well for matplotlib
** Use with VTK ports?
*** It uses [item_1,item_2] style ports usually with different tuple length.
* [TE] Remove emacs dependency from db generate [https://github.com/VisTrails/VisTrails/issues/1173 #1173]

=== May 11, 2016 ===

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]
** GUI-based solution [https://github.com/VisTrails/VisTrails/tree/union-port Branch union-port] Demo?
*** Shows single port for all ports with same sort_key
*** Select specific type when adding/showing
*** Only one type should be visible on the module at any time
*** Making tuple parameters union types is probably too complicated
*** Should work with alternate specs like matplotlib (if sort_key is defined correctly)

* [TE] Feature suggestion: Let connections connect to functions/parameters
** Show functions and parameters as ports and toggle port visibility directly for functions and parameters
** Use separate views for ports and functions (like before)
*** Allow rearranging of functions
** Pros:
*** Supports ordered connections. Create 2 functions, make them visible as ports, make connections to them.
**** We can also have, e.g., a line joining the ports on the module to indicate they are part of a list.
**** Makes List module simpler
*** Connect to parameter in tuple
*** Functions that are visible on the module can connect to an actual function, and not just to the first one it finds.
*** Can replace operation modules (in python-wrapper) in some cases for, e.g., numpy.
** Cons:
*** Interface more complicated and crowded
*** More difficult for users to grasp?
*** No immediate use case
*** Makes no union type for tuple parameters a bigger problem.

* [TE] Publish user survey?
** No response from vistrails release yet
** Not announced on vistrails-users yet.

=== May 4, 2016 ===
'''Updates'''
* VisTrails 2.2.4 released

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]

=== April 27, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Wrapping Bokeh
** New method type "operation"
*** Transforms Figure->Glyph->Output into Glyph->Figure->Output
**** Glyph sets function name and arguments as output
***** Not serializable, but should always be computed together with the subject of the operation.
**** Figure applies Glyph operation on itself
*** Useful for matplotlib?
**** matplotlib currently find actors by searching upstream?
**** But this is more difficult since matplotlib is not function-based.
** New "union" port type
*** Turns "x(float), x(list)" into "x (float, list)" and uses first set value
**** Uses only first value in tuple
**** Bokeh have many properties that support (list, string, Float)
*** Does not work with depth=1 types (e.g. Float of depth 1)
**** Turn Depth 1 types with known type into lists?

* [TE] New bugfix release
** Finalize survey

=== April 20, 2016 ===
'''Updates'''
* Merged upgrade fixes
** Now has infinite loop test
** loop test now correctly loops 5 times
*** remap_module used wrong (current) package version when creating ModuleDescriptor
* Fixed multi-step group upgrades (PR: [https://github.com/VisTrails/VisTrails/issues/1168 #1168])

'''Items to Discuss'''
* New bugfix release
** Merge usagestats
** Need to finalize survey

=== April 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Chaining upgrades done ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Replace "Upgrade" description annotation with "upgraded_from" annotation to identify which tags to hide?

* [TE] Iterating handle_invalid_pipeline ([https://github.com/VisTrails/VisTrails/pull/1165 #1165])
** Not based on [https://github.com/VisTrails/VisTrails/tree/chain-upgrades-loop chain-upgrades-loop]
** Cherry-pick test to preserve source?
** Need maxPipelineFixAttempts option?
*** The code is now smarter about recursion, so max attempts will "probably" never be reached.
** Need [https://github.com/VisTrails/VisTrails/commit/0ef0667426937eddb1d1c1e397f0657ffec039a9 debug messages]?
*** Would need to be moved into handle_invalid_pipeline

=== April 6, 2016 ===
'''Updates'''
* [TE] Query View improvements
** Done except for displaying "Version Info" and #1164
* [RR] Working on finishing new interpreter (finally!)

'''Items to Discuss'''
* [TE] Chaining upgrades ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Try latest upgrade first, then previous.
** If all fail, select latest upgrade?

=== March 30, 2016 ===
'''Updates'''

'''Items to Discuss'''

* [TE] Query View improvements
** Unified do_version_switch and get_upgrades as validate_version()
** Problems with query view using its own controller
*** Fixed module info not being displayed for query results
*** Still no version info for query results
*** Still an issue with version query view not being updated

=== March 23, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Usage reporting almost ready to go
** Need to record whether specific features are used: paramexpore, mashup, query
*** [DK] Record if LaTeX extension is used? But hard to distinguish from direct batch invocation
** How to record size of vistrail?
*** [DK] IdScope already walks over vistrail, use that
*** but total number of modules and versions doesn't give an idea of average size of individual pipelines

=== March 16, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Upgrades in Query Mode
** Now using code similar to do_version_switch
*** Uses handle_invalid_pipeline
*** Differences: Not using current_pipeline, flushes changes
*** New controller method get_pipeline optimized using cached pipelines (but not current_pipeline)
*** Integrate to avoid repeated code?
*** Use this for query mode?
* [TE] VisTrails 2.2.4 ready for release?
** tej package updated. Others?
* [JF] upgrades and the version tree
* [JF] provenance in Jupyter
* [DK] bundles: [https://github.com/VisTrails/VisTrails/pull/1092 #1092]

=== March 9, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixing search mode
** String query now matches all by default
*** This caused pipeline queries to never match
** String query can search: User/Notes/Tagname/Time/Module name
*** Should we search module names by default? (Disabled by default because it is expensive)
*** Fixed notes search
** '>' parameter queries in documentation but has been removed
** Fixed module matches for upgraded pipelines (By not upgrading pipeline)
*** Upgrades still a problem
*** Add "Upgrade all menu option?" (Or upgrade all on open when `hideUpgrades`)
*** [JF] Allow search on past tags

* [TE] Create new bugfix release
** Finish querying
** Path issue on windows

* [DK] Look into sqlalchemy and new bundle branches

=== March 2, 2016 ===
'''Updates'''
* [TE] Fixed cache bug with port specs
* [TE] VisTrails Next
** Most packages now work
** No qgis for Python 3

'''Items to Discuss'''
** Always dereference symlinks? [https://github.com/VisTrails/VisTrails/issues/1146 #1146]

=== February 23, 2016 ===
'''Updates'''
* [TE] Fixed PythonSource 100% CPU bug
* [TE] VisTrails Next
** Updated [http://opendap.co-ops.nos.noaa.gov/axis/webservices/wind/ NOAA Web Service] examples
*** Now uses REST service, tabledata, and Google Maps
*** Web Service replaced with DownloadFile

'''Items to Discuss'''
* [RR] Couple of fixes are in for API, and tej&reprounzip on the Mac binary. Also new release of tej, and working on anonymous usage reports.
** New 2.2 release soon?
* [RR] Anonymous usage reports
** Sends out info like number of modules & versions, packages used, Python & libs versions, execution time, specific features [https://github.com/VisTrails/VisTrails/pull/1154 #1154]
* [JF] Bring in noWorkflow to track variable dependencies, for the considered Jupyter integration?
* noWorkflow - provenance for python scripts
** Recent work on tracking dependencies
* Also integrates ReproZip with Jupyter
** [http://mybinder.org mybinder]
*** Use with ReproZip to automatically build Jupyter notebook interfaces
* Daves comments on Jupyter integration
** It is possible to identify cell order on the server side
** Not trivial to track order of cells on client side
* How does Galaxy workflows relate to VisTrails?
** Packaging in Galaxy is hard
** Galaxy for biomedical workflows, difficulty making it general
* Action items
** How difficult to track cell dependencies in Jupyter notebooks?
** Use noWorkflow to track cell dependencies?
** How difficult to modify mybinder to use ReproZip packages?

=== February 17, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixed Group memory usage
** Modules in groups are supposed to be freed when done executing
*** Prevented by logger that stored references to the modules (fixed, now using id(module))
*** Prevented by list iterator bug that stored list of modules on the 'self' port bug (fixed)
* [TE] VisTrails Next
** Removed deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** PythonSources will be upgraded
*** Fixes for Python < 3
*** fixes for VTK < 6
** TODOs
*** Remove RemoteQ
**** Port Hadoop to tej (Already have pbs)
*** Merge package wrapper
*** Finish SQLAlchemy branch
*** Finish new bundle branch
** [JF] Will contact Jeff and Matthias about moving to Python 3
* [JF] Query by Example is broken
* [JF] VisTrails Data Cleaning Project
** Use VisTrails to process and explore task-specific data while keeping provenance.
** Remi's Idea
*** Use VisTrails as the backend in a Jupyter notebook
*** Overcome problems with executing cells in random order
**** Interesting research topic, but little interest has yet been noted
*** Interesting to study how such a notebook would be used (Is there notebook usage data available?)
*** Impose restrictions to notebook cell boundaries
*** It will only work for functional operations
*** Can we fix, or detect, non-functional (mutating) operations?
*** Analyse code and data flow and see if it mutates data in unexpected ways?
*** Mutable operations can be created in many ways in Python
* Next meeting Tuesday 11:30

=== February 10, 2016 ===
'''Updates'''

'''Items to Discuss'''
* VisTrails Next
** Test suite passes
*** Python 3 less deterministic, module upgrade order random.
** [RR] updating packages: Reprounzip (pushed), tej, persistent_archive, ...
** All of our packages should run fine :)
** VTK thumbnail comparison works
*** Rendering bug on some systems
**** QVTKCell now inherits QGLWidget
*** Old thumbnails had wrong height due to spreadsheetwindow being too small
**** Fixed by regenerating thumbnails
*** Silenced deprecation messages when generating modules
*** Many new classes in VTK 7
** Remove deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** Will break existing PythonSources
**** Try to upgrade?
*** Old-style packages
**** Or only allow a new style, like __init__.py renamed to info.py? (merge with identifiers.py?)
***** Read info.py without importing package?
*** Fixes for Python < 3
*** Fixes for Qt < 5
*** fixes for VTK < 7
*** Remove self port?

=== February 3, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] [http://lists.vistrails.org/pipermail/vistrails-users/2016-January/000402.html Rendering a .pvd (ParaView) file?]

* VisTrails Next
** All tests but thumbnail comparison passes
** Still issues with gui and more packages needs to be tested
** PythonSource and MplSource upgraded with lib2to3
** Keep contrib packages? Update?
** [https://blog.kitware.com/vtk-7-0-0/ VTK 7 is released]
*** Supports Python 3
*** Will hopefully get into conda and others soon
*** Deprecates a bunch of modules

* [https://travis-ci.org/VisTrails/VisTrails/builds/106743348 Travis builder] for VisTrails Next
** Runs!
** Uses conda
*** Many levels of requirements
**** apt packages
**** conda packages
**** python packages in requirements.txt
**** python packages in setup.py
*** Can probably drop conda. Default builder does not have Qt5, but beta builder do!
*** But useful if we want to use conda in our own build process.
** Lots of errors I do not get locally?

* [http://goo.gl/forms/Z4HBrwaBWL User Survey]
** Have you used any alternatives to vistrails?
*** Relevant? More options?
** How often do you use any of these particular features in VisTrails?
*** Add/Remove alternatives?
** How important would you rank the following potential improvements to VisTrails?
*** Add alternatives?

=== January 27, 2016 ===
'''Updates'''
* New interpreter
** Working prototype soon
** Looping not completely done (and port combination mode: pairwise/cartesian...)
** Need to integrate with VisTrails
*** Compatibility with existing modules
*** Use log controller
*** Want to cache at multiple levels (whole stream/single element of stream)
*** Non-runtime attributes of modules (cache check, automatic conversion check, constant from/to string)

'''Items to Discuss'''
* User Survey

* ZMQ failing on windows (vistrails-users)

* [TE] [https://github.com/VisTrails/VisTrails/pull/1143 Python 3 branch]
** Testsuite almost passes
*** Failing are unicode filenames, some users guide examples, and thumbnail comparisons.
** Fixed issues
*** Signatures are now bytes (convert to string to show in widget)
*** Cannot compare different types, e.g., (None < 1)
**** PortSpec.depth and min/maxConn could be None. (Backport!)
**** cell.row could be None
*** Lots of unicode/bytes fixes to serializations
**** We have encryption implementations in the code! (keychain)
*** Lots of small fixes to package method differences
** Current issues
*** logging widget empty?
*** version tree signals messed up
*** provenance view legend icons black
*** Text do not fit in some widgets
*** VTK thumbnail comparison fails
**** VTK Cells have some faces in wrong direction?
**** Because running in VM?
** Installing on Ubuntu LTS/Latest Mint
*** Install latest matplotlib from pip
*** Install VTK 7.0.0rc2 from source
*** No QtWebEngine binary (controversial) (Must install sip/PyQt5/Qt5 from source)

=== January 20, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Backporting features from Python 3 + PyQt5 + Qt5
** Merged unicode with master ([https://github.com/VisTrails/VisTrails/tree/unicode unicode])
*** One unicode test failing
*** Problem saving to xml
** Used [http://python-future.org/ python-future] to run futurize stage 1 to update legacy (pre 2.6) code ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized unicode-futurized])
*** Updates print to functions 'from __future__ import print_function'
*** Updates exception calls to use 'as'
*** removes most usages of 'long' (mostly used unnecessarily)
**** Only needed for 32-bit support
*** Fixes relative imports (from __future__ import absolute_import)
** Fixing code that is deprecated in Qt 4.8 and removed in Qt 5 ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized-qt5 unicode-futurized-qt5])
*** Updated all signals to new-style
* If we go 2 to 3, this could break packages
** means we should schedule any package format changes for the same time
** e.g., imports should be unrelated to code path (function to load module from package identifier?) (take them out of vistrails.* [https://github.com/VisTrails/VisTrails/pull/1002 #1002])
** any structural changes (e.g. the __init__ versus init thing) (RR thinks it makes sense, though having both named "init" is unfortunate)
** putting package identifier as xml?
*** Python not so bad, plus some stuff in there is Python code (checking dependencies)
** version the APIs?
*** RR planning on versioning vistrails_module.Module, no point versioning the whole package?
* file formats on 2 to 3:
** no real translation/upgrade, but non-ascii values that work on 3 won't load in 2

=== January 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://gist.github.com/rexissimus/dfd27e466427529c385c Porting to Python 3 / PyQt5]
** Basic GUI and execution works
** Minimal work to support 2to3
** Hard to support both PyQt4 and PyQt5

=== January 6, 2016 ===
'''Updates'''
'''Items to Discuss'''
* Updating VisTrails dependencies
** Successfully built [https://gist.github.com/rexissimus/f1a1aada7de1c00a57c7 Win7-64/Python3/PyQt5/Qt5/WebEngine/VTK7]
*** VTK 7 is the first supporting Python 3 but is only in release candidate phase.
**** Next version of VTK 6 is rumored to support Python 3
**** There is a development branch of VTK 6 supporting Python 3
*** Can travis build this?
**** We can skip tests for WebEngine and VTK if needed
** Python 3 [https://python3wos.appspot.com/ showstoppers]
*** No MySQL-python (sqlalchemy supports mysql through other drivers)
*** No suds (there are active forks but we could also drop support?)
* Options for python2/3 support:
** Interpreter could be python2/python3 based on packages
** six layer works but not the easiest to maintain (e.g. in reprozip)
* Drop support for win-64
* Update copyright headers to 2016

== 2015 ==

=== December 30, 2015 ===
'''Updates'''
* Bokeh package finished
** Can output to Browser/IPython/Spreadsheet (Limited functionality in spreadsheet)
'''Items to Discuss'''
* Updating VisTrails dependencies
** Bokeh needs QWebEngine (Chromium) in Qt5 which requires PyQt5
*** Many plotting libraries only work in browsers
*** But Chromium may be a big and controversial dependency
*** Or create a browser version of the spreadsheet?
** Some users have requested Python 3
** Not backwards compatible?
** Target for VisTrails 3.0 with new interpreter?

=== December 16, 2015 ===
'''Updates'''
'''Items to Discuss'''
* Users list question
* [TE] Wrapping Bokeh
** Added bokeh property parser
*** complements numpydoc parser
*** Not all attributes are available, partially because I am using a pre-release version.
** Wrapped modules
*** bokeh.plotting finished (Backwards like matplotlib: Create plot then draw on it)
*** bokeh.charts mostly done (Missing arguments)
** QWebView mostly works (but no zooming or buttons)
*** It would be better to use external browser or QWebEngineView
** Added improvements to wrapper
*** Generalized port translations (Color/Path to native types)
*** Can use multiple docstring/property parsers simultaneously

=== December 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Looking into wrapper
** Will port TensorFlow
** Doing a pass on the wrapper code & doc
*** UX improvements
** Factorize high-level docstring parsers into core.wrapper? (sphinx, numpy, google)
** Problem with name vs module_name (fails sklearn tests because class_by_name() is broken)
** Looking into compressing specs, lazy registration of modules

=== December 2, 2015 ===
'''Updates'''
* [TE] Package wrapping
** Wrapped most of numpy/scipy using __all__
** Added class attribute and method access for classes (Can add to class or to separate inspector module)
** TODO: Document wrapping procedure

'''Items to Discuss'''

=== November 25, 2015 ===
'''Updates'''
* [RR] New interpreter is coming along
** Everything is a stream
** Task system, eventually work-stealing parallelism
** Streams no longer advance in lock-step
*** Allows for constructions like filter, join, sorted-merge
** depth>1 still to be tested, no current plan to allow this through the module interface
*** Through looping though, can do streams of streams

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapped most numpy functions (no polynomials)
** and half of scipy classes and functions
** Added functions manually from documentation (no parseable lists?)
** Focusing on data flow constructs (no property/method access for classes)
*** Using spec diff (empty for now) and dynamic parser (stores spec in .vistrails/)
** Python class/function wrapper now stable
** Add google doc parser?
*** Is there a parser available?

=== November 18, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Numpy class wrapping works
*** Basic type is List, since most types are array_likes.
*** TODO: More classes and functions
*** Some operations are in-place and some aren't, and docstring not super clear
*** [RR] It seems only methods mutate, and most have a numpy.xx function equivalent; just manually go through the methods and remove the mutating ones?
** Class wrapper is modular
*** Docstring parser and type string parser can be customized
*** Classes can have optional attribute/method ports
**** Inspectors and attribute/method modules can be created separately
** Use PythonCalc as an example
*** Can be re-implemented as a function with a parseable docstring
*** [RR] PythonCalc is just an example, and it might actually make sense to get rid of it, or do a proper math package with scalar operations (as separate modules, no combobox)
** [RR] TensorFlow to use wrapping as well
*** Very simple (only types 'tensor' & 'variable')

=== November 11, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapping numpy's classes using numpydoc (ndarray)
*** Wrapping constructor arguments, attribute getters/setters as module ports
**** Then how to access attributes afterwards?
***** Use input value port to class modules?
*** Wrap methods as modules? E.g., `ndarray.shape`.
*** Function wrapping is almost a subset of class wrapping
**** May be able to use the same parsing/execution methods
** VTK's non-getter/setter methods could be wrapped as modules
*** We could then remove extra logic in interpreter for keeping function order
** Bokeh uses autogenerated docstrings
*** We may be able to read the specification directly

* [RR] [https://github.com/VisTrails/VisTrails/pull/1138 TensorFlow package]
** Basic setup working, can execute the Mandelbrot example
** Will autogenerate the operations

=== November 4, 2015 ===
'''Updates'''
* [RR] Interpreter work requires a fix for [https://github.com/VisTrails/VisTrails/issues/1137 DB issue #1137]
* [DK] Kitware's Resonant [http://www.kitware.com/source/home/post/173]
** [https://github.com/girder/girder Girder]: data management system
** [https://github.com/Kitware/romanesco Romanesco]: execution engine, uses [http://www.celeryproject.org/ Celery] for task management
** Resonant Flow: web app for editing and executing workflows

'''Items to Discuss'''
* [TE] Added OSX Lion (10.7) VM on build machine using vagrant (seems ok with license?)
** New builds works on Lion
** Change the minimum requirement to 10.7?
* [TE] Package wrapping
* Added upgrade suggestions using 2 spec versions ([http://pastebin.com/30XUU8Gp example])
** using name edit distance to find matches
** Could use something better like port similarity for modules, and type similarity for ports
** Should write python upgrade code?
** Added spec to sklearn package
*** Can now diff spec versions and keep the spec static
*** There will be problems with downgrades and package versions

=== October 29, 2015 ===
'''Updates'''
* [TE] nightly-build-mac fixed (Needed to approve xcode license)

'''Items to Discuss'''
* [TE] matplotlib wrapper
** ported to general spec
** Diff can be used on general spec
*** Only needed minor changes
*** Fixed indexing bug that corrupted specs
*** Can now move diff tools to core/wrapper
** Add new plots?
*** New plots in mpl 1.3: eventplot
*** New plots in mpl 1.4: angle_spectrum, magnitude_spectrum, phase_spectrum', violinplot
*** No new plots in mpl 1.5 (from looking at boilerplate.py)

=== October 21, 2015 ===
'''Updates'''
* [RR] Alexis has arrived, will be working with [RR] on a more efficient interpreter

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package]
** Supporting multiple package versions
*** Check which version can be loaded [https://github.com/VisTrails/VisTrails/pull/1135 #1135]
*** We cannot show version requirements in the list of packages because old packages are loaded when importing the codepath
** Visual diff does not work well, but we can use the spec differ to see differences.
** Unifying vtk and matplotlib wrapping specs (WIP)
*** And porting matplotlibs spec differ to work on the general spec
*** Spec differ can then be used on vtk and other packages in the future
*** Will enable automatic upgrade generation
* [RR] Rework interpreter
** restore abstraction between interpreter/module code
** build looping, streaming, caching into the interpreter
** rework cache
** look into parallelism once basic functionality is there

=== October 14, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package] (adding numpydoc parser)

=== October 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/tree/fix-matplotlib-parser New matplotlib parser] (adding numpydoc parser)
** Added numpydoc attribute parser for plots.
*** TODO: Need better port spec reconciliation with call signature parser.
*** We can create a general numpydoc parser, but attribute types are unique to matplotlib.
** Needs package versioning
*** New spec will not support matplotlib < v1.4 due to changed path to axes classes.
*** Load spec version corresponding to installed matplotlib version?
*** Need version downgrades?

=== September 30, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Updating Matplotlib parser
** Matplotlib docstring parser fails on numpy docstrings
** I have [https://github.com/VisTrails/VisTrails/commit/eae8b0c16260810587e47c41cab53552cbb3cf0a added basic numpydoc parsing]
*** Only used by a few docstrings so far
*** Parsing uses many sources (class tables, signatures, ACCEPTS, method docstrings, definition parsing).
** Caswell said they were thinking about moving to traitlets, but this is not ready yet

=== September 23, 2015 ===
'''Updates'''
* [TE] VisTrails 2.2.3 released
** Also have pushed to PyPI, binstar, etc.
** Sourceforge vs. GitHub
*** should be able to host releases on GitHub
*** nightly binaries pushed to sf each night
*** old binaries?
* [TE] Re-wrapping MatPlotlib
** Keep static generation - Docstrings are brittle beween matplotlib versions
** Keep generating the executable classes - but create functions, not vistrails Modules
*** Why is there so much patching?
** Re-implemented Alternate PortSpec for InputPortSpec
*** It will now inherit specs from parent (No need to reimplement)
** Module upgrades?

'''Items to Discuss'''

=== September 16, 2015 ===
'''Updates'''
* [TE] Job Monitor tests and documentation done
** OK to leave document package in packages directory?

'''Items to Discuss'''
* [TE] Library wrapping: How to do code patching? [https://docs.google.com/drawings/d/1Sh3eOXot6v2y880jHKQrqXqAwr-0aoqYligg3z8G8MY/edit?usp=sharing Wrapping diagram]
** Insert code into module template (Old VTK code)
** Patch the library that is called (New VTK code)
** Somehow store code in spec and apply when executed?
*** Executed code needs at a minimum access to inputs, outputs, current class
*** Use standard input/output dict and obj reference that the code operates on?
*** Can this be done while keeping the execution abstract?

* Do new release now?

=== September 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* New release?
** [RR] wants reprounzip
** tej changes & doc
** job monitor & jobmixin fixes
** mongodb
** reprounzip
** warning: MplFigure type is int
** tabledata: add Reshape, DictoToTable & ListToTable, fix ListToTable with numpy arrays
** PythonSource can have same name for an input & output
** don't show spreadsheet at exit

=== September 2, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Limit autosaves? [https://github.com/VisTrails/VisTrails/pull/1126 #1126]

=== August 26, 2015 ===
'''Updates'''
* [TE] Added Job support to Parameter Explorations (Requested by Colin), and Mashups
** specify job ids, need to specify different ids for parameter explorations since they have the same version id
** how to deal with parameters passed in on command line
* [General] provenance: should be creating a new version when we execute workflow with changed parameters?
** currently, custom_params annotation stores this in provenance currently
** [RR] API doesn't record provenance if passing in parameters: http://git.io/vsAA5
'''Items to Discuss'''

=== August 19, 2015 ===
'''Updates'''
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [TE] Working on Job Monitor documentation

'''Items to Discuss'''
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [TE] Stop testing VisTrails 2.0?

=== August 12, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Build broken on Travis; because of IPython 4 released today? ([https://travis-ci.org/VisTrails/VisTrails/builds/75279795 build 992]; [https://github.com/VisTrails/VisTrails/issues/1123 #1123])

=== August 5, 2015 ===
'''Updates'''
* [TE] Fixes to Jobs
** Could not delete jobs
** Could not run job in group
** Job not reset when calling ModuleSuspended
** Added deleting job from context menu
* [RR] Writing documentation for everything [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

'''Items to Discuss'''

=== July 29, 2015 ===
'''Updates'''
* RR still looking into new interpreter thing
** Goal is to take out scheduling logic from Module so it can be split in multiple processes, and so that smarter strategies can be added in time
** This means some work on packages
** Spreadsheet can live in kernel process? Still some UI stuff that will take work (changing configuration, persistent archive's viewer, ...)
* [TE] Problems running examples [https://github.com/VisTrails/VisTrails/pull/1111 #1111]
** Testing of more examples requires additional packages on the test machines.
** Fixed faulty line-ending in PythonSource:s failing on Python 2.6.
** Test suite now testing SUDSWebServices (If web service is down, test suite will fail)
** preferences.py test failed reloading 'dialogs' package, switched to using 'URL'.

'''Items to Discuss'''

=== July 22, 2015 ===
'''Updates'''
* [TE] mailing lists back online
* [TE] Working on [https://github.com/VisTrails/VisTrails/issues/1107 #1107]
* [RR] Working on ReproZip package

'''Items to Discuss'''
* [RR] MongoDB package [https://github.com/VisTrails/VisTrails/pull/1106 #1106]
* [RR] Example for tej docs? [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

=== July 15, 2015 ===
'''Updates'''
* 2.2.2 released

'''Items to Discuss'''
* RR is considering executing everything in an IPython kernel (i.e. separate Python interpreter, like the one spawned for a notebook)
** It's a separate process that we can restart without restarting the app/gui
** We can isolate the execution environment (e.g. for the server)
** We can run the whole thing remotely (if your data is elsewhere, just run VisTrails locally and the pipeline elsewhere)
** Pipeline execution no longer makes the interface hang, it just makes the kernel hang (but that's fine)
** We can use notebooks as modules (probably way nicer than the PythonSource module)
** We can run multiple kernels so long as the ports carry things that are serializable
*** meaning we can put the multithreaded-interpreter without all the hacky parts it has now
*** we can run IPython kernels in all the languages IPython supports, [https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages currently 46]

=== July 8, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Buildbot github hook not working after IP address change
* [TE] No reference to VistrailsApplication ([https://github.com/VisTrails/VisTrails/issues/1103 #1103])
** [RR] Added PR [https://github.com/VisTrails/VisTrails/pull/1104 #1104]
* [TE] Reopening VT file after saving with bundled subworkflow won't offer subworkflow upgrade ([https://github.com/VisTrails/VisTrails/issues/1102 #1102])
** allow manual delete to fix right now
** fix this on top of the use-uuid branch
* [TE] Release VisTrails 2.2.1? ([https://github.com/VisTrails/VisTrails/blob/v2.2/CHANGELOG CHANGELOG])
** [https://github.com/VisTrails/VisTrails/pull/1093 output-modules-use-global-dir]
** [https://github.com/VisTrails/VisTrails/milestones/version%202.2 Current issues for 2.2]

=== July 1, 2015 ===
'''Updates'''
* [TE] PROV fixed
* [TE] Working on subworkflow issues
* [RR] Considering reworking the controller (log vs exception problem, retained upgrades causing interferences) and also the interpreter (IPython?)

'''Items to Discuss'''

=== June 24, 2015 ===
'''Updates'''

'''Items to Discuss'''
* UV-CDAT
* [TE] Can a cyclic workflow be valid? ([https://github.com/VisTrails/VisTrails/issues/1097 #1097])
** focus on disabling the ability to create cyclic pipelines because more things break than just this with a cyclic pipeline
* [RR] Relative paths ([https://github.com/VisTrails/VisTrails/pull/1057 #1057])
** This interacts with the new bundle; how do handle packing files inside the VT bundle?

=== June 17, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] current_version and reusing existing upgrades are broken ([https://github.com/VisTrails/VisTrails/issues/1095 ticket #1095])
** Could be that export to PROV is using an unflushed upgrade pipeline?
** current_version would then be correct.
** It may work to flush the actions before exporting?

=== June 10, 2015 ===
'''Updates'''
* DAT: fixed VTK issue on Linux and Mac
* Still crashes on Windows. Need help! Reminder: this works in the VisTrails spreadsheet (QCellPresenter), although no widget get changed there during a drag
** Is it a VTK bug?
** Is it simply impossible to change widgets during the drag, should we do it a different way?
** Did I miss something that is done in VisTrails but somehow not in DAT?
** Low prio, UV-CDAT doesn't run on Windows anyway

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 Updated pull request])
* Single instance code and batch mode

=== June 3, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 pr])
** Requires fixes to command line parameters, Output modules, and batch mode
** How to test this
** Updated missing/outdated flags
** Fixed view issues when generating graphs
* [TE] batch mode
** SpreadsheetOutput not enabled in batch mode. Should we check is_running_gui instead?
** Other instance setting flags from caller
** Is graphsAsPdf replacing spreadsheetDumpPdf?
** graphsAsPdf true by Default?
** Batch mode executing by default (Not needed when generating graphs)
** Re-added workflowInfo as withWorkflowInfo for writing graph and xml workflow
** [DK] batch mode should be outputting to files or stdout, shouldn't always trigger SpreadsheetMode
** execute flag, maybe make execution the default and allow a "--no-execute" if you only want to capture graphs, for example

=== May 27, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] API question
** http://lists.vistrails.org/pipermail/vistrails-users/2015-May/000357.html
* Status of DAT
** Can add VCS plot to DAT but need to work on configuration windows
** Documentation for graphics templates for UV-CDAT/vcs?
* Qt support?

=== May 20, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Reviving the DAT, integrating scripting & porting UV-CDAT!
** On [https://github.com/VisTrails/DAT GitHub] ([https://github.com/VisTrails/DAT/issues issues])
** Merging 2 years of development taking longer than expected, but getting there. The plan is to get the patches in VisTrails and never fork again, we never want to get in UV-CDAT's situation (and don't need to).
** VTK cell works fine on Linux but there was flickering on Mac & Windows before; still issues on Mac (Windows status unknown)
** Can get a VCS plot soon (but will need VTK cell fix)
** Integrate in UV-CDAT's build system (so we have cdms, VCS, ...) -> RR can do this, low priority
** How do we integrate scripting?
*** We want to be able to seamlessly make changes to a plot by changing Python code
*** Define new plots by entering Python code without writing modules/packages?
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 13, 2015 ===
'''Updates'''
* [RR] Test skipping whitelist ([https://github.com/VisTrails/VisTrails/pull/1069 #1069]) -- low priority
* [RR] Custom matplotlib modules can't be compatible with both 2.1 and 2.2 ([https://github.com/VisTrails/VisTrails/issues/1067 #1067]); should be fixed for ALPS ([https://github.com/VisTrails/VisTrails/issues/1070 #1070])

'''Items to Discuss'''
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 7, 2015 ===
'''Updates'''
* [RR] Export/import workflow to Python working!

'''Items to Discuss'''
* [Claudio] UV-CDAT
** The UV-CDAT project is the biggest user base of VisTrails
** VisTrails package management provides a lot of friction towards people plugging in their code
** Need to make it easy to integrate your random Python scripts in the system without having to deal with all the boilerplate, at least in the first step
** [RR] argues that modules are still good; UV-CDAT shouldn't move towards a purely script-based backend
** [RR] export/import with Python could reduce a lot of that friction by allowing 1) to edit workflow as Python 2) to open up boxes automatically if needed code doesn't match actual modules
** ...

=== April 29, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] <strike>Abstractions</strike> subworkflows status ([https://github.com/VisTrails/VisTrails/labels/subworkflows tickets])
* [RR] matplotlib compatibility (2.1 & 2.2), [https://github.com/VisTrails/VisTrails/issues/1067 #1067]
** RR to try and fix ALPS matplotlib modules

=== April 22, 2015 ===
'''Updates'''
* 2.2.0 has been released!
* Windows issue (via email from Ryan)
** issue with manifest file (may be a new file in VTK6?)
** Tommy has regenerated new Windows builds
* Binaries, pypi, and conda released
* [RR] Export as script
* Python sources using VTK need to switch to SetInputData (users should be aware of this)

=== April 15, 2015 ===
'''Updates'''
* Ready for 2.2.0 (apart from binary/deps issues)
** Missing some libs (scikit-learn, tej, tdparser, SQLAlchemy+connectors
** Windows: runvistrails.py is no longer used, so the PATH is wrong
** Windows: pip is broken, but it probably wouldn't work anyway because of permission issues (disable this?)
* Queries, upgrades and getPipeline() usage ([https://github.com/VisTrails/VisTrails/issues/1054 #1054])
** Getting a pipeline with getPipeline() is not safe: it might return an invalid pipeline
** This is used in many places throughout the code, like queries
** Upgrading would require going through the controller, but that creates new actions
* [TC] Avoid copying a module's output if it's used as input by exactly one downstream module ([https://github.com/VisTrails/VisTrails/issues/1060 #1060]) (useful for big numpy arrays you can update in-place)

=== April 8, 2015 ===
'''Updates'''
* [DK] Merged RR's changes for output modules (1012 and 1013)
** RR will merge remaining changes, then create v2.2 branch!

'''Items to Discuss'''
* BNL need numpy array to VTK image
** Looks like VTK has some helpers for this
** We will help if issues arise
** Will contribute back to VisTrails package
* Upgrade issue: [https://github.com/VisTrails/VisTrails/issues/1017 #1017]
** Automatic upgrades should happen between versions of provided upgrades
** Our existing upgrades work around this so it doesn't need to be 2.2.0
* Corner-case VTK modules
** No longer need VTKCell input port, so don't interfere with registry and API anymore
** Still work weirdly, people probably shouldn't use them
** But we have lots of clunky modules since we wrap the whole of VTK; some people might rely on this and know how to use them, let's keep them anyway
** Ready for 2.2.0

=== April 1, 2015 ===
'''Updates'''
* [RR] UV-CDAT: bugfixing for 2.2, long-term plans: implement scripting import/export in VisTrails, port to UV-CDAT
* Possibly, try to move to regular VisTrails to use new features

'''Items to Discuss'''
* 2.2 release: nothing much is pending anymore, release next week?
** [TE] vtkExporter classes [https://github.com/VisTrails/VisTrails/issues/1032 #1032]
** [RR] Hiding upgrades in version tree might make it (or might be 2.2.1 so we can test it out) [https://github.com/VisTrails/VisTrails/issues/949 #949]
** Output modules changes to go in
* add note to documentation about order of parameters in VTK
* add issue about exporter upgrades if not already there

=== March 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* 2.2 release
** Checklist on Github: https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist
** Review output modules
** RR has a couple more issues to fix
** Ready to go -- sign app package for OSX? [https://github.com/VisTrails/VisTrails/issues/984 #984] We need access to the Apple Membership team

=== March 18, 2015 ===
'''Updates'''
* [TE] VTK6 works

'''Items to Discuss'''
* [RR] Release v2.1.5 with backported tabledata?
** MTA example needs updated tabledata (for JoinTables)
** Google Maps package still not available
* [RR] Work torward v2.2.0?
** changes:
*** new persistence
*** API changes
*** output module changes (upgrades?), maintain cells but try to upgrade
*** not wrapping stuff
*** VTK6? yes
*** JobSubmission stuff?
*** relabeling for upgrades [https://github.com/VisTrails/VisTrails/issues/949 #949]
** makes sense, needs the tree view code to be updated, check selection
** See [https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist 2.2 checklist]
* Discussion of [https://github.com/VisTrails/VisTrails/issues/1016 #1016]
** plumbing between outputs and output modes, how to define a mode that works for many outputs without writing for each output?

=== March 11, 2015 ===
'''Updates'''
* [RR] persistent_archive done; merge? ([https://github.com/VisTrails/VisTrails/pull/755 #755])
** note about the focus events for widgets
** TE be aware of file_archive for future binaries that include persistent_archive
* [TE] [https://github.com/VisTrails/VisTrails/pull/998 New VTK package] finished

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails? (see last week; decision needed)
** RR email to JF about this
** yes; email sent to Github
* [RR] Switching order of output ports ([https://github.com/VisTrails/VisTrails/pull/1006 #1006])
** added port specs are sorted at a separate spot (Module.*_port_specs properties) than those in the registry (which are sorted in the registry), but those two lists are just combined without respect to sort keys
** need to determine whether the two lists should be merged or remain distinct
** should make sure that order of input ports and output ports makes parallel connections for things with same order
** DK suggests breaking backward compatibility here: workflows still run, can fix easily if a problem in an existing package.
* [RR] Question about output modes ([https://github.com/VisTrails/VisTrails/pull/1007 #1007]), how to integrate in API ([https://github.com/VisTrails/VisTrails/pull/24 #24])
** Should ImageFileMode be removed? ("image" is not a mode, "file" is)
** ImageOutput missing?
** Feel free to change how formats works
* [TE] Test suite segfaults on Fedora 17 virtualbox. Install newer version? (Support ended in 2013)

=== March 4, 2015 ===
'''Updates'''
* [TE] VTK wrapper
** Works on VTK 5.10
** Still need to test VTK 6
** New general wrappers for python functions and classes

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails?
** When [http://i.imgur.com/UTY2qfg.png filing a pull request] from UV-CDAT/VisTrails, VisTrails/VisTrails is selected by default
** People keep forgetting to change the default ([https://github.com/VisTrails/VisTrails/pull/956 #956] [https://github.com/VisTrails/VisTrails/pull/968 #968] [https://github.com/VisTrails/VisTrails/pull/999 #999] [https://github.com/VisTrails/VisTrails/pull/1000 #1000] [https://github.com/VisTrails/VisTrails/pull/1003 #1003] [https://github.com/VisTrails/VisTrails/pull/1004 #1004] [https://github.com/VisTrails/VisTrails/pull/1005 #1005])
** Only way to change that is to not have it marked as a fork of VisTrails/VisTrails
** Github staff [https://gist.github.com/remram44/b364c24ef1e462ce6e2f can make that change for us]; should we do it?
** Juliana: comments on this? visibility vs. convenience/annoyance for developers
* [RR] What about [https://github.com/VisTrails/VisTrails/issues/991 #991]?

=== February 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] vtkviewcell for infovis support, can we unify with VTKCell?
** need to test this
* [TE] vtk wrapping
** Mostly finished
** VTK 5.10 produce incorrect results with old wrapping
*** Old wrapper is based mostly on VTK 4
*** Most vtk_examples affected
*** [http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Replacement_of_SetInput]
*** should be able to upgrade from SetInput to SetInputData (need to drop GetOutput and replace with self ports)
*** can we change vtkInstance to just return self and not wrap things
** terminator example not working under 5.8?
* How does VTK wrapping fit into general wrapping framework?
* [RR] new persistence package

=== February 18, 2015 ===
'''Updates'''
* [RR] New VisTrails API and IPython integration ([https://github.com/VisTrails/VisTrails/pull/24 #24])

'''Items to Discuss'''
* [TE] VTK wrapping
** [https://gist.github.com/rexissimus/16b74693545b5e7c1035 Benchmarking vtk package]
*** Old: 24.7 seconds
*** New: 10.5 seconds (Except first time that adds 8 sec)
**** The parsing that calls is_abstract (that tries to instanciate all vtk classes) is now only run the first time.
**** get_items_from_sigstring takes 2 seconds, maybe we can use a lookup dict for already computed sigstrings?
** Now using a general python function wrapper
*** VTK classes are wrapped into python function that does not depend on vistrails
*** VTK functions can be executed without vistrails
*** The spec maps functions into vistrails modules, but can also describe wrapping
*** A general python function wrapper that supports
**** kwarg inputs
**** single, list, dict outputs
**** callback for progress reporting
**** temporary file generator for using FilePool
**** optional output generation
*** Creating specs:
***** Create spec by hand
***** Auto-create spec outline (TODO) and manually finish it
***** Dynamically create spec (VTK)
***** Implement documentation wrappers (Can use scikitlearn wrapper to wrap numpydoc) (TODO)
***** Classes as bad functions needs to be wrapped in new functions before they are wrapped. This is different for each package.
****** Classes is hard: Like VTK, and matplotlib. Scikit-learn does still not wrap classes
***** Spec diffing and patching could be done using code from matplotlib.
** Still needs upgrades from old VTK package
*** Is it possible to dynamically wrap functions, e.g, you see a SetFunc and just remove the 'Set' prefix. Or do you need to create a complete mapping?

=== February 11, 2015 ===
'''Updates'''
* Update from Friday's meeting
** discussed VisTrails internals
** discussed wrapping
*** xml discussion, hard to modify because tied to db code
*** TE has made it possible to add the schema-defined attributes to the intermediate representation
*** higher-level operations on the port specs
** make sure the simple case works
*** [JF] take a simple package with documentation and figure out what the base case for wrapping is

'''Items to Discuss'''
* [TE] VTK wrapping
** Dynamic loading works
** Reading XML is fast enough, but [https://gist.github.com/rexissimus/8272d3c776ccfa115d82 unserializing data is slow]
** Working on patterns for patching
** Matplotlib has many advanced patterns like argument ordering, nested arguments, alternateSpecs, output types.
*** Having all this in a general wrapper might confuse users?
** [RR] Delay module (except for identifiers) until you need it---e.g. don't deal with port specs, etc. until necessary
* Scripting Support [https://github.com/VisTrails/VisTrails/pull/950 #950]
** [RR] Issue with getting code from modules
** Design a simple solution
** [JF] Couldn't you use modules as black boxes without conversion, just to call into modules/subworkflows easily from e.g. IPython?
*** [RR] This is a job for the API, and a very separate use case. See [https://github.com/VisTrails/VisTrails/pull/24 #24]

=== February 4, 2015 ===
'''Updates'''

'''Items to Discuss'''
* Wrapping
** Format to use? Currently XML (like current matplotlib)
*** JSON and YAML have simple "to python dictionary" methods
*** But don't stream
*** YAML a lot easier for humans
** [DK] vtk-new-package also changes parameter names, creates enumerations
*** intermediate schema needs to be extensible
*** packages will want to store there specific infos for compute() method generation
*** also might have specs-altering info, like matplotlib's alternateSpec
** representation to code , registry already has schema for some aspects
** [RR] We might want to see if Module subclasses can be created lazily
*** no need to create all the classes just to register them in the registry and never actually use most of them
*** future effort
* [RR] Where should VisTrails packages live?
** tej installs as 'vistrailspkg.tej', TE installed it as 'userpackages.tej'
** Currently, standard packages are 'vistrails.packages.', user packages are 'userpackages.' and packages loaded through pkg_resources might be anything
** [RR] Use 'vistrailspkg.' everywhere?
** Long-term effort to simplify package distribution/installation (and have VisTrails get them automatically?)

=== January 28, 2015 ===
'''Updates'''
* T. Caswell to come visit on Fri 6 to discuss wrapping work

'''Items to Discuss'''
* [TE] New VTK wrapping
** Current code by DK seems a good deal faster
** Generates XML that can be patched/tweaked, generates Python code from it, VisTrails only loads generated Python code
** RR would rather have VisTrails load intermediate representation (= XML) directly, wants to make sure this is not slower
** The goal is to turn the intermediate step into something generic that would be used for every wrapped package (vtk, numpy, matplotlib, sklearn, java) instead of each having its own
** TC has its own code at [https://github.com/Nikea/VTTools/blob/master/vttools/wrap_lib.py github:VTTools] which parses numpy docstrings and generates modules, doesn't yet handle classes or persist anything
* Web crawler
** Right now, TE starts jobs for "start crawler", "stop crawler", "install classifier"
** RR would rather have the crawling be a job as far as VisTrails and tej are concerned
** The whole thing would be one pipeline: load examples, train classifier, start crawler [check for job, kill previous one, upload model, start processes], get snapshot, visualize
*** Need some support in tej and job submission system: long-running jobs, stop a job (wait for it to finish?), restart a job even though results are cached

=== January 21, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Unified wrapping method discussion [https://github.com/VisTrails/VisTrails/issues/991 #991]
** TE to work on reusable method with intermediate representation, starting with VTK
* [RR] Examples for scikit-learn: JF has an old example using Weka with parameter exploration (not currently in source tree)
** AM's examples are enough
* [AM] scikit-learn package is done, merge it in? [https://github.com/VisTrails/VisTrails/pull/955#issuecomment-70286788 #955]
** RR will merge
* [RR] What should copyright headers say? [https://github.com/VisTrails/VisTrails/pull/994#issuecomment-70173935 #994]
** Let's keep everything in there: Utah/Poly/NYU

=== January 14, 2015 ===
'''Updates'''
* [TE] Working on classifier
* [RR] Scripting integration, work in progress

'''Items to Discuss'''
* [RR] Unified wrapping method discussion ([https://github.com/VisTrails/VisTrails/issues/991 #991])
** Let's talk next week, [AM] and [DK] are not here

=== January 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* make sure that we address critical issues, questions, and pending review branches in a timely manner
* scripting support
** [RR] no issues if we want to just keep annotations in the generated code to allow the link back to a workflow
** [RR] can translate from workflow to script, working on script to workflow
** will work for parameter value changes, structural changes require changes to the annotations
** need to publish best practices here
** would be cool to do looping in scripts (easier interface than with workflows)
* notebook support (convert form notebook to workflow)
** RR will sync with FC on this
* Issue with console in built-from-scratch
** [TC] iPython rearranged some of the completion stuff in 2.2 and 2.3
** binary has old version of iPython -> 1.0.0, should we update?
* [TC] automated wrapping of numpy and scipy
** discovered a bunch of malformed documentation in numpy and scipy
** has github repo for vistrails tools
** example modules wrap a bunch of R stuff (not baked in, just how things are)
** will be pushing wrapping logic up
** port names forbidden (window and domain)
** have an import hook to get from yaml directly to VisTrails Modules
** should work for any python modules with well-formed numpy docstrings.
* [Action] should make it clear in documentation that Constant now means serializable not that the value doesn't change (e.g. List)
* [TC] might be interesting to try to build components of matplotlib and accumulate in figure (long-term project, but thinking about how this might work)
* [TE] build and build scripts
** completely automatic, buildbot
** need to set the build machines for the environment we want for the binary
** would virtualenv work here?
** [TC] anaconda can pin versions, potential path to test different configurations
** Q: upload nightly binary builds? A: makes sense, make sure they are well-labeled
* sourceforge stats: e.g. http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07
* package issues (see Remi's message)
* [TE] Scope of tej
** Support single ssh commands?
** Queue can be used as a remote machine (crawler is using queue.call*)
* SourceForge stats: http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07

== Older meetings ==
* [[Development/2014]]
* [[Development/2013]]
* [[Development/2012]]
* [[Development/2011]]
* [[Development/2010]]

Development

2016-08-03T15:02:21Z

Tommy: /* August 3, 2016 */

<div class="nonumtoc toclimit-1">
__TOC__
</div>

See also the [https://github.com/VisTrails/VisTrails/wiki/Development Github wiki]

== 2016 ==
=== August 3, 2016 ===

'''Updates'''

'''Items to Discuss'''

* [TE] Wrapper patches now stored as [https://github.com/VisTrails/VisTrails/blob/python-wrapper-script-patches/vistrails/packages/vtk/vtk_wrapper/vtk_patch.py python code]
** Connection variables now lowercase
** Can we use code as output variables?
*** E.g. "vtk_dataset_mapper.GetOutput(0)"
*** Could mutate output when output method is only supposed to be called once
*** Need to be able to rename output port as python code(e.g. when there are 2 "vtk_dataset_mapper"s)

=== July 27, 2016 ===

'''Updates'''

* [DK] DB bundle serialization implemented

'''Items to Discuss'''
* [TE] Finished using patch in script [https://github.com/VisTrails/VisTrails/tree/python-wrapper-script-patches python-wrapper-script-patches]
** locale?
** [https://gist.github.com/rexissimus/f0d6b026aa5a2a770847f3321744645d new patching example] vs [https://gist.github.com/rexissimus/b28d83ae516a519167f5751bb8ab3739 old patching example]
** [https://github.com/VisTrails/VisTrails/blob/python-wrapper-script-patches/vistrails/packages/vtk/vtk_wrapper/parse.py#L135-L273 Example of new patches]
** Legacy '.vtkInstance' is now added as a patch "self.vtkInstance=self" (see new patching example)
** [https://github.com/VisTrails/VisTrails/blob/python-wrapper-script-patches/vistrails/core/scripting/api.py New api for executing standalone modules]
*** Accessing module was disabled for core/api, but a different api for this is probably better anyway.
*** api.Package now gives [https://gist.github.com/rexissimus/f0d6b026aa5a2a770847f3321744645d#file-new_patching-py-L26 directly callable module compute functions]
*** Only works on modules not using interpreter functionality ('.interpreter', etc.)
**** for zip file modules and others that need temp files and use the interpreter for this, need to modify the module, but could work around with python libraries for managing temp files
** Fixed more renaming issues - [https://github.com/VisTrails/VisTrails/blob/python-wrapper-script-patches/vistrails/core/scripting/scripts.py#L63-L64 function argument names should not be replaced]
** Still need to do something nicer for the patch formatting
*** patch keys currently contain non-python-variable characters but this can be fixed
*** Need to replace string template with python variables that is replacable using RedBaron
**** Patches could then look like:

def vtkInstance():
self.vtkInstance = self

=== July 20, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] New patch method for python-wrapper [https://gist.github.com/rexissimus/009b303e4cadcd4b8f2fec6cf848cb2b example]
** A patch is a string template with self/input/output variables for patching a class method
** Patches are stored in xml specification
** Patches are assigned to methods in ClassSpec's
** Used both for execution in vistrails and when exporting as script
*** Executed with "exec" when run in vistrails
*** Turns patches into natural calls in script
** Wrapping VTK library no longer needed
*** Removes ".vtkInstance" (Automatically removed from PythonSources and vtkInteractionHandlers)
** Removed fix_classes.py (Subclassing of VTK classes to patch methods directly)
** Also used for port translations (With patch names like "basic:Color#input") (No more ugly input_t method definitions)
** TODO's
*** Add to export_as_script
*** Patch Modules that represent Python functions as well

* [vistrails-users] Read data from SQL example?

=== July 13, 2016 ===

'''Updates'''

* [DK] bundles on sql-alchemy branch
** Bundle, BundleMapping, and BundleSerializer
** New BaseSerializers to deal with versions of directory, zip, db serializers
** Can register the BundleSerializers with the base serializers
** Translation between bundle versions
** Bundle.add_object "just works" if an appropriate mapping was registered

'''Items to Discuss'''
* [TE] Simplified running module using API for scripting [https://gist.github.com/rexissimus/b28d83ae516a519167f5751bb8ab3739 example]
** API Module can be executed using '''compute''' method
*** Takes list of outputs to compute + inputs as keyword arguments
* Status of general cell synchronization (vistrails-users)

=== July 6, 2016 ===

'''Updates'''

* [DK] Working on bundles

'''Items to Discuss'''
* [TE] Using vistrails API in scripting [https://gist.github.com/rexissimus/034d9c4dedc3299a079e84981dedd8c7 example 1 (API with VTK)] [https://gist.github.com/rexissimus/a4a9ca6c08d4058c64967d2b35415fd5 example 2 (DownloadFile only)]
** Call module in script using vistrails API
** Can be used when no export method is defined.
* [TE] [https://github.com/VisTrails/VisTrails/commit/c76c109349769fee1280f85c22678380a2f9cd39 Server news bug] Critical?
**[RR] No, unreleased
* [DK] New bundle organization
** BundleMapping contains individual mappings from raw objects to BundleObj
** Must be separate in order to have in-memory, separate from serializer settings

=== June 29, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Export VTK as python script
** Works on Terminator (Isosurface, Volume Rendering, clipping plane, combined rendering) [https://gist.github.com/rexissimus/16caf5200802e150296f62a0c7844c5a example]
** Preludes (imports) still need improvements
** Works with vtkInteractionHandler (clipping plane)
** Resulting clipping plane is incorrect? (supposed to hide one side of the plane)
** vtkRendererOutput Uses VTKRenderWindow as output
*** Should support different output modes?
*** Does not work with multiple outputs (Next cell is displayed when current is closed)
*** Uses wrapped vtkInstance (as vvtk)
**** Create new patch system with code that can be used both in vistrails and in a python script?

=== June 22, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Fix for upgraded analogies (PR [https://github.com/VisTrails/VisTrails/pull/1177 #1177])
** Uses module location to find module remap (The best we can do right now?)
** Also fixes remapped port names for connections to existing modules
** May still fail on complex upgrades like adding a function on an upgraded module that has a different port name

* [TE] Working on exporting wrapped libraries (VTK)

=== June 15, 2016 ===

'''Updates'''
* [TE] Added depth logic to python script exporter ([https://github.com/VisTrails/VisTrails/commit/50f220e4f6abe5a7bb8689f73f456f43df2dbc12 full commit])
** Fully implements connection merging and list looping

'''Items to Discuss'''

* [TE] Making analogy work on upgraded workflows ([https://github.com/VisTrails/VisTrails/issues/1175 #1175])
** Analogy only works We need to use the non-upgraded action chain
** But pipelines need to be valid (matcher uses module portspecs)
** Tried to get upgrade remap from upgrade action, but this seems impossible
** Use module location instead?
*** Location should be identical for one-to-one module upgrades

=== June 1, 2016 ===

'''Updates'''
* VisTrails 2.2.4 announced (finally)
** 5 survey replies
** 47 downloads last week

'''Items to Discuss'''
* [TE] Export VTK as script (python-wrapper)
** to_python_script
*** needs the pipeline (or at least the connections)
**** Should not generate code for any possible VTK method (exporter detects which ports is used in the source)
**** VTK needs to know connection order
**** Adding functions directly to the script results in nicer code
** Add support for multiple input connections
** Add support for list looping

=== May 25, 2016 ===

'''Updates'''
* Mailing-list fixed
* Getting stats from the "server news" mechanism (via [https://github.com/remram44/apache-log-info parser])

'''Items to Discuss'''
* [RR] Alexis doing writeup on VisTrails, curious about interesting streaming use-cases (and potential future users)
* [TE] Union ports
** Show union ports in pipeline (DEMO)

=== May 18, 2016 ===

'''Items to Discuss'''
* [TE] mailing list still down - Julio working on it
* [TE] Improved union port
** New schema 1.0.5 adds portitem.union string attribute
** Works with pipeline view, parameter exploration view, and mashup view
** Should work well for matplotlib
** Use with VTK ports?
*** It uses [item_1,item_2] style ports usually with different tuple length.
* [TE] Remove emacs dependency from db generate [https://github.com/VisTrails/VisTrails/issues/1173 #1173]

=== May 11, 2016 ===

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]
** GUI-based solution [https://github.com/VisTrails/VisTrails/tree/union-port Branch union-port] Demo?
*** Shows single port for all ports with same sort_key
*** Select specific type when adding/showing
*** Only one type should be visible on the module at any time
*** Making tuple parameters union types is probably too complicated
*** Should work with alternate specs like matplotlib (if sort_key is defined correctly)

* [TE] Feature suggestion: Let connections connect to functions/parameters
** Show functions and parameters as ports and toggle port visibility directly for functions and parameters
** Use separate views for ports and functions (like before)
*** Allow rearranging of functions
** Pros:
*** Supports ordered connections. Create 2 functions, make them visible as ports, make connections to them.
**** We can also have, e.g., a line joining the ports on the module to indicate they are part of a list.
**** Makes List module simpler
*** Connect to parameter in tuple
*** Functions that are visible on the module can connect to an actual function, and not just to the first one it finds.
*** Can replace operation modules (in python-wrapper) in some cases for, e.g., numpy.
** Cons:
*** Interface more complicated and crowded
*** More difficult for users to grasp?
*** No immediate use case
*** Makes no union type for tuple parameters a bigger problem.

* [TE] Publish user survey?
** No response from vistrails release yet
** Not announced on vistrails-users yet.

=== May 4, 2016 ===
'''Updates'''
* VisTrails 2.2.4 released

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]

=== April 27, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Wrapping Bokeh
** New method type "operation"
*** Transforms Figure->Glyph->Output into Glyph->Figure->Output
**** Glyph sets function name and arguments as output
***** Not serializable, but should always be computed together with the subject of the operation.
**** Figure applies Glyph operation on itself
*** Useful for matplotlib?
**** matplotlib currently find actors by searching upstream?
**** But this is more difficult since matplotlib is not function-based.
** New "union" port type
*** Turns "x(float), x(list)" into "x (float, list)" and uses first set value
**** Uses only first value in tuple
**** Bokeh have many properties that support (list, string, Float)
*** Does not work with depth=1 types (e.g. Float of depth 1)
**** Turn Depth 1 types with known type into lists?

* [TE] New bugfix release
** Finalize survey

=== April 20, 2016 ===
'''Updates'''
* Merged upgrade fixes
** Now has infinite loop test
** loop test now correctly loops 5 times
*** remap_module used wrong (current) package version when creating ModuleDescriptor
* Fixed multi-step group upgrades (PR: [https://github.com/VisTrails/VisTrails/issues/1168 #1168])

'''Items to Discuss'''
* New bugfix release
** Merge usagestats
** Need to finalize survey

=== April 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Chaining upgrades done ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Replace "Upgrade" description annotation with "upgraded_from" annotation to identify which tags to hide?

* [TE] Iterating handle_invalid_pipeline ([https://github.com/VisTrails/VisTrails/pull/1165 #1165])
** Not based on [https://github.com/VisTrails/VisTrails/tree/chain-upgrades-loop chain-upgrades-loop]
** Cherry-pick test to preserve source?
** Need maxPipelineFixAttempts option?
*** The code is now smarter about recursion, so max attempts will "probably" never be reached.
** Need [https://github.com/VisTrails/VisTrails/commit/0ef0667426937eddb1d1c1e397f0657ffec039a9 debug messages]?
*** Would need to be moved into handle_invalid_pipeline

=== April 6, 2016 ===
'''Updates'''
* [TE] Query View improvements
** Done except for displaying "Version Info" and #1164
* [RR] Working on finishing new interpreter (finally!)

'''Items to Discuss'''
* [TE] Chaining upgrades ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Try latest upgrade first, then previous.
** If all fail, select latest upgrade?

=== March 30, 2016 ===
'''Updates'''

'''Items to Discuss'''

* [TE] Query View improvements
** Unified do_version_switch and get_upgrades as validate_version()
** Problems with query view using its own controller
*** Fixed module info not being displayed for query results
*** Still no version info for query results
*** Still an issue with version query view not being updated

=== March 23, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Usage reporting almost ready to go
** Need to record whether specific features are used: paramexpore, mashup, query
*** [DK] Record if LaTeX extension is used? But hard to distinguish from direct batch invocation
** How to record size of vistrail?
*** [DK] IdScope already walks over vistrail, use that
*** but total number of modules and versions doesn't give an idea of average size of individual pipelines

=== March 16, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Upgrades in Query Mode
** Now using code similar to do_version_switch
*** Uses handle_invalid_pipeline
*** Differences: Not using current_pipeline, flushes changes
*** New controller method get_pipeline optimized using cached pipelines (but not current_pipeline)
*** Integrate to avoid repeated code?
*** Use this for query mode?
* [TE] VisTrails 2.2.4 ready for release?
** tej package updated. Others?
* [JF] upgrades and the version tree
* [JF] provenance in Jupyter
* [DK] bundles: [https://github.com/VisTrails/VisTrails/pull/1092 #1092]

=== March 9, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixing search mode
** String query now matches all by default
*** This caused pipeline queries to never match
** String query can search: User/Notes/Tagname/Time/Module name
*** Should we search module names by default? (Disabled by default because it is expensive)
*** Fixed notes search
** '>' parameter queries in documentation but has been removed
** Fixed module matches for upgraded pipelines (By not upgrading pipeline)
*** Upgrades still a problem
*** Add "Upgrade all menu option?" (Or upgrade all on open when `hideUpgrades`)
*** [JF] Allow search on past tags

* [TE] Create new bugfix release
** Finish querying
** Path issue on windows

* [DK] Look into sqlalchemy and new bundle branches

=== March 2, 2016 ===
'''Updates'''
* [TE] Fixed cache bug with port specs
* [TE] VisTrails Next
** Most packages now work
** No qgis for Python 3

'''Items to Discuss'''
** Always dereference symlinks? [https://github.com/VisTrails/VisTrails/issues/1146 #1146]

=== February 23, 2016 ===
'''Updates'''
* [TE] Fixed PythonSource 100% CPU bug
* [TE] VisTrails Next
** Updated [http://opendap.co-ops.nos.noaa.gov/axis/webservices/wind/ NOAA Web Service] examples
*** Now uses REST service, tabledata, and Google Maps
*** Web Service replaced with DownloadFile

'''Items to Discuss'''
* [RR] Couple of fixes are in for API, and tej&reprounzip on the Mac binary. Also new release of tej, and working on anonymous usage reports.
** New 2.2 release soon?
* [RR] Anonymous usage reports
** Sends out info like number of modules & versions, packages used, Python & libs versions, execution time, specific features [https://github.com/VisTrails/VisTrails/pull/1154 #1154]
* [JF] Bring in noWorkflow to track variable dependencies, for the considered Jupyter integration?
* noWorkflow - provenance for python scripts
** Recent work on tracking dependencies
* Also integrates ReproZip with Jupyter
** [http://mybinder.org mybinder]
*** Use with ReproZip to automatically build Jupyter notebook interfaces
* Daves comments on Jupyter integration
** It is possible to identify cell order on the server side
** Not trivial to track order of cells on client side
* How does Galaxy workflows relate to VisTrails?
** Packaging in Galaxy is hard
** Galaxy for biomedical workflows, difficulty making it general
* Action items
** How difficult to track cell dependencies in Jupyter notebooks?
** Use noWorkflow to track cell dependencies?
** How difficult to modify mybinder to use ReproZip packages?

=== February 17, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixed Group memory usage
** Modules in groups are supposed to be freed when done executing
*** Prevented by logger that stored references to the modules (fixed, now using id(module))
*** Prevented by list iterator bug that stored list of modules on the 'self' port bug (fixed)
* [TE] VisTrails Next
** Removed deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** PythonSources will be upgraded
*** Fixes for Python < 3
*** fixes for VTK < 6
** TODOs
*** Remove RemoteQ
**** Port Hadoop to tej (Already have pbs)
*** Merge package wrapper
*** Finish SQLAlchemy branch
*** Finish new bundle branch
** [JF] Will contact Jeff and Matthias about moving to Python 3
* [JF] Query by Example is broken
* [JF] VisTrails Data Cleaning Project
** Use VisTrails to process and explore task-specific data while keeping provenance.
** Remi's Idea
*** Use VisTrails as the backend in a Jupyter notebook
*** Overcome problems with executing cells in random order
**** Interesting research topic, but little interest has yet been noted
*** Interesting to study how such a notebook would be used (Is there notebook usage data available?)
*** Impose restrictions to notebook cell boundaries
*** It will only work for functional operations
*** Can we fix, or detect, non-functional (mutating) operations?
*** Analyse code and data flow and see if it mutates data in unexpected ways?
*** Mutable operations can be created in many ways in Python
* Next meeting Tuesday 11:30

=== February 10, 2016 ===
'''Updates'''

'''Items to Discuss'''
* VisTrails Next
** Test suite passes
*** Python 3 less deterministic, module upgrade order random.
** [RR] updating packages: Reprounzip (pushed), tej, persistent_archive, ...
** All of our packages should run fine :)
** VTK thumbnail comparison works
*** Rendering bug on some systems
**** QVTKCell now inherits QGLWidget
*** Old thumbnails had wrong height due to spreadsheetwindow being too small
**** Fixed by regenerating thumbnails
*** Silenced deprecation messages when generating modules
*** Many new classes in VTK 7
** Remove deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** Will break existing PythonSources
**** Try to upgrade?
*** Old-style packages
**** Or only allow a new style, like __init__.py renamed to info.py? (merge with identifiers.py?)
***** Read info.py without importing package?
*** Fixes for Python < 3
*** Fixes for Qt < 5
*** fixes for VTK < 7
*** Remove self port?

=== February 3, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] [http://lists.vistrails.org/pipermail/vistrails-users/2016-January/000402.html Rendering a .pvd (ParaView) file?]

* VisTrails Next
** All tests but thumbnail comparison passes
** Still issues with gui and more packages needs to be tested
** PythonSource and MplSource upgraded with lib2to3
** Keep contrib packages? Update?
** [https://blog.kitware.com/vtk-7-0-0/ VTK 7 is released]
*** Supports Python 3
*** Will hopefully get into conda and others soon
*** Deprecates a bunch of modules

* [https://travis-ci.org/VisTrails/VisTrails/builds/106743348 Travis builder] for VisTrails Next
** Runs!
** Uses conda
*** Many levels of requirements
**** apt packages
**** conda packages
**** python packages in requirements.txt
**** python packages in setup.py
*** Can probably drop conda. Default builder does not have Qt5, but beta builder do!
*** But useful if we want to use conda in our own build process.
** Lots of errors I do not get locally?

* [http://goo.gl/forms/Z4HBrwaBWL User Survey]
** Have you used any alternatives to vistrails?
*** Relevant? More options?
** How often do you use any of these particular features in VisTrails?
*** Add/Remove alternatives?
** How important would you rank the following potential improvements to VisTrails?
*** Add alternatives?

=== January 27, 2016 ===
'''Updates'''
* New interpreter
** Working prototype soon
** Looping not completely done (and port combination mode: pairwise/cartesian...)
** Need to integrate with VisTrails
*** Compatibility with existing modules
*** Use log controller
*** Want to cache at multiple levels (whole stream/single element of stream)
*** Non-runtime attributes of modules (cache check, automatic conversion check, constant from/to string)

'''Items to Discuss'''
* User Survey

* ZMQ failing on windows (vistrails-users)

* [TE] [https://github.com/VisTrails/VisTrails/pull/1143 Python 3 branch]
** Testsuite almost passes
*** Failing are unicode filenames, some users guide examples, and thumbnail comparisons.
** Fixed issues
*** Signatures are now bytes (convert to string to show in widget)
*** Cannot compare different types, e.g., (None < 1)
**** PortSpec.depth and min/maxConn could be None. (Backport!)
**** cell.row could be None
*** Lots of unicode/bytes fixes to serializations
**** We have encryption implementations in the code! (keychain)
*** Lots of small fixes to package method differences
** Current issues
*** logging widget empty?
*** version tree signals messed up
*** provenance view legend icons black
*** Text do not fit in some widgets
*** VTK thumbnail comparison fails
**** VTK Cells have some faces in wrong direction?
**** Because running in VM?
** Installing on Ubuntu LTS/Latest Mint
*** Install latest matplotlib from pip
*** Install VTK 7.0.0rc2 from source
*** No QtWebEngine binary (controversial) (Must install sip/PyQt5/Qt5 from source)

=== January 20, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Backporting features from Python 3 + PyQt5 + Qt5
** Merged unicode with master ([https://github.com/VisTrails/VisTrails/tree/unicode unicode])
*** One unicode test failing
*** Problem saving to xml
** Used [http://python-future.org/ python-future] to run futurize stage 1 to update legacy (pre 2.6) code ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized unicode-futurized])
*** Updates print to functions 'from __future__ import print_function'
*** Updates exception calls to use 'as'
*** removes most usages of 'long' (mostly used unnecessarily)
**** Only needed for 32-bit support
*** Fixes relative imports (from __future__ import absolute_import)
** Fixing code that is deprecated in Qt 4.8 and removed in Qt 5 ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized-qt5 unicode-futurized-qt5])
*** Updated all signals to new-style
* If we go 2 to 3, this could break packages
** means we should schedule any package format changes for the same time
** e.g., imports should be unrelated to code path (function to load module from package identifier?) (take them out of vistrails.* [https://github.com/VisTrails/VisTrails/pull/1002 #1002])
** any structural changes (e.g. the __init__ versus init thing) (RR thinks it makes sense, though having both named "init" is unfortunate)
** putting package identifier as xml?
*** Python not so bad, plus some stuff in there is Python code (checking dependencies)
** version the APIs?
*** RR planning on versioning vistrails_module.Module, no point versioning the whole package?
* file formats on 2 to 3:
** no real translation/upgrade, but non-ascii values that work on 3 won't load in 2

=== January 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://gist.github.com/rexissimus/dfd27e466427529c385c Porting to Python 3 / PyQt5]
** Basic GUI and execution works
** Minimal work to support 2to3
** Hard to support both PyQt4 and PyQt5

=== January 6, 2016 ===
'''Updates'''
'''Items to Discuss'''
* Updating VisTrails dependencies
** Successfully built [https://gist.github.com/rexissimus/f1a1aada7de1c00a57c7 Win7-64/Python3/PyQt5/Qt5/WebEngine/VTK7]
*** VTK 7 is the first supporting Python 3 but is only in release candidate phase.
**** Next version of VTK 6 is rumored to support Python 3
**** There is a development branch of VTK 6 supporting Python 3
*** Can travis build this?
**** We can skip tests for WebEngine and VTK if needed
** Python 3 [https://python3wos.appspot.com/ showstoppers]
*** No MySQL-python (sqlalchemy supports mysql through other drivers)
*** No suds (there are active forks but we could also drop support?)
* Options for python2/3 support:
** Interpreter could be python2/python3 based on packages
** six layer works but not the easiest to maintain (e.g. in reprozip)
* Drop support for win-64
* Update copyright headers to 2016

== 2015 ==

=== December 30, 2015 ===
'''Updates'''
* Bokeh package finished
** Can output to Browser/IPython/Spreadsheet (Limited functionality in spreadsheet)
'''Items to Discuss'''
* Updating VisTrails dependencies
** Bokeh needs QWebEngine (Chromium) in Qt5 which requires PyQt5
*** Many plotting libraries only work in browsers
*** But Chromium may be a big and controversial dependency
*** Or create a browser version of the spreadsheet?
** Some users have requested Python 3
** Not backwards compatible?
** Target for VisTrails 3.0 with new interpreter?

=== December 16, 2015 ===
'''Updates'''
'''Items to Discuss'''
* Users list question
* [TE] Wrapping Bokeh
** Added bokeh property parser
*** complements numpydoc parser
*** Not all attributes are available, partially because I am using a pre-release version.
** Wrapped modules
*** bokeh.plotting finished (Backwards like matplotlib: Create plot then draw on it)
*** bokeh.charts mostly done (Missing arguments)
** QWebView mostly works (but no zooming or buttons)
*** It would be better to use external browser or QWebEngineView
** Added improvements to wrapper
*** Generalized port translations (Color/Path to native types)
*** Can use multiple docstring/property parsers simultaneously

=== December 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Looking into wrapper
** Will port TensorFlow
** Doing a pass on the wrapper code & doc
*** UX improvements
** Factorize high-level docstring parsers into core.wrapper? (sphinx, numpy, google)
** Problem with name vs module_name (fails sklearn tests because class_by_name() is broken)
** Looking into compressing specs, lazy registration of modules

=== December 2, 2015 ===
'''Updates'''
* [TE] Package wrapping
** Wrapped most of numpy/scipy using __all__
** Added class attribute and method access for classes (Can add to class or to separate inspector module)
** TODO: Document wrapping procedure

'''Items to Discuss'''

=== November 25, 2015 ===
'''Updates'''
* [RR] New interpreter is coming along
** Everything is a stream
** Task system, eventually work-stealing parallelism
** Streams no longer advance in lock-step
*** Allows for constructions like filter, join, sorted-merge
** depth>1 still to be tested, no current plan to allow this through the module interface
*** Through looping though, can do streams of streams

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapped most numpy functions (no polynomials)
** and half of scipy classes and functions
** Added functions manually from documentation (no parseable lists?)
** Focusing on data flow constructs (no property/method access for classes)
*** Using spec diff (empty for now) and dynamic parser (stores spec in .vistrails/)
** Python class/function wrapper now stable
** Add google doc parser?
*** Is there a parser available?

=== November 18, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Numpy class wrapping works
*** Basic type is List, since most types are array_likes.
*** TODO: More classes and functions
*** Some operations are in-place and some aren't, and docstring not super clear
*** [RR] It seems only methods mutate, and most have a numpy.xx function equivalent; just manually go through the methods and remove the mutating ones?
** Class wrapper is modular
*** Docstring parser and type string parser can be customized
*** Classes can have optional attribute/method ports
**** Inspectors and attribute/method modules can be created separately
** Use PythonCalc as an example
*** Can be re-implemented as a function with a parseable docstring
*** [RR] PythonCalc is just an example, and it might actually make sense to get rid of it, or do a proper math package with scalar operations (as separate modules, no combobox)
** [RR] TensorFlow to use wrapping as well
*** Very simple (only types 'tensor' & 'variable')

=== November 11, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapping numpy's classes using numpydoc (ndarray)
*** Wrapping constructor arguments, attribute getters/setters as module ports
**** Then how to access attributes afterwards?
***** Use input value port to class modules?
*** Wrap methods as modules? E.g., `ndarray.shape`.
*** Function wrapping is almost a subset of class wrapping
**** May be able to use the same parsing/execution methods
** VTK's non-getter/setter methods could be wrapped as modules
*** We could then remove extra logic in interpreter for keeping function order
** Bokeh uses autogenerated docstrings
*** We may be able to read the specification directly

* [RR] [https://github.com/VisTrails/VisTrails/pull/1138 TensorFlow package]
** Basic setup working, can execute the Mandelbrot example
** Will autogenerate the operations

=== November 4, 2015 ===
'''Updates'''
* [RR] Interpreter work requires a fix for [https://github.com/VisTrails/VisTrails/issues/1137 DB issue #1137]
* [DK] Kitware's Resonant [http://www.kitware.com/source/home/post/173]
** [https://github.com/girder/girder Girder]: data management system
** [https://github.com/Kitware/romanesco Romanesco]: execution engine, uses [http://www.celeryproject.org/ Celery] for task management
** Resonant Flow: web app for editing and executing workflows

'''Items to Discuss'''
* [TE] Added OSX Lion (10.7) VM on build machine using vagrant (seems ok with license?)
** New builds works on Lion
** Change the minimum requirement to 10.7?
* [TE] Package wrapping
* Added upgrade suggestions using 2 spec versions ([http://pastebin.com/30XUU8Gp example])
** using name edit distance to find matches
** Could use something better like port similarity for modules, and type similarity for ports
** Should write python upgrade code?
** Added spec to sklearn package
*** Can now diff spec versions and keep the spec static
*** There will be problems with downgrades and package versions

=== October 29, 2015 ===
'''Updates'''
* [TE] nightly-build-mac fixed (Needed to approve xcode license)

'''Items to Discuss'''
* [TE] matplotlib wrapper
** ported to general spec
** Diff can be used on general spec
*** Only needed minor changes
*** Fixed indexing bug that corrupted specs
*** Can now move diff tools to core/wrapper
** Add new plots?
*** New plots in mpl 1.3: eventplot
*** New plots in mpl 1.4: angle_spectrum, magnitude_spectrum, phase_spectrum', violinplot
*** No new plots in mpl 1.5 (from looking at boilerplate.py)

=== October 21, 2015 ===
'''Updates'''
* [RR] Alexis has arrived, will be working with [RR] on a more efficient interpreter

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package]
** Supporting multiple package versions
*** Check which version can be loaded [https://github.com/VisTrails/VisTrails/pull/1135 #1135]
*** We cannot show version requirements in the list of packages because old packages are loaded when importing the codepath
** Visual diff does not work well, but we can use the spec differ to see differences.
** Unifying vtk and matplotlib wrapping specs (WIP)
*** And porting matplotlibs spec differ to work on the general spec
*** Spec differ can then be used on vtk and other packages in the future
*** Will enable automatic upgrade generation
* [RR] Rework interpreter
** restore abstraction between interpreter/module code
** build looping, streaming, caching into the interpreter
** rework cache
** look into parallelism once basic functionality is there

=== October 14, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package] (adding numpydoc parser)

=== October 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/tree/fix-matplotlib-parser New matplotlib parser] (adding numpydoc parser)
** Added numpydoc attribute parser for plots.
*** TODO: Need better port spec reconciliation with call signature parser.
*** We can create a general numpydoc parser, but attribute types are unique to matplotlib.
** Needs package versioning
*** New spec will not support matplotlib < v1.4 due to changed path to axes classes.
*** Load spec version corresponding to installed matplotlib version?
*** Need version downgrades?

=== September 30, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Updating Matplotlib parser
** Matplotlib docstring parser fails on numpy docstrings
** I have [https://github.com/VisTrails/VisTrails/commit/eae8b0c16260810587e47c41cab53552cbb3cf0a added basic numpydoc parsing]
*** Only used by a few docstrings so far
*** Parsing uses many sources (class tables, signatures, ACCEPTS, method docstrings, definition parsing).
** Caswell said they were thinking about moving to traitlets, but this is not ready yet

=== September 23, 2015 ===
'''Updates'''
* [TE] VisTrails 2.2.3 released
** Also have pushed to PyPI, binstar, etc.
** Sourceforge vs. GitHub
*** should be able to host releases on GitHub
*** nightly binaries pushed to sf each night
*** old binaries?
* [TE] Re-wrapping MatPlotlib
** Keep static generation - Docstrings are brittle beween matplotlib versions
** Keep generating the executable classes - but create functions, not vistrails Modules
*** Why is there so much patching?
** Re-implemented Alternate PortSpec for InputPortSpec
*** It will now inherit specs from parent (No need to reimplement)
** Module upgrades?

'''Items to Discuss'''

=== September 16, 2015 ===
'''Updates'''
* [TE] Job Monitor tests and documentation done
** OK to leave document package in packages directory?

'''Items to Discuss'''
* [TE] Library wrapping: How to do code patching? [https://docs.google.com/drawings/d/1Sh3eOXot6v2y880jHKQrqXqAwr-0aoqYligg3z8G8MY/edit?usp=sharing Wrapping diagram]
** Insert code into module template (Old VTK code)
** Patch the library that is called (New VTK code)
** Somehow store code in spec and apply when executed?
*** Executed code needs at a minimum access to inputs, outputs, current class
*** Use standard input/output dict and obj reference that the code operates on?
*** Can this be done while keeping the execution abstract?

* Do new release now?

=== September 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* New release?
** [RR] wants reprounzip
** tej changes & doc
** job monitor & jobmixin fixes
** mongodb
** reprounzip
** warning: MplFigure type is int
** tabledata: add Reshape, DictoToTable & ListToTable, fix ListToTable with numpy arrays
** PythonSource can have same name for an input & output
** don't show spreadsheet at exit

=== September 2, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Limit autosaves? [https://github.com/VisTrails/VisTrails/pull/1126 #1126]

=== August 26, 2015 ===
'''Updates'''
* [TE] Added Job support to Parameter Explorations (Requested by Colin), and Mashups
** specify job ids, need to specify different ids for parameter explorations since they have the same version id
** how to deal with parameters passed in on command line
* [General] provenance: should be creating a new version when we execute workflow with changed parameters?
** currently, custom_params annotation stores this in provenance currently
** [RR] API doesn't record provenance if passing in parameters: http://git.io/vsAA5
'''Items to Discuss'''

=== August 19, 2015 ===
'''Updates'''
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [TE] Working on Job Monitor documentation

'''Items to Discuss'''
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [TE] Stop testing VisTrails 2.0?

=== August 12, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Build broken on Travis; because of IPython 4 released today? ([https://travis-ci.org/VisTrails/VisTrails/builds/75279795 build 992]; [https://github.com/VisTrails/VisTrails/issues/1123 #1123])

=== August 5, 2015 ===
'''Updates'''
* [TE] Fixes to Jobs
** Could not delete jobs
** Could not run job in group
** Job not reset when calling ModuleSuspended
** Added deleting job from context menu
* [RR] Writing documentation for everything [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

'''Items to Discuss'''

=== July 29, 2015 ===
'''Updates'''
* RR still looking into new interpreter thing
** Goal is to take out scheduling logic from Module so it can be split in multiple processes, and so that smarter strategies can be added in time
** This means some work on packages
** Spreadsheet can live in kernel process? Still some UI stuff that will take work (changing configuration, persistent archive's viewer, ...)
* [TE] Problems running examples [https://github.com/VisTrails/VisTrails/pull/1111 #1111]
** Testing of more examples requires additional packages on the test machines.
** Fixed faulty line-ending in PythonSource:s failing on Python 2.6.
** Test suite now testing SUDSWebServices (If web service is down, test suite will fail)
** preferences.py test failed reloading 'dialogs' package, switched to using 'URL'.

'''Items to Discuss'''

=== July 22, 2015 ===
'''Updates'''
* [TE] mailing lists back online
* [TE] Working on [https://github.com/VisTrails/VisTrails/issues/1107 #1107]
* [RR] Working on ReproZip package

'''Items to Discuss'''
* [RR] MongoDB package [https://github.com/VisTrails/VisTrails/pull/1106 #1106]
* [RR] Example for tej docs? [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

=== July 15, 2015 ===
'''Updates'''
* 2.2.2 released

'''Items to Discuss'''
* RR is considering executing everything in an IPython kernel (i.e. separate Python interpreter, like the one spawned for a notebook)
** It's a separate process that we can restart without restarting the app/gui
** We can isolate the execution environment (e.g. for the server)
** We can run the whole thing remotely (if your data is elsewhere, just run VisTrails locally and the pipeline elsewhere)
** Pipeline execution no longer makes the interface hang, it just makes the kernel hang (but that's fine)
** We can use notebooks as modules (probably way nicer than the PythonSource module)
** We can run multiple kernels so long as the ports carry things that are serializable
*** meaning we can put the multithreaded-interpreter without all the hacky parts it has now
*** we can run IPython kernels in all the languages IPython supports, [https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages currently 46]

=== July 8, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Buildbot github hook not working after IP address change
* [TE] No reference to VistrailsApplication ([https://github.com/VisTrails/VisTrails/issues/1103 #1103])
** [RR] Added PR [https://github.com/VisTrails/VisTrails/pull/1104 #1104]
* [TE] Reopening VT file after saving with bundled subworkflow won't offer subworkflow upgrade ([https://github.com/VisTrails/VisTrails/issues/1102 #1102])
** allow manual delete to fix right now
** fix this on top of the use-uuid branch
* [TE] Release VisTrails 2.2.1? ([https://github.com/VisTrails/VisTrails/blob/v2.2/CHANGELOG CHANGELOG])
** [https://github.com/VisTrails/VisTrails/pull/1093 output-modules-use-global-dir]
** [https://github.com/VisTrails/VisTrails/milestones/version%202.2 Current issues for 2.2]

=== July 1, 2015 ===
'''Updates'''
* [TE] PROV fixed
* [TE] Working on subworkflow issues
* [RR] Considering reworking the controller (log vs exception problem, retained upgrades causing interferences) and also the interpreter (IPython?)

'''Items to Discuss'''

=== June 24, 2015 ===
'''Updates'''

'''Items to Discuss'''
* UV-CDAT
* [TE] Can a cyclic workflow be valid? ([https://github.com/VisTrails/VisTrails/issues/1097 #1097])
** focus on disabling the ability to create cyclic pipelines because more things break than just this with a cyclic pipeline
* [RR] Relative paths ([https://github.com/VisTrails/VisTrails/pull/1057 #1057])
** This interacts with the new bundle; how do handle packing files inside the VT bundle?

=== June 17, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] current_version and reusing existing upgrades are broken ([https://github.com/VisTrails/VisTrails/issues/1095 ticket #1095])
** Could be that export to PROV is using an unflushed upgrade pipeline?
** current_version would then be correct.
** It may work to flush the actions before exporting?

=== June 10, 2015 ===
'''Updates'''
* DAT: fixed VTK issue on Linux and Mac
* Still crashes on Windows. Need help! Reminder: this works in the VisTrails spreadsheet (QCellPresenter), although no widget get changed there during a drag
** Is it a VTK bug?
** Is it simply impossible to change widgets during the drag, should we do it a different way?
** Did I miss something that is done in VisTrails but somehow not in DAT?
** Low prio, UV-CDAT doesn't run on Windows anyway

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 Updated pull request])
* Single instance code and batch mode

=== June 3, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 pr])
** Requires fixes to command line parameters, Output modules, and batch mode
** How to test this
** Updated missing/outdated flags
** Fixed view issues when generating graphs
* [TE] batch mode
** SpreadsheetOutput not enabled in batch mode. Should we check is_running_gui instead?
** Other instance setting flags from caller
** Is graphsAsPdf replacing spreadsheetDumpPdf?
** graphsAsPdf true by Default?
** Batch mode executing by default (Not needed when generating graphs)
** Re-added workflowInfo as withWorkflowInfo for writing graph and xml workflow
** [DK] batch mode should be outputting to files or stdout, shouldn't always trigger SpreadsheetMode
** execute flag, maybe make execution the default and allow a "--no-execute" if you only want to capture graphs, for example

=== May 27, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] API question
** http://lists.vistrails.org/pipermail/vistrails-users/2015-May/000357.html
* Status of DAT
** Can add VCS plot to DAT but need to work on configuration windows
** Documentation for graphics templates for UV-CDAT/vcs?
* Qt support?

=== May 20, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Reviving the DAT, integrating scripting & porting UV-CDAT!
** On [https://github.com/VisTrails/DAT GitHub] ([https://github.com/VisTrails/DAT/issues issues])
** Merging 2 years of development taking longer than expected, but getting there. The plan is to get the patches in VisTrails and never fork again, we never want to get in UV-CDAT's situation (and don't need to).
** VTK cell works fine on Linux but there was flickering on Mac & Windows before; still issues on Mac (Windows status unknown)
** Can get a VCS plot soon (but will need VTK cell fix)
** Integrate in UV-CDAT's build system (so we have cdms, VCS, ...) -> RR can do this, low priority
** How do we integrate scripting?
*** We want to be able to seamlessly make changes to a plot by changing Python code
*** Define new plots by entering Python code without writing modules/packages?
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 13, 2015 ===
'''Updates'''
* [RR] Test skipping whitelist ([https://github.com/VisTrails/VisTrails/pull/1069 #1069]) -- low priority
* [RR] Custom matplotlib modules can't be compatible with both 2.1 and 2.2 ([https://github.com/VisTrails/VisTrails/issues/1067 #1067]); should be fixed for ALPS ([https://github.com/VisTrails/VisTrails/issues/1070 #1070])

'''Items to Discuss'''
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 7, 2015 ===
'''Updates'''
* [RR] Export/import workflow to Python working!

'''Items to Discuss'''
* [Claudio] UV-CDAT
** The UV-CDAT project is the biggest user base of VisTrails
** VisTrails package management provides a lot of friction towards people plugging in their code
** Need to make it easy to integrate your random Python scripts in the system without having to deal with all the boilerplate, at least in the first step
** [RR] argues that modules are still good; UV-CDAT shouldn't move towards a purely script-based backend
** [RR] export/import with Python could reduce a lot of that friction by allowing 1) to edit workflow as Python 2) to open up boxes automatically if needed code doesn't match actual modules
** ...

=== April 29, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] <strike>Abstractions</strike> subworkflows status ([https://github.com/VisTrails/VisTrails/labels/subworkflows tickets])
* [RR] matplotlib compatibility (2.1 & 2.2), [https://github.com/VisTrails/VisTrails/issues/1067 #1067]
** RR to try and fix ALPS matplotlib modules

=== April 22, 2015 ===
'''Updates'''
* 2.2.0 has been released!
* Windows issue (via email from Ryan)
** issue with manifest file (may be a new file in VTK6?)
** Tommy has regenerated new Windows builds
* Binaries, pypi, and conda released
* [RR] Export as script
* Python sources using VTK need to switch to SetInputData (users should be aware of this)

=== April 15, 2015 ===
'''Updates'''
* Ready for 2.2.0 (apart from binary/deps issues)
** Missing some libs (scikit-learn, tej, tdparser, SQLAlchemy+connectors
** Windows: runvistrails.py is no longer used, so the PATH is wrong
** Windows: pip is broken, but it probably wouldn't work anyway because of permission issues (disable this?)
* Queries, upgrades and getPipeline() usage ([https://github.com/VisTrails/VisTrails/issues/1054 #1054])
** Getting a pipeline with getPipeline() is not safe: it might return an invalid pipeline
** This is used in many places throughout the code, like queries
** Upgrading would require going through the controller, but that creates new actions
* [TC] Avoid copying a module's output if it's used as input by exactly one downstream module ([https://github.com/VisTrails/VisTrails/issues/1060 #1060]) (useful for big numpy arrays you can update in-place)

=== April 8, 2015 ===
'''Updates'''
* [DK] Merged RR's changes for output modules (1012 and 1013)
** RR will merge remaining changes, then create v2.2 branch!

'''Items to Discuss'''
* BNL need numpy array to VTK image
** Looks like VTK has some helpers for this
** We will help if issues arise
** Will contribute back to VisTrails package
* Upgrade issue: [https://github.com/VisTrails/VisTrails/issues/1017 #1017]
** Automatic upgrades should happen between versions of provided upgrades
** Our existing upgrades work around this so it doesn't need to be 2.2.0
* Corner-case VTK modules
** No longer need VTKCell input port, so don't interfere with registry and API anymore
** Still work weirdly, people probably shouldn't use them
** But we have lots of clunky modules since we wrap the whole of VTK; some people might rely on this and know how to use them, let's keep them anyway
** Ready for 2.2.0

=== April 1, 2015 ===
'''Updates'''
* [RR] UV-CDAT: bugfixing for 2.2, long-term plans: implement scripting import/export in VisTrails, port to UV-CDAT
* Possibly, try to move to regular VisTrails to use new features

'''Items to Discuss'''
* 2.2 release: nothing much is pending anymore, release next week?
** [TE] vtkExporter classes [https://github.com/VisTrails/VisTrails/issues/1032 #1032]
** [RR] Hiding upgrades in version tree might make it (or might be 2.2.1 so we can test it out) [https://github.com/VisTrails/VisTrails/issues/949 #949]
** Output modules changes to go in
* add note to documentation about order of parameters in VTK
* add issue about exporter upgrades if not already there

=== March 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* 2.2 release
** Checklist on Github: https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist
** Review output modules
** RR has a couple more issues to fix
** Ready to go -- sign app package for OSX? [https://github.com/VisTrails/VisTrails/issues/984 #984] We need access to the Apple Membership team

=== March 18, 2015 ===
'''Updates'''
* [TE] VTK6 works

'''Items to Discuss'''
* [RR] Release v2.1.5 with backported tabledata?
** MTA example needs updated tabledata (for JoinTables)
** Google Maps package still not available
* [RR] Work torward v2.2.0?
** changes:
*** new persistence
*** API changes
*** output module changes (upgrades?), maintain cells but try to upgrade
*** not wrapping stuff
*** VTK6? yes
*** JobSubmission stuff?
*** relabeling for upgrades [https://github.com/VisTrails/VisTrails/issues/949 #949]
** makes sense, needs the tree view code to be updated, check selection
** See [https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist 2.2 checklist]
* Discussion of [https://github.com/VisTrails/VisTrails/issues/1016 #1016]
** plumbing between outputs and output modes, how to define a mode that works for many outputs without writing for each output?

=== March 11, 2015 ===
'''Updates'''
* [RR] persistent_archive done; merge? ([https://github.com/VisTrails/VisTrails/pull/755 #755])
** note about the focus events for widgets
** TE be aware of file_archive for future binaries that include persistent_archive
* [TE] [https://github.com/VisTrails/VisTrails/pull/998 New VTK package] finished

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails? (see last week; decision needed)
** RR email to JF about this
** yes; email sent to Github
* [RR] Switching order of output ports ([https://github.com/VisTrails/VisTrails/pull/1006 #1006])
** added port specs are sorted at a separate spot (Module.*_port_specs properties) than those in the registry (which are sorted in the registry), but those two lists are just combined without respect to sort keys
** need to determine whether the two lists should be merged or remain distinct
** should make sure that order of input ports and output ports makes parallel connections for things with same order
** DK suggests breaking backward compatibility here: workflows still run, can fix easily if a problem in an existing package.
* [RR] Question about output modes ([https://github.com/VisTrails/VisTrails/pull/1007 #1007]), how to integrate in API ([https://github.com/VisTrails/VisTrails/pull/24 #24])
** Should ImageFileMode be removed? ("image" is not a mode, "file" is)
** ImageOutput missing?
** Feel free to change how formats works
* [TE] Test suite segfaults on Fedora 17 virtualbox. Install newer version? (Support ended in 2013)

=== March 4, 2015 ===
'''Updates'''
* [TE] VTK wrapper
** Works on VTK 5.10
** Still need to test VTK 6
** New general wrappers for python functions and classes

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails?
** When [http://i.imgur.com/UTY2qfg.png filing a pull request] from UV-CDAT/VisTrails, VisTrails/VisTrails is selected by default
** People keep forgetting to change the default ([https://github.com/VisTrails/VisTrails/pull/956 #956] [https://github.com/VisTrails/VisTrails/pull/968 #968] [https://github.com/VisTrails/VisTrails/pull/999 #999] [https://github.com/VisTrails/VisTrails/pull/1000 #1000] [https://github.com/VisTrails/VisTrails/pull/1003 #1003] [https://github.com/VisTrails/VisTrails/pull/1004 #1004] [https://github.com/VisTrails/VisTrails/pull/1005 #1005])
** Only way to change that is to not have it marked as a fork of VisTrails/VisTrails
** Github staff [https://gist.github.com/remram44/b364c24ef1e462ce6e2f can make that change for us]; should we do it?
** Juliana: comments on this? visibility vs. convenience/annoyance for developers
* [RR] What about [https://github.com/VisTrails/VisTrails/issues/991 #991]?

=== February 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] vtkviewcell for infovis support, can we unify with VTKCell?
** need to test this
* [TE] vtk wrapping
** Mostly finished
** VTK 5.10 produce incorrect results with old wrapping
*** Old wrapper is based mostly on VTK 4
*** Most vtk_examples affected
*** [http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Replacement_of_SetInput]
*** should be able to upgrade from SetInput to SetInputData (need to drop GetOutput and replace with self ports)
*** can we change vtkInstance to just return self and not wrap things
** terminator example not working under 5.8?
* How does VTK wrapping fit into general wrapping framework?
* [RR] new persistence package

=== February 18, 2015 ===
'''Updates'''
* [RR] New VisTrails API and IPython integration ([https://github.com/VisTrails/VisTrails/pull/24 #24])

'''Items to Discuss'''
* [TE] VTK wrapping
** [https://gist.github.com/rexissimus/16b74693545b5e7c1035 Benchmarking vtk package]
*** Old: 24.7 seconds
*** New: 10.5 seconds (Except first time that adds 8 sec)
**** The parsing that calls is_abstract (that tries to instanciate all vtk classes) is now only run the first time.
**** get_items_from_sigstring takes 2 seconds, maybe we can use a lookup dict for already computed sigstrings?
** Now using a general python function wrapper
*** VTK classes are wrapped into python function that does not depend on vistrails
*** VTK functions can be executed without vistrails
*** The spec maps functions into vistrails modules, but can also describe wrapping
*** A general python function wrapper that supports
**** kwarg inputs
**** single, list, dict outputs
**** callback for progress reporting
**** temporary file generator for using FilePool
**** optional output generation
*** Creating specs:
***** Create spec by hand
***** Auto-create spec outline (TODO) and manually finish it
***** Dynamically create spec (VTK)
***** Implement documentation wrappers (Can use scikitlearn wrapper to wrap numpydoc) (TODO)
***** Classes as bad functions needs to be wrapped in new functions before they are wrapped. This is different for each package.
****** Classes is hard: Like VTK, and matplotlib. Scikit-learn does still not wrap classes
***** Spec diffing and patching could be done using code from matplotlib.
** Still needs upgrades from old VTK package
*** Is it possible to dynamically wrap functions, e.g, you see a SetFunc and just remove the 'Set' prefix. Or do you need to create a complete mapping?

=== February 11, 2015 ===
'''Updates'''
* Update from Friday's meeting
** discussed VisTrails internals
** discussed wrapping
*** xml discussion, hard to modify because tied to db code
*** TE has made it possible to add the schema-defined attributes to the intermediate representation
*** higher-level operations on the port specs
** make sure the simple case works
*** [JF] take a simple package with documentation and figure out what the base case for wrapping is

'''Items to Discuss'''
* [TE] VTK wrapping
** Dynamic loading works
** Reading XML is fast enough, but [https://gist.github.com/rexissimus/8272d3c776ccfa115d82 unserializing data is slow]
** Working on patterns for patching
** Matplotlib has many advanced patterns like argument ordering, nested arguments, alternateSpecs, output types.
*** Having all this in a general wrapper might confuse users?
** [RR] Delay module (except for identifiers) until you need it---e.g. don't deal with port specs, etc. until necessary
* Scripting Support [https://github.com/VisTrails/VisTrails/pull/950 #950]
** [RR] Issue with getting code from modules
** Design a simple solution
** [JF] Couldn't you use modules as black boxes without conversion, just to call into modules/subworkflows easily from e.g. IPython?
*** [RR] This is a job for the API, and a very separate use case. See [https://github.com/VisTrails/VisTrails/pull/24 #24]

=== February 4, 2015 ===
'''Updates'''

'''Items to Discuss'''
* Wrapping
** Format to use? Currently XML (like current matplotlib)
*** JSON and YAML have simple "to python dictionary" methods
*** But don't stream
*** YAML a lot easier for humans
** [DK] vtk-new-package also changes parameter names, creates enumerations
*** intermediate schema needs to be extensible
*** packages will want to store there specific infos for compute() method generation
*** also might have specs-altering info, like matplotlib's alternateSpec
** representation to code , registry already has schema for some aspects
** [RR] We might want to see if Module subclasses can be created lazily
*** no need to create all the classes just to register them in the registry and never actually use most of them
*** future effort
* [RR] Where should VisTrails packages live?
** tej installs as 'vistrailspkg.tej', TE installed it as 'userpackages.tej'
** Currently, standard packages are 'vistrails.packages.', user packages are 'userpackages.' and packages loaded through pkg_resources might be anything
** [RR] Use 'vistrailspkg.' everywhere?
** Long-term effort to simplify package distribution/installation (and have VisTrails get them automatically?)

=== January 28, 2015 ===
'''Updates'''
* T. Caswell to come visit on Fri 6 to discuss wrapping work

'''Items to Discuss'''
* [TE] New VTK wrapping
** Current code by DK seems a good deal faster
** Generates XML that can be patched/tweaked, generates Python code from it, VisTrails only loads generated Python code
** RR would rather have VisTrails load intermediate representation (= XML) directly, wants to make sure this is not slower
** The goal is to turn the intermediate step into something generic that would be used for every wrapped package (vtk, numpy, matplotlib, sklearn, java) instead of each having its own
** TC has its own code at [https://github.com/Nikea/VTTools/blob/master/vttools/wrap_lib.py github:VTTools] which parses numpy docstrings and generates modules, doesn't yet handle classes or persist anything
* Web crawler
** Right now, TE starts jobs for "start crawler", "stop crawler", "install classifier"
** RR would rather have the crawling be a job as far as VisTrails and tej are concerned
** The whole thing would be one pipeline: load examples, train classifier, start crawler [check for job, kill previous one, upload model, start processes], get snapshot, visualize
*** Need some support in tej and job submission system: long-running jobs, stop a job (wait for it to finish?), restart a job even though results are cached

=== January 21, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Unified wrapping method discussion [https://github.com/VisTrails/VisTrails/issues/991 #991]
** TE to work on reusable method with intermediate representation, starting with VTK
* [RR] Examples for scikit-learn: JF has an old example using Weka with parameter exploration (not currently in source tree)
** AM's examples are enough
* [AM] scikit-learn package is done, merge it in? [https://github.com/VisTrails/VisTrails/pull/955#issuecomment-70286788 #955]
** RR will merge
* [RR] What should copyright headers say? [https://github.com/VisTrails/VisTrails/pull/994#issuecomment-70173935 #994]
** Let's keep everything in there: Utah/Poly/NYU

=== January 14, 2015 ===
'''Updates'''
* [TE] Working on classifier
* [RR] Scripting integration, work in progress

'''Items to Discuss'''
* [RR] Unified wrapping method discussion ([https://github.com/VisTrails/VisTrails/issues/991 #991])
** Let's talk next week, [AM] and [DK] are not here

=== January 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* make sure that we address critical issues, questions, and pending review branches in a timely manner
* scripting support
** [RR] no issues if we want to just keep annotations in the generated code to allow the link back to a workflow
** [RR] can translate from workflow to script, working on script to workflow
** will work for parameter value changes, structural changes require changes to the annotations
** need to publish best practices here
** would be cool to do looping in scripts (easier interface than with workflows)
* notebook support (convert form notebook to workflow)
** RR will sync with FC on this
* Issue with console in built-from-scratch
** [TC] iPython rearranged some of the completion stuff in 2.2 and 2.3
** binary has old version of iPython -> 1.0.0, should we update?
* [TC] automated wrapping of numpy and scipy
** discovered a bunch of malformed documentation in numpy and scipy
** has github repo for vistrails tools
** example modules wrap a bunch of R stuff (not baked in, just how things are)
** will be pushing wrapping logic up
** port names forbidden (window and domain)
** have an import hook to get from yaml directly to VisTrails Modules
** should work for any python modules with well-formed numpy docstrings.
* [Action] should make it clear in documentation that Constant now means serializable not that the value doesn't change (e.g. List)
* [TC] might be interesting to try to build components of matplotlib and accumulate in figure (long-term project, but thinking about how this might work)
* [TE] build and build scripts
** completely automatic, buildbot
** need to set the build machines for the environment we want for the binary
** would virtualenv work here?
** [TC] anaconda can pin versions, potential path to test different configurations
** Q: upload nightly binary builds? A: makes sense, make sure they are well-labeled
* sourceforge stats: e.g. http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07
* package issues (see Remi's message)
* [TE] Scope of tej
** Support single ssh commands?
** Queue can be used as a remote machine (crawler is using queue.call*)
* SourceForge stats: http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07

== Older meetings ==
* [[Development/2014]]
* [[Development/2013]]
* [[Development/2012]]
* [[Development/2011]]
* [[Development/2010]]

Development

2016-08-02T15:38:20Z

Tommy: /* August 3, 2016 */

<div class="nonumtoc toclimit-1">
__TOC__
</div>

See also the [https://github.com/VisTrails/VisTrails/wiki/Development Github wiki]

== 2016 ==
=== August 3, 2016 ===

'''Updates'''
* [TE] Wrapper patches now stored as [https://github.com/VisTrails/VisTrails/blob/python-wrapper-script-patches/vistrails/packages/vtk/vtk_wrapper/vtk_patch.py python code]
** connection variables now lowercase

'''Items to Discuss'''

=== July 27, 2016 ===

'''Updates'''

* [DK] DB bundle serialization implemented

'''Items to Discuss'''
* [TE] Finished using patch in script [https://github.com/VisTrails/VisTrails/tree/python-wrapper-script-patches python-wrapper-script-patches]
** locale?
** [https://gist.github.com/rexissimus/f0d6b026aa5a2a770847f3321744645d new patching example] vs [https://gist.github.com/rexissimus/b28d83ae516a519167f5751bb8ab3739 old patching example]
** [https://github.com/VisTrails/VisTrails/blob/python-wrapper-script-patches/vistrails/packages/vtk/vtk_wrapper/parse.py#L135-L273 Example of new patches]
** Legacy '.vtkInstance' is now added as a patch "self.vtkInstance=self" (see new patching example)
** [https://github.com/VisTrails/VisTrails/blob/python-wrapper-script-patches/vistrails/core/scripting/api.py New api for executing standalone modules]
*** Accessing module was disabled for core/api, but a different api for this is probably better anyway.
*** api.Package now gives [https://gist.github.com/rexissimus/f0d6b026aa5a2a770847f3321744645d#file-new_patching-py-L26 directly callable module compute functions]
*** Only works on modules not using interpreter functionality ('.interpreter', etc.)
**** for zip file modules and others that need temp files and use the interpreter for this, need to modify the module, but could work around with python libraries for managing temp files
** Fixed more renaming issues - [https://github.com/VisTrails/VisTrails/blob/python-wrapper-script-patches/vistrails/core/scripting/scripts.py#L63-L64 function argument names should not be replaced]
** Still need to do something nicer for the patch formatting
*** patch keys currently contain non-python-variable characters but this can be fixed
*** Need to replace string template with python variables that is replacable using RedBaron
**** Patches could then look like:

def vtkInstance():
self.vtkInstance = self

=== July 20, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] New patch method for python-wrapper [https://gist.github.com/rexissimus/009b303e4cadcd4b8f2fec6cf848cb2b example]
** A patch is a string template with self/input/output variables for patching a class method
** Patches are stored in xml specification
** Patches are assigned to methods in ClassSpec's
** Used both for execution in vistrails and when exporting as script
*** Executed with "exec" when run in vistrails
*** Turns patches into natural calls in script
** Wrapping VTK library no longer needed
*** Removes ".vtkInstance" (Automatically removed from PythonSources and vtkInteractionHandlers)
** Removed fix_classes.py (Subclassing of VTK classes to patch methods directly)
** Also used for port translations (With patch names like "basic:Color#input") (No more ugly input_t method definitions)
** TODO's
*** Add to export_as_script
*** Patch Modules that represent Python functions as well

* [vistrails-users] Read data from SQL example?

=== July 13, 2016 ===

'''Updates'''

* [DK] bundles on sql-alchemy branch
** Bundle, BundleMapping, and BundleSerializer
** New BaseSerializers to deal with versions of directory, zip, db serializers
** Can register the BundleSerializers with the base serializers
** Translation between bundle versions
** Bundle.add_object "just works" if an appropriate mapping was registered

'''Items to Discuss'''
* [TE] Simplified running module using API for scripting [https://gist.github.com/rexissimus/b28d83ae516a519167f5751bb8ab3739 example]
** API Module can be executed using '''compute''' method
*** Takes list of outputs to compute + inputs as keyword arguments
* Status of general cell synchronization (vistrails-users)

=== July 6, 2016 ===

'''Updates'''

* [DK] Working on bundles

'''Items to Discuss'''
* [TE] Using vistrails API in scripting [https://gist.github.com/rexissimus/034d9c4dedc3299a079e84981dedd8c7 example 1 (API with VTK)] [https://gist.github.com/rexissimus/a4a9ca6c08d4058c64967d2b35415fd5 example 2 (DownloadFile only)]
** Call module in script using vistrails API
** Can be used when no export method is defined.
* [TE] [https://github.com/VisTrails/VisTrails/commit/c76c109349769fee1280f85c22678380a2f9cd39 Server news bug] Critical?
**[RR] No, unreleased
* [DK] New bundle organization
** BundleMapping contains individual mappings from raw objects to BundleObj
** Must be separate in order to have in-memory, separate from serializer settings

=== June 29, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Export VTK as python script
** Works on Terminator (Isosurface, Volume Rendering, clipping plane, combined rendering) [https://gist.github.com/rexissimus/16caf5200802e150296f62a0c7844c5a example]
** Preludes (imports) still need improvements
** Works with vtkInteractionHandler (clipping plane)
** Resulting clipping plane is incorrect? (supposed to hide one side of the plane)
** vtkRendererOutput Uses VTKRenderWindow as output
*** Should support different output modes?
*** Does not work with multiple outputs (Next cell is displayed when current is closed)
*** Uses wrapped vtkInstance (as vvtk)
**** Create new patch system with code that can be used both in vistrails and in a python script?

=== June 22, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Fix for upgraded analogies (PR [https://github.com/VisTrails/VisTrails/pull/1177 #1177])
** Uses module location to find module remap (The best we can do right now?)
** Also fixes remapped port names for connections to existing modules
** May still fail on complex upgrades like adding a function on an upgraded module that has a different port name

* [TE] Working on exporting wrapped libraries (VTK)

=== June 15, 2016 ===

'''Updates'''
* [TE] Added depth logic to python script exporter ([https://github.com/VisTrails/VisTrails/commit/50f220e4f6abe5a7bb8689f73f456f43df2dbc12 full commit])
** Fully implements connection merging and list looping

'''Items to Discuss'''

* [TE] Making analogy work on upgraded workflows ([https://github.com/VisTrails/VisTrails/issues/1175 #1175])
** Analogy only works We need to use the non-upgraded action chain
** But pipelines need to be valid (matcher uses module portspecs)
** Tried to get upgrade remap from upgrade action, but this seems impossible
** Use module location instead?
*** Location should be identical for one-to-one module upgrades

=== June 1, 2016 ===

'''Updates'''
* VisTrails 2.2.4 announced (finally)
** 5 survey replies
** 47 downloads last week

'''Items to Discuss'''
* [TE] Export VTK as script (python-wrapper)
** to_python_script
*** needs the pipeline (or at least the connections)
**** Should not generate code for any possible VTK method (exporter detects which ports is used in the source)
**** VTK needs to know connection order
**** Adding functions directly to the script results in nicer code
** Add support for multiple input connections
** Add support for list looping

=== May 25, 2016 ===

'''Updates'''
* Mailing-list fixed
* Getting stats from the "server news" mechanism (via [https://github.com/remram44/apache-log-info parser])

'''Items to Discuss'''
* [RR] Alexis doing writeup on VisTrails, curious about interesting streaming use-cases (and potential future users)
* [TE] Union ports
** Show union ports in pipeline (DEMO)

=== May 18, 2016 ===

'''Items to Discuss'''
* [TE] mailing list still down - Julio working on it
* [TE] Improved union port
** New schema 1.0.5 adds portitem.union string attribute
** Works with pipeline view, parameter exploration view, and mashup view
** Should work well for matplotlib
** Use with VTK ports?
*** It uses [item_1,item_2] style ports usually with different tuple length.
* [TE] Remove emacs dependency from db generate [https://github.com/VisTrails/VisTrails/issues/1173 #1173]

=== May 11, 2016 ===

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]
** GUI-based solution [https://github.com/VisTrails/VisTrails/tree/union-port Branch union-port] Demo?
*** Shows single port for all ports with same sort_key
*** Select specific type when adding/showing
*** Only one type should be visible on the module at any time
*** Making tuple parameters union types is probably too complicated
*** Should work with alternate specs like matplotlib (if sort_key is defined correctly)

* [TE] Feature suggestion: Let connections connect to functions/parameters
** Show functions and parameters as ports and toggle port visibility directly for functions and parameters
** Use separate views for ports and functions (like before)
*** Allow rearranging of functions
** Pros:
*** Supports ordered connections. Create 2 functions, make them visible as ports, make connections to them.
**** We can also have, e.g., a line joining the ports on the module to indicate they are part of a list.
**** Makes List module simpler
*** Connect to parameter in tuple
*** Functions that are visible on the module can connect to an actual function, and not just to the first one it finds.
*** Can replace operation modules (in python-wrapper) in some cases for, e.g., numpy.
** Cons:
*** Interface more complicated and crowded
*** More difficult for users to grasp?
*** No immediate use case
*** Makes no union type for tuple parameters a bigger problem.

* [TE] Publish user survey?
** No response from vistrails release yet
** Not announced on vistrails-users yet.

=== May 4, 2016 ===
'''Updates'''
* VisTrails 2.2.4 released

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]

=== April 27, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Wrapping Bokeh
** New method type "operation"
*** Transforms Figure->Glyph->Output into Glyph->Figure->Output
**** Glyph sets function name and arguments as output
***** Not serializable, but should always be computed together with the subject of the operation.
**** Figure applies Glyph operation on itself
*** Useful for matplotlib?
**** matplotlib currently find actors by searching upstream?
**** But this is more difficult since matplotlib is not function-based.
** New "union" port type
*** Turns "x(float), x(list)" into "x (float, list)" and uses first set value
**** Uses only first value in tuple
**** Bokeh have many properties that support (list, string, Float)
*** Does not work with depth=1 types (e.g. Float of depth 1)
**** Turn Depth 1 types with known type into lists?

* [TE] New bugfix release
** Finalize survey

=== April 20, 2016 ===
'''Updates'''
* Merged upgrade fixes
** Now has infinite loop test
** loop test now correctly loops 5 times
*** remap_module used wrong (current) package version when creating ModuleDescriptor
* Fixed multi-step group upgrades (PR: [https://github.com/VisTrails/VisTrails/issues/1168 #1168])

'''Items to Discuss'''
* New bugfix release
** Merge usagestats
** Need to finalize survey

=== April 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Chaining upgrades done ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Replace "Upgrade" description annotation with "upgraded_from" annotation to identify which tags to hide?

* [TE] Iterating handle_invalid_pipeline ([https://github.com/VisTrails/VisTrails/pull/1165 #1165])
** Not based on [https://github.com/VisTrails/VisTrails/tree/chain-upgrades-loop chain-upgrades-loop]
** Cherry-pick test to preserve source?
** Need maxPipelineFixAttempts option?
*** The code is now smarter about recursion, so max attempts will "probably" never be reached.
** Need [https://github.com/VisTrails/VisTrails/commit/0ef0667426937eddb1d1c1e397f0657ffec039a9 debug messages]?
*** Would need to be moved into handle_invalid_pipeline

=== April 6, 2016 ===
'''Updates'''
* [TE] Query View improvements
** Done except for displaying "Version Info" and #1164
* [RR] Working on finishing new interpreter (finally!)

'''Items to Discuss'''
* [TE] Chaining upgrades ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Try latest upgrade first, then previous.
** If all fail, select latest upgrade?

=== March 30, 2016 ===
'''Updates'''

'''Items to Discuss'''

* [TE] Query View improvements
** Unified do_version_switch and get_upgrades as validate_version()
** Problems with query view using its own controller
*** Fixed module info not being displayed for query results
*** Still no version info for query results
*** Still an issue with version query view not being updated

=== March 23, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Usage reporting almost ready to go
** Need to record whether specific features are used: paramexpore, mashup, query
*** [DK] Record if LaTeX extension is used? But hard to distinguish from direct batch invocation
** How to record size of vistrail?
*** [DK] IdScope already walks over vistrail, use that
*** but total number of modules and versions doesn't give an idea of average size of individual pipelines

=== March 16, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Upgrades in Query Mode
** Now using code similar to do_version_switch
*** Uses handle_invalid_pipeline
*** Differences: Not using current_pipeline, flushes changes
*** New controller method get_pipeline optimized using cached pipelines (but not current_pipeline)
*** Integrate to avoid repeated code?
*** Use this for query mode?
* [TE] VisTrails 2.2.4 ready for release?
** tej package updated. Others?
* [JF] upgrades and the version tree
* [JF] provenance in Jupyter
* [DK] bundles: [https://github.com/VisTrails/VisTrails/pull/1092 #1092]

=== March 9, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixing search mode
** String query now matches all by default
*** This caused pipeline queries to never match
** String query can search: User/Notes/Tagname/Time/Module name
*** Should we search module names by default? (Disabled by default because it is expensive)
*** Fixed notes search
** '>' parameter queries in documentation but has been removed
** Fixed module matches for upgraded pipelines (By not upgrading pipeline)
*** Upgrades still a problem
*** Add "Upgrade all menu option?" (Or upgrade all on open when `hideUpgrades`)
*** [JF] Allow search on past tags

* [TE] Create new bugfix release
** Finish querying
** Path issue on windows

* [DK] Look into sqlalchemy and new bundle branches

=== March 2, 2016 ===
'''Updates'''
* [TE] Fixed cache bug with port specs
* [TE] VisTrails Next
** Most packages now work
** No qgis for Python 3

'''Items to Discuss'''
** Always dereference symlinks? [https://github.com/VisTrails/VisTrails/issues/1146 #1146]

=== February 23, 2016 ===
'''Updates'''
* [TE] Fixed PythonSource 100% CPU bug
* [TE] VisTrails Next
** Updated [http://opendap.co-ops.nos.noaa.gov/axis/webservices/wind/ NOAA Web Service] examples
*** Now uses REST service, tabledata, and Google Maps
*** Web Service replaced with DownloadFile

'''Items to Discuss'''
* [RR] Couple of fixes are in for API, and tej&reprounzip on the Mac binary. Also new release of tej, and working on anonymous usage reports.
** New 2.2 release soon?
* [RR] Anonymous usage reports
** Sends out info like number of modules & versions, packages used, Python & libs versions, execution time, specific features [https://github.com/VisTrails/VisTrails/pull/1154 #1154]
* [JF] Bring in noWorkflow to track variable dependencies, for the considered Jupyter integration?
* noWorkflow - provenance for python scripts
** Recent work on tracking dependencies
* Also integrates ReproZip with Jupyter
** [http://mybinder.org mybinder]
*** Use with ReproZip to automatically build Jupyter notebook interfaces
* Daves comments on Jupyter integration
** It is possible to identify cell order on the server side
** Not trivial to track order of cells on client side
* How does Galaxy workflows relate to VisTrails?
** Packaging in Galaxy is hard
** Galaxy for biomedical workflows, difficulty making it general
* Action items
** How difficult to track cell dependencies in Jupyter notebooks?
** Use noWorkflow to track cell dependencies?
** How difficult to modify mybinder to use ReproZip packages?

=== February 17, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixed Group memory usage
** Modules in groups are supposed to be freed when done executing
*** Prevented by logger that stored references to the modules (fixed, now using id(module))
*** Prevented by list iterator bug that stored list of modules on the 'self' port bug (fixed)
* [TE] VisTrails Next
** Removed deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** PythonSources will be upgraded
*** Fixes for Python < 3
*** fixes for VTK < 6
** TODOs
*** Remove RemoteQ
**** Port Hadoop to tej (Already have pbs)
*** Merge package wrapper
*** Finish SQLAlchemy branch
*** Finish new bundle branch
** [JF] Will contact Jeff and Matthias about moving to Python 3
* [JF] Query by Example is broken
* [JF] VisTrails Data Cleaning Project
** Use VisTrails to process and explore task-specific data while keeping provenance.
** Remi's Idea
*** Use VisTrails as the backend in a Jupyter notebook
*** Overcome problems with executing cells in random order
**** Interesting research topic, but little interest has yet been noted
*** Interesting to study how such a notebook would be used (Is there notebook usage data available?)
*** Impose restrictions to notebook cell boundaries
*** It will only work for functional operations
*** Can we fix, or detect, non-functional (mutating) operations?
*** Analyse code and data flow and see if it mutates data in unexpected ways?
*** Mutable operations can be created in many ways in Python
* Next meeting Tuesday 11:30

=== February 10, 2016 ===
'''Updates'''

'''Items to Discuss'''
* VisTrails Next
** Test suite passes
*** Python 3 less deterministic, module upgrade order random.
** [RR] updating packages: Reprounzip (pushed), tej, persistent_archive, ...
** All of our packages should run fine :)
** VTK thumbnail comparison works
*** Rendering bug on some systems
**** QVTKCell now inherits QGLWidget
*** Old thumbnails had wrong height due to spreadsheetwindow being too small
**** Fixed by regenerating thumbnails
*** Silenced deprecation messages when generating modules
*** Many new classes in VTK 7
** Remove deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** Will break existing PythonSources
**** Try to upgrade?
*** Old-style packages
**** Or only allow a new style, like __init__.py renamed to info.py? (merge with identifiers.py?)
***** Read info.py without importing package?
*** Fixes for Python < 3
*** Fixes for Qt < 5
*** fixes for VTK < 7
*** Remove self port?

=== February 3, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] [http://lists.vistrails.org/pipermail/vistrails-users/2016-January/000402.html Rendering a .pvd (ParaView) file?]

* VisTrails Next
** All tests but thumbnail comparison passes
** Still issues with gui and more packages needs to be tested
** PythonSource and MplSource upgraded with lib2to3
** Keep contrib packages? Update?
** [https://blog.kitware.com/vtk-7-0-0/ VTK 7 is released]
*** Supports Python 3
*** Will hopefully get into conda and others soon
*** Deprecates a bunch of modules

* [https://travis-ci.org/VisTrails/VisTrails/builds/106743348 Travis builder] for VisTrails Next
** Runs!
** Uses conda
*** Many levels of requirements
**** apt packages
**** conda packages
**** python packages in requirements.txt
**** python packages in setup.py
*** Can probably drop conda. Default builder does not have Qt5, but beta builder do!
*** But useful if we want to use conda in our own build process.
** Lots of errors I do not get locally?

* [http://goo.gl/forms/Z4HBrwaBWL User Survey]
** Have you used any alternatives to vistrails?
*** Relevant? More options?
** How often do you use any of these particular features in VisTrails?
*** Add/Remove alternatives?
** How important would you rank the following potential improvements to VisTrails?
*** Add alternatives?

=== January 27, 2016 ===
'''Updates'''
* New interpreter
** Working prototype soon
** Looping not completely done (and port combination mode: pairwise/cartesian...)
** Need to integrate with VisTrails
*** Compatibility with existing modules
*** Use log controller
*** Want to cache at multiple levels (whole stream/single element of stream)
*** Non-runtime attributes of modules (cache check, automatic conversion check, constant from/to string)

'''Items to Discuss'''
* User Survey

* ZMQ failing on windows (vistrails-users)

* [TE] [https://github.com/VisTrails/VisTrails/pull/1143 Python 3 branch]
** Testsuite almost passes
*** Failing are unicode filenames, some users guide examples, and thumbnail comparisons.
** Fixed issues
*** Signatures are now bytes (convert to string to show in widget)
*** Cannot compare different types, e.g., (None < 1)
**** PortSpec.depth and min/maxConn could be None. (Backport!)
**** cell.row could be None
*** Lots of unicode/bytes fixes to serializations
**** We have encryption implementations in the code! (keychain)
*** Lots of small fixes to package method differences
** Current issues
*** logging widget empty?
*** version tree signals messed up
*** provenance view legend icons black
*** Text do not fit in some widgets
*** VTK thumbnail comparison fails
**** VTK Cells have some faces in wrong direction?
**** Because running in VM?
** Installing on Ubuntu LTS/Latest Mint
*** Install latest matplotlib from pip
*** Install VTK 7.0.0rc2 from source
*** No QtWebEngine binary (controversial) (Must install sip/PyQt5/Qt5 from source)

=== January 20, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Backporting features from Python 3 + PyQt5 + Qt5
** Merged unicode with master ([https://github.com/VisTrails/VisTrails/tree/unicode unicode])
*** One unicode test failing
*** Problem saving to xml
** Used [http://python-future.org/ python-future] to run futurize stage 1 to update legacy (pre 2.6) code ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized unicode-futurized])
*** Updates print to functions 'from __future__ import print_function'
*** Updates exception calls to use 'as'
*** removes most usages of 'long' (mostly used unnecessarily)
**** Only needed for 32-bit support
*** Fixes relative imports (from __future__ import absolute_import)
** Fixing code that is deprecated in Qt 4.8 and removed in Qt 5 ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized-qt5 unicode-futurized-qt5])
*** Updated all signals to new-style
* If we go 2 to 3, this could break packages
** means we should schedule any package format changes for the same time
** e.g., imports should be unrelated to code path (function to load module from package identifier?) (take them out of vistrails.* [https://github.com/VisTrails/VisTrails/pull/1002 #1002])
** any structural changes (e.g. the __init__ versus init thing) (RR thinks it makes sense, though having both named "init" is unfortunate)
** putting package identifier as xml?
*** Python not so bad, plus some stuff in there is Python code (checking dependencies)
** version the APIs?
*** RR planning on versioning vistrails_module.Module, no point versioning the whole package?
* file formats on 2 to 3:
** no real translation/upgrade, but non-ascii values that work on 3 won't load in 2

=== January 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://gist.github.com/rexissimus/dfd27e466427529c385c Porting to Python 3 / PyQt5]
** Basic GUI and execution works
** Minimal work to support 2to3
** Hard to support both PyQt4 and PyQt5

=== January 6, 2016 ===
'''Updates'''
'''Items to Discuss'''
* Updating VisTrails dependencies
** Successfully built [https://gist.github.com/rexissimus/f1a1aada7de1c00a57c7 Win7-64/Python3/PyQt5/Qt5/WebEngine/VTK7]
*** VTK 7 is the first supporting Python 3 but is only in release candidate phase.
**** Next version of VTK 6 is rumored to support Python 3
**** There is a development branch of VTK 6 supporting Python 3
*** Can travis build this?
**** We can skip tests for WebEngine and VTK if needed
** Python 3 [https://python3wos.appspot.com/ showstoppers]
*** No MySQL-python (sqlalchemy supports mysql through other drivers)
*** No suds (there are active forks but we could also drop support?)
* Options for python2/3 support:
** Interpreter could be python2/python3 based on packages
** six layer works but not the easiest to maintain (e.g. in reprozip)
* Drop support for win-64
* Update copyright headers to 2016

== 2015 ==

=== December 30, 2015 ===
'''Updates'''
* Bokeh package finished
** Can output to Browser/IPython/Spreadsheet (Limited functionality in spreadsheet)
'''Items to Discuss'''
* Updating VisTrails dependencies
** Bokeh needs QWebEngine (Chromium) in Qt5 which requires PyQt5
*** Many plotting libraries only work in browsers
*** But Chromium may be a big and controversial dependency
*** Or create a browser version of the spreadsheet?
** Some users have requested Python 3
** Not backwards compatible?
** Target for VisTrails 3.0 with new interpreter?

=== December 16, 2015 ===
'''Updates'''
'''Items to Discuss'''
* Users list question
* [TE] Wrapping Bokeh
** Added bokeh property parser
*** complements numpydoc parser
*** Not all attributes are available, partially because I am using a pre-release version.
** Wrapped modules
*** bokeh.plotting finished (Backwards like matplotlib: Create plot then draw on it)
*** bokeh.charts mostly done (Missing arguments)
** QWebView mostly works (but no zooming or buttons)
*** It would be better to use external browser or QWebEngineView
** Added improvements to wrapper
*** Generalized port translations (Color/Path to native types)
*** Can use multiple docstring/property parsers simultaneously

=== December 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Looking into wrapper
** Will port TensorFlow
** Doing a pass on the wrapper code & doc
*** UX improvements
** Factorize high-level docstring parsers into core.wrapper? (sphinx, numpy, google)
** Problem with name vs module_name (fails sklearn tests because class_by_name() is broken)
** Looking into compressing specs, lazy registration of modules

=== December 2, 2015 ===
'''Updates'''
* [TE] Package wrapping
** Wrapped most of numpy/scipy using __all__
** Added class attribute and method access for classes (Can add to class or to separate inspector module)
** TODO: Document wrapping procedure

'''Items to Discuss'''

=== November 25, 2015 ===
'''Updates'''
* [RR] New interpreter is coming along
** Everything is a stream
** Task system, eventually work-stealing parallelism
** Streams no longer advance in lock-step
*** Allows for constructions like filter, join, sorted-merge
** depth>1 still to be tested, no current plan to allow this through the module interface
*** Through looping though, can do streams of streams

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapped most numpy functions (no polynomials)
** and half of scipy classes and functions
** Added functions manually from documentation (no parseable lists?)
** Focusing on data flow constructs (no property/method access for classes)
*** Using spec diff (empty for now) and dynamic parser (stores spec in .vistrails/)
** Python class/function wrapper now stable
** Add google doc parser?
*** Is there a parser available?

=== November 18, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Numpy class wrapping works
*** Basic type is List, since most types are array_likes.
*** TODO: More classes and functions
*** Some operations are in-place and some aren't, and docstring not super clear
*** [RR] It seems only methods mutate, and most have a numpy.xx function equivalent; just manually go through the methods and remove the mutating ones?
** Class wrapper is modular
*** Docstring parser and type string parser can be customized
*** Classes can have optional attribute/method ports
**** Inspectors and attribute/method modules can be created separately
** Use PythonCalc as an example
*** Can be re-implemented as a function with a parseable docstring
*** [RR] PythonCalc is just an example, and it might actually make sense to get rid of it, or do a proper math package with scalar operations (as separate modules, no combobox)
** [RR] TensorFlow to use wrapping as well
*** Very simple (only types 'tensor' & 'variable')

=== November 11, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapping numpy's classes using numpydoc (ndarray)
*** Wrapping constructor arguments, attribute getters/setters as module ports
**** Then how to access attributes afterwards?
***** Use input value port to class modules?
*** Wrap methods as modules? E.g., `ndarray.shape`.
*** Function wrapping is almost a subset of class wrapping
**** May be able to use the same parsing/execution methods
** VTK's non-getter/setter methods could be wrapped as modules
*** We could then remove extra logic in interpreter for keeping function order
** Bokeh uses autogenerated docstrings
*** We may be able to read the specification directly

* [RR] [https://github.com/VisTrails/VisTrails/pull/1138 TensorFlow package]
** Basic setup working, can execute the Mandelbrot example
** Will autogenerate the operations

=== November 4, 2015 ===
'''Updates'''
* [RR] Interpreter work requires a fix for [https://github.com/VisTrails/VisTrails/issues/1137 DB issue #1137]
* [DK] Kitware's Resonant [http://www.kitware.com/source/home/post/173]
** [https://github.com/girder/girder Girder]: data management system
** [https://github.com/Kitware/romanesco Romanesco]: execution engine, uses [http://www.celeryproject.org/ Celery] for task management
** Resonant Flow: web app for editing and executing workflows

'''Items to Discuss'''
* [TE] Added OSX Lion (10.7) VM on build machine using vagrant (seems ok with license?)
** New builds works on Lion
** Change the minimum requirement to 10.7?
* [TE] Package wrapping
* Added upgrade suggestions using 2 spec versions ([http://pastebin.com/30XUU8Gp example])
** using name edit distance to find matches
** Could use something better like port similarity for modules, and type similarity for ports
** Should write python upgrade code?
** Added spec to sklearn package
*** Can now diff spec versions and keep the spec static
*** There will be problems with downgrades and package versions

=== October 29, 2015 ===
'''Updates'''
* [TE] nightly-build-mac fixed (Needed to approve xcode license)

'''Items to Discuss'''
* [TE] matplotlib wrapper
** ported to general spec
** Diff can be used on general spec
*** Only needed minor changes
*** Fixed indexing bug that corrupted specs
*** Can now move diff tools to core/wrapper
** Add new plots?
*** New plots in mpl 1.3: eventplot
*** New plots in mpl 1.4: angle_spectrum, magnitude_spectrum, phase_spectrum', violinplot
*** No new plots in mpl 1.5 (from looking at boilerplate.py)

=== October 21, 2015 ===
'''Updates'''
* [RR] Alexis has arrived, will be working with [RR] on a more efficient interpreter

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package]
** Supporting multiple package versions
*** Check which version can be loaded [https://github.com/VisTrails/VisTrails/pull/1135 #1135]
*** We cannot show version requirements in the list of packages because old packages are loaded when importing the codepath
** Visual diff does not work well, but we can use the spec differ to see differences.
** Unifying vtk and matplotlib wrapping specs (WIP)
*** And porting matplotlibs spec differ to work on the general spec
*** Spec differ can then be used on vtk and other packages in the future
*** Will enable automatic upgrade generation
* [RR] Rework interpreter
** restore abstraction between interpreter/module code
** build looping, streaming, caching into the interpreter
** rework cache
** look into parallelism once basic functionality is there

=== October 14, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package] (adding numpydoc parser)

=== October 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/tree/fix-matplotlib-parser New matplotlib parser] (adding numpydoc parser)
** Added numpydoc attribute parser for plots.
*** TODO: Need better port spec reconciliation with call signature parser.
*** We can create a general numpydoc parser, but attribute types are unique to matplotlib.
** Needs package versioning
*** New spec will not support matplotlib < v1.4 due to changed path to axes classes.
*** Load spec version corresponding to installed matplotlib version?
*** Need version downgrades?

=== September 30, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Updating Matplotlib parser
** Matplotlib docstring parser fails on numpy docstrings
** I have [https://github.com/VisTrails/VisTrails/commit/eae8b0c16260810587e47c41cab53552cbb3cf0a added basic numpydoc parsing]
*** Only used by a few docstrings so far
*** Parsing uses many sources (class tables, signatures, ACCEPTS, method docstrings, definition parsing).
** Caswell said they were thinking about moving to traitlets, but this is not ready yet

=== September 23, 2015 ===
'''Updates'''
* [TE] VisTrails 2.2.3 released
** Also have pushed to PyPI, binstar, etc.
** Sourceforge vs. GitHub
*** should be able to host releases on GitHub
*** nightly binaries pushed to sf each night
*** old binaries?
* [TE] Re-wrapping MatPlotlib
** Keep static generation - Docstrings are brittle beween matplotlib versions
** Keep generating the executable classes - but create functions, not vistrails Modules
*** Why is there so much patching?
** Re-implemented Alternate PortSpec for InputPortSpec
*** It will now inherit specs from parent (No need to reimplement)
** Module upgrades?

'''Items to Discuss'''

=== September 16, 2015 ===
'''Updates'''
* [TE] Job Monitor tests and documentation done
** OK to leave document package in packages directory?

'''Items to Discuss'''
* [TE] Library wrapping: How to do code patching? [https://docs.google.com/drawings/d/1Sh3eOXot6v2y880jHKQrqXqAwr-0aoqYligg3z8G8MY/edit?usp=sharing Wrapping diagram]
** Insert code into module template (Old VTK code)
** Patch the library that is called (New VTK code)
** Somehow store code in spec and apply when executed?
*** Executed code needs at a minimum access to inputs, outputs, current class
*** Use standard input/output dict and obj reference that the code operates on?
*** Can this be done while keeping the execution abstract?

* Do new release now?

=== September 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* New release?
** [RR] wants reprounzip
** tej changes & doc
** job monitor & jobmixin fixes
** mongodb
** reprounzip
** warning: MplFigure type is int
** tabledata: add Reshape, DictoToTable & ListToTable, fix ListToTable with numpy arrays
** PythonSource can have same name for an input & output
** don't show spreadsheet at exit

=== September 2, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Limit autosaves? [https://github.com/VisTrails/VisTrails/pull/1126 #1126]

=== August 26, 2015 ===
'''Updates'''
* [TE] Added Job support to Parameter Explorations (Requested by Colin), and Mashups
** specify job ids, need to specify different ids for parameter explorations since they have the same version id
** how to deal with parameters passed in on command line
* [General] provenance: should be creating a new version when we execute workflow with changed parameters?
** currently, custom_params annotation stores this in provenance currently
** [RR] API doesn't record provenance if passing in parameters: http://git.io/vsAA5
'''Items to Discuss'''

=== August 19, 2015 ===
'''Updates'''
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [TE] Working on Job Monitor documentation

'''Items to Discuss'''
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [TE] Stop testing VisTrails 2.0?

=== August 12, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Build broken on Travis; because of IPython 4 released today? ([https://travis-ci.org/VisTrails/VisTrails/builds/75279795 build 992]; [https://github.com/VisTrails/VisTrails/issues/1123 #1123])

=== August 5, 2015 ===
'''Updates'''
* [TE] Fixes to Jobs
** Could not delete jobs
** Could not run job in group
** Job not reset when calling ModuleSuspended
** Added deleting job from context menu
* [RR] Writing documentation for everything [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

'''Items to Discuss'''

=== July 29, 2015 ===
'''Updates'''
* RR still looking into new interpreter thing
** Goal is to take out scheduling logic from Module so it can be split in multiple processes, and so that smarter strategies can be added in time
** This means some work on packages
** Spreadsheet can live in kernel process? Still some UI stuff that will take work (changing configuration, persistent archive's viewer, ...)
* [TE] Problems running examples [https://github.com/VisTrails/VisTrails/pull/1111 #1111]
** Testing of more examples requires additional packages on the test machines.
** Fixed faulty line-ending in PythonSource:s failing on Python 2.6.
** Test suite now testing SUDSWebServices (If web service is down, test suite will fail)
** preferences.py test failed reloading 'dialogs' package, switched to using 'URL'.

'''Items to Discuss'''

=== July 22, 2015 ===
'''Updates'''
* [TE] mailing lists back online
* [TE] Working on [https://github.com/VisTrails/VisTrails/issues/1107 #1107]
* [RR] Working on ReproZip package

'''Items to Discuss'''
* [RR] MongoDB package [https://github.com/VisTrails/VisTrails/pull/1106 #1106]
* [RR] Example for tej docs? [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

=== July 15, 2015 ===
'''Updates'''
* 2.2.2 released

'''Items to Discuss'''
* RR is considering executing everything in an IPython kernel (i.e. separate Python interpreter, like the one spawned for a notebook)
** It's a separate process that we can restart without restarting the app/gui
** We can isolate the execution environment (e.g. for the server)
** We can run the whole thing remotely (if your data is elsewhere, just run VisTrails locally and the pipeline elsewhere)
** Pipeline execution no longer makes the interface hang, it just makes the kernel hang (but that's fine)
** We can use notebooks as modules (probably way nicer than the PythonSource module)
** We can run multiple kernels so long as the ports carry things that are serializable
*** meaning we can put the multithreaded-interpreter without all the hacky parts it has now
*** we can run IPython kernels in all the languages IPython supports, [https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages currently 46]

=== July 8, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Buildbot github hook not working after IP address change
* [TE] No reference to VistrailsApplication ([https://github.com/VisTrails/VisTrails/issues/1103 #1103])
** [RR] Added PR [https://github.com/VisTrails/VisTrails/pull/1104 #1104]
* [TE] Reopening VT file after saving with bundled subworkflow won't offer subworkflow upgrade ([https://github.com/VisTrails/VisTrails/issues/1102 #1102])
** allow manual delete to fix right now
** fix this on top of the use-uuid branch
* [TE] Release VisTrails 2.2.1? ([https://github.com/VisTrails/VisTrails/blob/v2.2/CHANGELOG CHANGELOG])
** [https://github.com/VisTrails/VisTrails/pull/1093 output-modules-use-global-dir]
** [https://github.com/VisTrails/VisTrails/milestones/version%202.2 Current issues for 2.2]

=== July 1, 2015 ===
'''Updates'''
* [TE] PROV fixed
* [TE] Working on subworkflow issues
* [RR] Considering reworking the controller (log vs exception problem, retained upgrades causing interferences) and also the interpreter (IPython?)

'''Items to Discuss'''

=== June 24, 2015 ===
'''Updates'''

'''Items to Discuss'''
* UV-CDAT
* [TE] Can a cyclic workflow be valid? ([https://github.com/VisTrails/VisTrails/issues/1097 #1097])
** focus on disabling the ability to create cyclic pipelines because more things break than just this with a cyclic pipeline
* [RR] Relative paths ([https://github.com/VisTrails/VisTrails/pull/1057 #1057])
** This interacts with the new bundle; how do handle packing files inside the VT bundle?

=== June 17, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] current_version and reusing existing upgrades are broken ([https://github.com/VisTrails/VisTrails/issues/1095 ticket #1095])
** Could be that export to PROV is using an unflushed upgrade pipeline?
** current_version would then be correct.
** It may work to flush the actions before exporting?

=== June 10, 2015 ===
'''Updates'''
* DAT: fixed VTK issue on Linux and Mac
* Still crashes on Windows. Need help! Reminder: this works in the VisTrails spreadsheet (QCellPresenter), although no widget get changed there during a drag
** Is it a VTK bug?
** Is it simply impossible to change widgets during the drag, should we do it a different way?
** Did I miss something that is done in VisTrails but somehow not in DAT?
** Low prio, UV-CDAT doesn't run on Windows anyway

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 Updated pull request])
* Single instance code and batch mode

=== June 3, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 pr])
** Requires fixes to command line parameters, Output modules, and batch mode
** How to test this
** Updated missing/outdated flags
** Fixed view issues when generating graphs
* [TE] batch mode
** SpreadsheetOutput not enabled in batch mode. Should we check is_running_gui instead?
** Other instance setting flags from caller
** Is graphsAsPdf replacing spreadsheetDumpPdf?
** graphsAsPdf true by Default?
** Batch mode executing by default (Not needed when generating graphs)
** Re-added workflowInfo as withWorkflowInfo for writing graph and xml workflow
** [DK] batch mode should be outputting to files or stdout, shouldn't always trigger SpreadsheetMode
** execute flag, maybe make execution the default and allow a "--no-execute" if you only want to capture graphs, for example

=== May 27, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] API question
** http://lists.vistrails.org/pipermail/vistrails-users/2015-May/000357.html
* Status of DAT
** Can add VCS plot to DAT but need to work on configuration windows
** Documentation for graphics templates for UV-CDAT/vcs?
* Qt support?

=== May 20, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Reviving the DAT, integrating scripting & porting UV-CDAT!
** On [https://github.com/VisTrails/DAT GitHub] ([https://github.com/VisTrails/DAT/issues issues])
** Merging 2 years of development taking longer than expected, but getting there. The plan is to get the patches in VisTrails and never fork again, we never want to get in UV-CDAT's situation (and don't need to).
** VTK cell works fine on Linux but there was flickering on Mac & Windows before; still issues on Mac (Windows status unknown)
** Can get a VCS plot soon (but will need VTK cell fix)
** Integrate in UV-CDAT's build system (so we have cdms, VCS, ...) -> RR can do this, low priority
** How do we integrate scripting?
*** We want to be able to seamlessly make changes to a plot by changing Python code
*** Define new plots by entering Python code without writing modules/packages?
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 13, 2015 ===
'''Updates'''
* [RR] Test skipping whitelist ([https://github.com/VisTrails/VisTrails/pull/1069 #1069]) -- low priority
* [RR] Custom matplotlib modules can't be compatible with both 2.1 and 2.2 ([https://github.com/VisTrails/VisTrails/issues/1067 #1067]); should be fixed for ALPS ([https://github.com/VisTrails/VisTrails/issues/1070 #1070])

'''Items to Discuss'''
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 7, 2015 ===
'''Updates'''
* [RR] Export/import workflow to Python working!

'''Items to Discuss'''
* [Claudio] UV-CDAT
** The UV-CDAT project is the biggest user base of VisTrails
** VisTrails package management provides a lot of friction towards people plugging in their code
** Need to make it easy to integrate your random Python scripts in the system without having to deal with all the boilerplate, at least in the first step
** [RR] argues that modules are still good; UV-CDAT shouldn't move towards a purely script-based backend
** [RR] export/import with Python could reduce a lot of that friction by allowing 1) to edit workflow as Python 2) to open up boxes automatically if needed code doesn't match actual modules
** ...

=== April 29, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] <strike>Abstractions</strike> subworkflows status ([https://github.com/VisTrails/VisTrails/labels/subworkflows tickets])
* [RR] matplotlib compatibility (2.1 & 2.2), [https://github.com/VisTrails/VisTrails/issues/1067 #1067]
** RR to try and fix ALPS matplotlib modules

=== April 22, 2015 ===
'''Updates'''
* 2.2.0 has been released!
* Windows issue (via email from Ryan)
** issue with manifest file (may be a new file in VTK6?)
** Tommy has regenerated new Windows builds
* Binaries, pypi, and conda released
* [RR] Export as script
* Python sources using VTK need to switch to SetInputData (users should be aware of this)

=== April 15, 2015 ===
'''Updates'''
* Ready for 2.2.0 (apart from binary/deps issues)
** Missing some libs (scikit-learn, tej, tdparser, SQLAlchemy+connectors
** Windows: runvistrails.py is no longer used, so the PATH is wrong
** Windows: pip is broken, but it probably wouldn't work anyway because of permission issues (disable this?)
* Queries, upgrades and getPipeline() usage ([https://github.com/VisTrails/VisTrails/issues/1054 #1054])
** Getting a pipeline with getPipeline() is not safe: it might return an invalid pipeline
** This is used in many places throughout the code, like queries
** Upgrading would require going through the controller, but that creates new actions
* [TC] Avoid copying a module's output if it's used as input by exactly one downstream module ([https://github.com/VisTrails/VisTrails/issues/1060 #1060]) (useful for big numpy arrays you can update in-place)

=== April 8, 2015 ===
'''Updates'''
* [DK] Merged RR's changes for output modules (1012 and 1013)
** RR will merge remaining changes, then create v2.2 branch!

'''Items to Discuss'''
* BNL need numpy array to VTK image
** Looks like VTK has some helpers for this
** We will help if issues arise
** Will contribute back to VisTrails package
* Upgrade issue: [https://github.com/VisTrails/VisTrails/issues/1017 #1017]
** Automatic upgrades should happen between versions of provided upgrades
** Our existing upgrades work around this so it doesn't need to be 2.2.0
* Corner-case VTK modules
** No longer need VTKCell input port, so don't interfere with registry and API anymore
** Still work weirdly, people probably shouldn't use them
** But we have lots of clunky modules since we wrap the whole of VTK; some people might rely on this and know how to use them, let's keep them anyway
** Ready for 2.2.0

=== April 1, 2015 ===
'''Updates'''
* [RR] UV-CDAT: bugfixing for 2.2, long-term plans: implement scripting import/export in VisTrails, port to UV-CDAT
* Possibly, try to move to regular VisTrails to use new features

'''Items to Discuss'''
* 2.2 release: nothing much is pending anymore, release next week?
** [TE] vtkExporter classes [https://github.com/VisTrails/VisTrails/issues/1032 #1032]
** [RR] Hiding upgrades in version tree might make it (or might be 2.2.1 so we can test it out) [https://github.com/VisTrails/VisTrails/issues/949 #949]
** Output modules changes to go in
* add note to documentation about order of parameters in VTK
* add issue about exporter upgrades if not already there

=== March 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* 2.2 release
** Checklist on Github: https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist
** Review output modules
** RR has a couple more issues to fix
** Ready to go -- sign app package for OSX? [https://github.com/VisTrails/VisTrails/issues/984 #984] We need access to the Apple Membership team

=== March 18, 2015 ===
'''Updates'''
* [TE] VTK6 works

'''Items to Discuss'''
* [RR] Release v2.1.5 with backported tabledata?
** MTA example needs updated tabledata (for JoinTables)
** Google Maps package still not available
* [RR] Work torward v2.2.0?
** changes:
*** new persistence
*** API changes
*** output module changes (upgrades?), maintain cells but try to upgrade
*** not wrapping stuff
*** VTK6? yes
*** JobSubmission stuff?
*** relabeling for upgrades [https://github.com/VisTrails/VisTrails/issues/949 #949]
** makes sense, needs the tree view code to be updated, check selection
** See [https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist 2.2 checklist]
* Discussion of [https://github.com/VisTrails/VisTrails/issues/1016 #1016]
** plumbing between outputs and output modes, how to define a mode that works for many outputs without writing for each output?

=== March 11, 2015 ===
'''Updates'''
* [RR] persistent_archive done; merge? ([https://github.com/VisTrails/VisTrails/pull/755 #755])
** note about the focus events for widgets
** TE be aware of file_archive for future binaries that include persistent_archive
* [TE] [https://github.com/VisTrails/VisTrails/pull/998 New VTK package] finished

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails? (see last week; decision needed)
** RR email to JF about this
** yes; email sent to Github
* [RR] Switching order of output ports ([https://github.com/VisTrails/VisTrails/pull/1006 #1006])
** added port specs are sorted at a separate spot (Module.*_port_specs properties) than those in the registry (which are sorted in the registry), but those two lists are just combined without respect to sort keys
** need to determine whether the two lists should be merged or remain distinct
** should make sure that order of input ports and output ports makes parallel connections for things with same order
** DK suggests breaking backward compatibility here: workflows still run, can fix easily if a problem in an existing package.
* [RR] Question about output modes ([https://github.com/VisTrails/VisTrails/pull/1007 #1007]), how to integrate in API ([https://github.com/VisTrails/VisTrails/pull/24 #24])
** Should ImageFileMode be removed? ("image" is not a mode, "file" is)
** ImageOutput missing?
** Feel free to change how formats works
* [TE] Test suite segfaults on Fedora 17 virtualbox. Install newer version? (Support ended in 2013)

=== March 4, 2015 ===
'''Updates'''
* [TE] VTK wrapper
** Works on VTK 5.10
** Still need to test VTK 6
** New general wrappers for python functions and classes

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails?
** When [http://i.imgur.com/UTY2qfg.png filing a pull request] from UV-CDAT/VisTrails, VisTrails/VisTrails is selected by default
** People keep forgetting to change the default ([https://github.com/VisTrails/VisTrails/pull/956 #956] [https://github.com/VisTrails/VisTrails/pull/968 #968] [https://github.com/VisTrails/VisTrails/pull/999 #999] [https://github.com/VisTrails/VisTrails/pull/1000 #1000] [https://github.com/VisTrails/VisTrails/pull/1003 #1003] [https://github.com/VisTrails/VisTrails/pull/1004 #1004] [https://github.com/VisTrails/VisTrails/pull/1005 #1005])
** Only way to change that is to not have it marked as a fork of VisTrails/VisTrails
** Github staff [https://gist.github.com/remram44/b364c24ef1e462ce6e2f can make that change for us]; should we do it?
** Juliana: comments on this? visibility vs. convenience/annoyance for developers
* [RR] What about [https://github.com/VisTrails/VisTrails/issues/991 #991]?

=== February 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] vtkviewcell for infovis support, can we unify with VTKCell?
** need to test this
* [TE] vtk wrapping
** Mostly finished
** VTK 5.10 produce incorrect results with old wrapping
*** Old wrapper is based mostly on VTK 4
*** Most vtk_examples affected
*** [http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Replacement_of_SetInput]
*** should be able to upgrade from SetInput to SetInputData (need to drop GetOutput and replace with self ports)
*** can we change vtkInstance to just return self and not wrap things
** terminator example not working under 5.8?
* How does VTK wrapping fit into general wrapping framework?
* [RR] new persistence package

=== February 18, 2015 ===
'''Updates'''
* [RR] New VisTrails API and IPython integration ([https://github.com/VisTrails/VisTrails/pull/24 #24])

'''Items to Discuss'''
* [TE] VTK wrapping
** [https://gist.github.com/rexissimus/16b74693545b5e7c1035 Benchmarking vtk package]
*** Old: 24.7 seconds
*** New: 10.5 seconds (Except first time that adds 8 sec)
**** The parsing that calls is_abstract (that tries to instanciate all vtk classes) is now only run the first time.
**** get_items_from_sigstring takes 2 seconds, maybe we can use a lookup dict for already computed sigstrings?
** Now using a general python function wrapper
*** VTK classes are wrapped into python function that does not depend on vistrails
*** VTK functions can be executed without vistrails
*** The spec maps functions into vistrails modules, but can also describe wrapping
*** A general python function wrapper that supports
**** kwarg inputs
**** single, list, dict outputs
**** callback for progress reporting
**** temporary file generator for using FilePool
**** optional output generation
*** Creating specs:
***** Create spec by hand
***** Auto-create spec outline (TODO) and manually finish it
***** Dynamically create spec (VTK)
***** Implement documentation wrappers (Can use scikitlearn wrapper to wrap numpydoc) (TODO)
***** Classes as bad functions needs to be wrapped in new functions before they are wrapped. This is different for each package.
****** Classes is hard: Like VTK, and matplotlib. Scikit-learn does still not wrap classes
***** Spec diffing and patching could be done using code from matplotlib.
** Still needs upgrades from old VTK package
*** Is it possible to dynamically wrap functions, e.g, you see a SetFunc and just remove the 'Set' prefix. Or do you need to create a complete mapping?

=== February 11, 2015 ===
'''Updates'''
* Update from Friday's meeting
** discussed VisTrails internals
** discussed wrapping
*** xml discussion, hard to modify because tied to db code
*** TE has made it possible to add the schema-defined attributes to the intermediate representation
*** higher-level operations on the port specs
** make sure the simple case works
*** [JF] take a simple package with documentation and figure out what the base case for wrapping is

'''Items to Discuss'''
* [TE] VTK wrapping
** Dynamic loading works
** Reading XML is fast enough, but [https://gist.github.com/rexissimus/8272d3c776ccfa115d82 unserializing data is slow]
** Working on patterns for patching
** Matplotlib has many advanced patterns like argument ordering, nested arguments, alternateSpecs, output types.
*** Having all this in a general wrapper might confuse users?
** [RR] Delay module (except for identifiers) until you need it---e.g. don't deal with port specs, etc. until necessary
* Scripting Support [https://github.com/VisTrails/VisTrails/pull/950 #950]
** [RR] Issue with getting code from modules
** Design a simple solution
** [JF] Couldn't you use modules as black boxes without conversion, just to call into modules/subworkflows easily from e.g. IPython?
*** [RR] This is a job for the API, and a very separate use case. See [https://github.com/VisTrails/VisTrails/pull/24 #24]

=== February 4, 2015 ===
'''Updates'''

'''Items to Discuss'''
* Wrapping
** Format to use? Currently XML (like current matplotlib)
*** JSON and YAML have simple "to python dictionary" methods
*** But don't stream
*** YAML a lot easier for humans
** [DK] vtk-new-package also changes parameter names, creates enumerations
*** intermediate schema needs to be extensible
*** packages will want to store there specific infos for compute() method generation
*** also might have specs-altering info, like matplotlib's alternateSpec
** representation to code , registry already has schema for some aspects
** [RR] We might want to see if Module subclasses can be created lazily
*** no need to create all the classes just to register them in the registry and never actually use most of them
*** future effort
* [RR] Where should VisTrails packages live?
** tej installs as 'vistrailspkg.tej', TE installed it as 'userpackages.tej'
** Currently, standard packages are 'vistrails.packages.', user packages are 'userpackages.' and packages loaded through pkg_resources might be anything
** [RR] Use 'vistrailspkg.' everywhere?
** Long-term effort to simplify package distribution/installation (and have VisTrails get them automatically?)

=== January 28, 2015 ===
'''Updates'''
* T. Caswell to come visit on Fri 6 to discuss wrapping work

'''Items to Discuss'''
* [TE] New VTK wrapping
** Current code by DK seems a good deal faster
** Generates XML that can be patched/tweaked, generates Python code from it, VisTrails only loads generated Python code
** RR would rather have VisTrails load intermediate representation (= XML) directly, wants to make sure this is not slower
** The goal is to turn the intermediate step into something generic that would be used for every wrapped package (vtk, numpy, matplotlib, sklearn, java) instead of each having its own
** TC has its own code at [https://github.com/Nikea/VTTools/blob/master/vttools/wrap_lib.py github:VTTools] which parses numpy docstrings and generates modules, doesn't yet handle classes or persist anything
* Web crawler
** Right now, TE starts jobs for "start crawler", "stop crawler", "install classifier"
** RR would rather have the crawling be a job as far as VisTrails and tej are concerned
** The whole thing would be one pipeline: load examples, train classifier, start crawler [check for job, kill previous one, upload model, start processes], get snapshot, visualize
*** Need some support in tej and job submission system: long-running jobs, stop a job (wait for it to finish?), restart a job even though results are cached

=== January 21, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Unified wrapping method discussion [https://github.com/VisTrails/VisTrails/issues/991 #991]
** TE to work on reusable method with intermediate representation, starting with VTK
* [RR] Examples for scikit-learn: JF has an old example using Weka with parameter exploration (not currently in source tree)
** AM's examples are enough
* [AM] scikit-learn package is done, merge it in? [https://github.com/VisTrails/VisTrails/pull/955#issuecomment-70286788 #955]
** RR will merge
* [RR] What should copyright headers say? [https://github.com/VisTrails/VisTrails/pull/994#issuecomment-70173935 #994]
** Let's keep everything in there: Utah/Poly/NYU

=== January 14, 2015 ===
'''Updates'''
* [TE] Working on classifier
* [RR] Scripting integration, work in progress

'''Items to Discuss'''
* [RR] Unified wrapping method discussion ([https://github.com/VisTrails/VisTrails/issues/991 #991])
** Let's talk next week, [AM] and [DK] are not here

=== January 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* make sure that we address critical issues, questions, and pending review branches in a timely manner
* scripting support
** [RR] no issues if we want to just keep annotations in the generated code to allow the link back to a workflow
** [RR] can translate from workflow to script, working on script to workflow
** will work for parameter value changes, structural changes require changes to the annotations
** need to publish best practices here
** would be cool to do looping in scripts (easier interface than with workflows)
* notebook support (convert form notebook to workflow)
** RR will sync with FC on this
* Issue with console in built-from-scratch
** [TC] iPython rearranged some of the completion stuff in 2.2 and 2.3
** binary has old version of iPython -> 1.0.0, should we update?
* [TC] automated wrapping of numpy and scipy
** discovered a bunch of malformed documentation in numpy and scipy
** has github repo for vistrails tools
** example modules wrap a bunch of R stuff (not baked in, just how things are)
** will be pushing wrapping logic up
** port names forbidden (window and domain)
** have an import hook to get from yaml directly to VisTrails Modules
** should work for any python modules with well-formed numpy docstrings.
* [Action] should make it clear in documentation that Constant now means serializable not that the value doesn't change (e.g. List)
* [TC] might be interesting to try to build components of matplotlib and accumulate in figure (long-term project, but thinking about how this might work)
* [TE] build and build scripts
** completely automatic, buildbot
** need to set the build machines for the environment we want for the binary
** would virtualenv work here?
** [TC] anaconda can pin versions, potential path to test different configurations
** Q: upload nightly binary builds? A: makes sense, make sure they are well-labeled
* sourceforge stats: e.g. http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07
* package issues (see Remi's message)
* [TE] Scope of tej
** Support single ssh commands?
** Queue can be used as a remote machine (crawler is using queue.call*)
* SourceForge stats: http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07

== Older meetings ==
* [[Development/2014]]
* [[Development/2013]]
* [[Development/2012]]
* [[Development/2011]]
* [[Development/2010]]

Development

2016-08-02T13:53:35Z

Tommy: /* 2016 */

<div class="nonumtoc toclimit-1">
__TOC__
</div>

See also the [https://github.com/VisTrails/VisTrails/wiki/Development Github wiki]

== 2016 ==
=== August 3, 2016 ===

'''Updates'''
* [TE] Wrapper patches now stored as [https://github.com/VisTrails/VisTrails/blob/python-wrapper-script-patches/vistrails/packages/vtk/vtk_wrapper/vtk_patch.py python code]

'''Items to Discuss'''

=== July 27, 2016 ===

'''Updates'''

* [DK] DB bundle serialization implemented

'''Items to Discuss'''
* [TE] Finished using patch in script [https://github.com/VisTrails/VisTrails/tree/python-wrapper-script-patches python-wrapper-script-patches]
** locale?
** [https://gist.github.com/rexissimus/f0d6b026aa5a2a770847f3321744645d new patching example] vs [https://gist.github.com/rexissimus/b28d83ae516a519167f5751bb8ab3739 old patching example]
** [https://github.com/VisTrails/VisTrails/blob/python-wrapper-script-patches/vistrails/packages/vtk/vtk_wrapper/parse.py#L135-L273 Example of new patches]
** Legacy '.vtkInstance' is now added as a patch "self.vtkInstance=self" (see new patching example)
** [https://github.com/VisTrails/VisTrails/blob/python-wrapper-script-patches/vistrails/core/scripting/api.py New api for executing standalone modules]
*** Accessing module was disabled for core/api, but a different api for this is probably better anyway.
*** api.Package now gives [https://gist.github.com/rexissimus/f0d6b026aa5a2a770847f3321744645d#file-new_patching-py-L26 directly callable module compute functions]
*** Only works on modules not using interpreter functionality ('.interpreter', etc.)
**** for zip file modules and others that need temp files and use the interpreter for this, need to modify the module, but could work around with python libraries for managing temp files
** Fixed more renaming issues - [https://github.com/VisTrails/VisTrails/blob/python-wrapper-script-patches/vistrails/core/scripting/scripts.py#L63-L64 function argument names should not be replaced]
** Still need to do something nicer for the patch formatting
*** patch keys currently contain non-python-variable characters but this can be fixed
*** Need to replace string template with python variables that is replacable using RedBaron
**** Patches could then look like:

def vtkInstance():
self.vtkInstance = self

=== July 20, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] New patch method for python-wrapper [https://gist.github.com/rexissimus/009b303e4cadcd4b8f2fec6cf848cb2b example]
** A patch is a string template with self/input/output variables for patching a class method
** Patches are stored in xml specification
** Patches are assigned to methods in ClassSpec's
** Used both for execution in vistrails and when exporting as script
*** Executed with "exec" when run in vistrails
*** Turns patches into natural calls in script
** Wrapping VTK library no longer needed
*** Removes ".vtkInstance" (Automatically removed from PythonSources and vtkInteractionHandlers)
** Removed fix_classes.py (Subclassing of VTK classes to patch methods directly)
** Also used for port translations (With patch names like "basic:Color#input") (No more ugly input_t method definitions)
** TODO's
*** Add to export_as_script
*** Patch Modules that represent Python functions as well

* [vistrails-users] Read data from SQL example?

=== July 13, 2016 ===

'''Updates'''

* [DK] bundles on sql-alchemy branch
** Bundle, BundleMapping, and BundleSerializer
** New BaseSerializers to deal with versions of directory, zip, db serializers
** Can register the BundleSerializers with the base serializers
** Translation between bundle versions
** Bundle.add_object "just works" if an appropriate mapping was registered

'''Items to Discuss'''
* [TE] Simplified running module using API for scripting [https://gist.github.com/rexissimus/b28d83ae516a519167f5751bb8ab3739 example]
** API Module can be executed using '''compute''' method
*** Takes list of outputs to compute + inputs as keyword arguments
* Status of general cell synchronization (vistrails-users)

=== July 6, 2016 ===

'''Updates'''

* [DK] Working on bundles

'''Items to Discuss'''
* [TE] Using vistrails API in scripting [https://gist.github.com/rexissimus/034d9c4dedc3299a079e84981dedd8c7 example 1 (API with VTK)] [https://gist.github.com/rexissimus/a4a9ca6c08d4058c64967d2b35415fd5 example 2 (DownloadFile only)]
** Call module in script using vistrails API
** Can be used when no export method is defined.
* [TE] [https://github.com/VisTrails/VisTrails/commit/c76c109349769fee1280f85c22678380a2f9cd39 Server news bug] Critical?
**[RR] No, unreleased
* [DK] New bundle organization
** BundleMapping contains individual mappings from raw objects to BundleObj
** Must be separate in order to have in-memory, separate from serializer settings

=== June 29, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Export VTK as python script
** Works on Terminator (Isosurface, Volume Rendering, clipping plane, combined rendering) [https://gist.github.com/rexissimus/16caf5200802e150296f62a0c7844c5a example]
** Preludes (imports) still need improvements
** Works with vtkInteractionHandler (clipping plane)
** Resulting clipping plane is incorrect? (supposed to hide one side of the plane)
** vtkRendererOutput Uses VTKRenderWindow as output
*** Should support different output modes?
*** Does not work with multiple outputs (Next cell is displayed when current is closed)
*** Uses wrapped vtkInstance (as vvtk)
**** Create new patch system with code that can be used both in vistrails and in a python script?

=== June 22, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Fix for upgraded analogies (PR [https://github.com/VisTrails/VisTrails/pull/1177 #1177])
** Uses module location to find module remap (The best we can do right now?)
** Also fixes remapped port names for connections to existing modules
** May still fail on complex upgrades like adding a function on an upgraded module that has a different port name

* [TE] Working on exporting wrapped libraries (VTK)

=== June 15, 2016 ===

'''Updates'''
* [TE] Added depth logic to python script exporter ([https://github.com/VisTrails/VisTrails/commit/50f220e4f6abe5a7bb8689f73f456f43df2dbc12 full commit])
** Fully implements connection merging and list looping

'''Items to Discuss'''

* [TE] Making analogy work on upgraded workflows ([https://github.com/VisTrails/VisTrails/issues/1175 #1175])
** Analogy only works We need to use the non-upgraded action chain
** But pipelines need to be valid (matcher uses module portspecs)
** Tried to get upgrade remap from upgrade action, but this seems impossible
** Use module location instead?
*** Location should be identical for one-to-one module upgrades

=== June 1, 2016 ===

'''Updates'''
* VisTrails 2.2.4 announced (finally)
** 5 survey replies
** 47 downloads last week

'''Items to Discuss'''
* [TE] Export VTK as script (python-wrapper)
** to_python_script
*** needs the pipeline (or at least the connections)
**** Should not generate code for any possible VTK method (exporter detects which ports is used in the source)
**** VTK needs to know connection order
**** Adding functions directly to the script results in nicer code
** Add support for multiple input connections
** Add support for list looping

=== May 25, 2016 ===

'''Updates'''
* Mailing-list fixed
* Getting stats from the "server news" mechanism (via [https://github.com/remram44/apache-log-info parser])

'''Items to Discuss'''
* [RR] Alexis doing writeup on VisTrails, curious about interesting streaming use-cases (and potential future users)
* [TE] Union ports
** Show union ports in pipeline (DEMO)

=== May 18, 2016 ===

'''Items to Discuss'''
* [TE] mailing list still down - Julio working on it
* [TE] Improved union port
** New schema 1.0.5 adds portitem.union string attribute
** Works with pipeline view, parameter exploration view, and mashup view
** Should work well for matplotlib
** Use with VTK ports?
*** It uses [item_1,item_2] style ports usually with different tuple length.
* [TE] Remove emacs dependency from db generate [https://github.com/VisTrails/VisTrails/issues/1173 #1173]

=== May 11, 2016 ===

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]
** GUI-based solution [https://github.com/VisTrails/VisTrails/tree/union-port Branch union-port] Demo?
*** Shows single port for all ports with same sort_key
*** Select specific type when adding/showing
*** Only one type should be visible on the module at any time
*** Making tuple parameters union types is probably too complicated
*** Should work with alternate specs like matplotlib (if sort_key is defined correctly)

* [TE] Feature suggestion: Let connections connect to functions/parameters
** Show functions and parameters as ports and toggle port visibility directly for functions and parameters
** Use separate views for ports and functions (like before)
*** Allow rearranging of functions
** Pros:
*** Supports ordered connections. Create 2 functions, make them visible as ports, make connections to them.
**** We can also have, e.g., a line joining the ports on the module to indicate they are part of a list.
**** Makes List module simpler
*** Connect to parameter in tuple
*** Functions that are visible on the module can connect to an actual function, and not just to the first one it finds.
*** Can replace operation modules (in python-wrapper) in some cases for, e.g., numpy.
** Cons:
*** Interface more complicated and crowded
*** More difficult for users to grasp?
*** No immediate use case
*** Makes no union type for tuple parameters a bigger problem.

* [TE] Publish user survey?
** No response from vistrails release yet
** Not announced on vistrails-users yet.

=== May 4, 2016 ===
'''Updates'''
* VisTrails 2.2.4 released

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]

=== April 27, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Wrapping Bokeh
** New method type "operation"
*** Transforms Figure->Glyph->Output into Glyph->Figure->Output
**** Glyph sets function name and arguments as output
***** Not serializable, but should always be computed together with the subject of the operation.
**** Figure applies Glyph operation on itself
*** Useful for matplotlib?
**** matplotlib currently find actors by searching upstream?
**** But this is more difficult since matplotlib is not function-based.
** New "union" port type
*** Turns "x(float), x(list)" into "x (float, list)" and uses first set value
**** Uses only first value in tuple
**** Bokeh have many properties that support (list, string, Float)
*** Does not work with depth=1 types (e.g. Float of depth 1)
**** Turn Depth 1 types with known type into lists?

* [TE] New bugfix release
** Finalize survey

=== April 20, 2016 ===
'''Updates'''
* Merged upgrade fixes
** Now has infinite loop test
** loop test now correctly loops 5 times
*** remap_module used wrong (current) package version when creating ModuleDescriptor
* Fixed multi-step group upgrades (PR: [https://github.com/VisTrails/VisTrails/issues/1168 #1168])

'''Items to Discuss'''
* New bugfix release
** Merge usagestats
** Need to finalize survey

=== April 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Chaining upgrades done ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Replace "Upgrade" description annotation with "upgraded_from" annotation to identify which tags to hide?

* [TE] Iterating handle_invalid_pipeline ([https://github.com/VisTrails/VisTrails/pull/1165 #1165])
** Not based on [https://github.com/VisTrails/VisTrails/tree/chain-upgrades-loop chain-upgrades-loop]
** Cherry-pick test to preserve source?
** Need maxPipelineFixAttempts option?
*** The code is now smarter about recursion, so max attempts will "probably" never be reached.
** Need [https://github.com/VisTrails/VisTrails/commit/0ef0667426937eddb1d1c1e397f0657ffec039a9 debug messages]?
*** Would need to be moved into handle_invalid_pipeline

=== April 6, 2016 ===
'''Updates'''
* [TE] Query View improvements
** Done except for displaying "Version Info" and #1164
* [RR] Working on finishing new interpreter (finally!)

'''Items to Discuss'''
* [TE] Chaining upgrades ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Try latest upgrade first, then previous.
** If all fail, select latest upgrade?

=== March 30, 2016 ===
'''Updates'''

'''Items to Discuss'''

* [TE] Query View improvements
** Unified do_version_switch and get_upgrades as validate_version()
** Problems with query view using its own controller
*** Fixed module info not being displayed for query results
*** Still no version info for query results
*** Still an issue with version query view not being updated

=== March 23, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Usage reporting almost ready to go
** Need to record whether specific features are used: paramexpore, mashup, query
*** [DK] Record if LaTeX extension is used? But hard to distinguish from direct batch invocation
** How to record size of vistrail?
*** [DK] IdScope already walks over vistrail, use that
*** but total number of modules and versions doesn't give an idea of average size of individual pipelines

=== March 16, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Upgrades in Query Mode
** Now using code similar to do_version_switch
*** Uses handle_invalid_pipeline
*** Differences: Not using current_pipeline, flushes changes
*** New controller method get_pipeline optimized using cached pipelines (but not current_pipeline)
*** Integrate to avoid repeated code?
*** Use this for query mode?
* [TE] VisTrails 2.2.4 ready for release?
** tej package updated. Others?
* [JF] upgrades and the version tree
* [JF] provenance in Jupyter
* [DK] bundles: [https://github.com/VisTrails/VisTrails/pull/1092 #1092]

=== March 9, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixing search mode
** String query now matches all by default
*** This caused pipeline queries to never match
** String query can search: User/Notes/Tagname/Time/Module name
*** Should we search module names by default? (Disabled by default because it is expensive)
*** Fixed notes search
** '>' parameter queries in documentation but has been removed
** Fixed module matches for upgraded pipelines (By not upgrading pipeline)
*** Upgrades still a problem
*** Add "Upgrade all menu option?" (Or upgrade all on open when `hideUpgrades`)
*** [JF] Allow search on past tags

* [TE] Create new bugfix release
** Finish querying
** Path issue on windows

* [DK] Look into sqlalchemy and new bundle branches

=== March 2, 2016 ===
'''Updates'''
* [TE] Fixed cache bug with port specs
* [TE] VisTrails Next
** Most packages now work
** No qgis for Python 3

'''Items to Discuss'''
** Always dereference symlinks? [https://github.com/VisTrails/VisTrails/issues/1146 #1146]

=== February 23, 2016 ===
'''Updates'''
* [TE] Fixed PythonSource 100% CPU bug
* [TE] VisTrails Next
** Updated [http://opendap.co-ops.nos.noaa.gov/axis/webservices/wind/ NOAA Web Service] examples
*** Now uses REST service, tabledata, and Google Maps
*** Web Service replaced with DownloadFile

'''Items to Discuss'''
* [RR] Couple of fixes are in for API, and tej&reprounzip on the Mac binary. Also new release of tej, and working on anonymous usage reports.
** New 2.2 release soon?
* [RR] Anonymous usage reports
** Sends out info like number of modules & versions, packages used, Python & libs versions, execution time, specific features [https://github.com/VisTrails/VisTrails/pull/1154 #1154]
* [JF] Bring in noWorkflow to track variable dependencies, for the considered Jupyter integration?
* noWorkflow - provenance for python scripts
** Recent work on tracking dependencies
* Also integrates ReproZip with Jupyter
** [http://mybinder.org mybinder]
*** Use with ReproZip to automatically build Jupyter notebook interfaces
* Daves comments on Jupyter integration
** It is possible to identify cell order on the server side
** Not trivial to track order of cells on client side
* How does Galaxy workflows relate to VisTrails?
** Packaging in Galaxy is hard
** Galaxy for biomedical workflows, difficulty making it general
* Action items
** How difficult to track cell dependencies in Jupyter notebooks?
** Use noWorkflow to track cell dependencies?
** How difficult to modify mybinder to use ReproZip packages?

=== February 17, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixed Group memory usage
** Modules in groups are supposed to be freed when done executing
*** Prevented by logger that stored references to the modules (fixed, now using id(module))
*** Prevented by list iterator bug that stored list of modules on the 'self' port bug (fixed)
* [TE] VisTrails Next
** Removed deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** PythonSources will be upgraded
*** Fixes for Python < 3
*** fixes for VTK < 6
** TODOs
*** Remove RemoteQ
**** Port Hadoop to tej (Already have pbs)
*** Merge package wrapper
*** Finish SQLAlchemy branch
*** Finish new bundle branch
** [JF] Will contact Jeff and Matthias about moving to Python 3
* [JF] Query by Example is broken
* [JF] VisTrails Data Cleaning Project
** Use VisTrails to process and explore task-specific data while keeping provenance.
** Remi's Idea
*** Use VisTrails as the backend in a Jupyter notebook
*** Overcome problems with executing cells in random order
**** Interesting research topic, but little interest has yet been noted
*** Interesting to study how such a notebook would be used (Is there notebook usage data available?)
*** Impose restrictions to notebook cell boundaries
*** It will only work for functional operations
*** Can we fix, or detect, non-functional (mutating) operations?
*** Analyse code and data flow and see if it mutates data in unexpected ways?
*** Mutable operations can be created in many ways in Python
* Next meeting Tuesday 11:30

=== February 10, 2016 ===
'''Updates'''

'''Items to Discuss'''
* VisTrails Next
** Test suite passes
*** Python 3 less deterministic, module upgrade order random.
** [RR] updating packages: Reprounzip (pushed), tej, persistent_archive, ...
** All of our packages should run fine :)
** VTK thumbnail comparison works
*** Rendering bug on some systems
**** QVTKCell now inherits QGLWidget
*** Old thumbnails had wrong height due to spreadsheetwindow being too small
**** Fixed by regenerating thumbnails
*** Silenced deprecation messages when generating modules
*** Many new classes in VTK 7
** Remove deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** Will break existing PythonSources
**** Try to upgrade?
*** Old-style packages
**** Or only allow a new style, like __init__.py renamed to info.py? (merge with identifiers.py?)
***** Read info.py without importing package?
*** Fixes for Python < 3
*** Fixes for Qt < 5
*** fixes for VTK < 7
*** Remove self port?

=== February 3, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] [http://lists.vistrails.org/pipermail/vistrails-users/2016-January/000402.html Rendering a .pvd (ParaView) file?]

* VisTrails Next
** All tests but thumbnail comparison passes
** Still issues with gui and more packages needs to be tested
** PythonSource and MplSource upgraded with lib2to3
** Keep contrib packages? Update?
** [https://blog.kitware.com/vtk-7-0-0/ VTK 7 is released]
*** Supports Python 3
*** Will hopefully get into conda and others soon
*** Deprecates a bunch of modules

* [https://travis-ci.org/VisTrails/VisTrails/builds/106743348 Travis builder] for VisTrails Next
** Runs!
** Uses conda
*** Many levels of requirements
**** apt packages
**** conda packages
**** python packages in requirements.txt
**** python packages in setup.py
*** Can probably drop conda. Default builder does not have Qt5, but beta builder do!
*** But useful if we want to use conda in our own build process.
** Lots of errors I do not get locally?

* [http://goo.gl/forms/Z4HBrwaBWL User Survey]
** Have you used any alternatives to vistrails?
*** Relevant? More options?
** How often do you use any of these particular features in VisTrails?
*** Add/Remove alternatives?
** How important would you rank the following potential improvements to VisTrails?
*** Add alternatives?

=== January 27, 2016 ===
'''Updates'''
* New interpreter
** Working prototype soon
** Looping not completely done (and port combination mode: pairwise/cartesian...)
** Need to integrate with VisTrails
*** Compatibility with existing modules
*** Use log controller
*** Want to cache at multiple levels (whole stream/single element of stream)
*** Non-runtime attributes of modules (cache check, automatic conversion check, constant from/to string)

'''Items to Discuss'''
* User Survey

* ZMQ failing on windows (vistrails-users)

* [TE] [https://github.com/VisTrails/VisTrails/pull/1143 Python 3 branch]
** Testsuite almost passes
*** Failing are unicode filenames, some users guide examples, and thumbnail comparisons.
** Fixed issues
*** Signatures are now bytes (convert to string to show in widget)
*** Cannot compare different types, e.g., (None < 1)
**** PortSpec.depth and min/maxConn could be None. (Backport!)
**** cell.row could be None
*** Lots of unicode/bytes fixes to serializations
**** We have encryption implementations in the code! (keychain)
*** Lots of small fixes to package method differences
** Current issues
*** logging widget empty?
*** version tree signals messed up
*** provenance view legend icons black
*** Text do not fit in some widgets
*** VTK thumbnail comparison fails
**** VTK Cells have some faces in wrong direction?
**** Because running in VM?
** Installing on Ubuntu LTS/Latest Mint
*** Install latest matplotlib from pip
*** Install VTK 7.0.0rc2 from source
*** No QtWebEngine binary (controversial) (Must install sip/PyQt5/Qt5 from source)

=== January 20, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Backporting features from Python 3 + PyQt5 + Qt5
** Merged unicode with master ([https://github.com/VisTrails/VisTrails/tree/unicode unicode])
*** One unicode test failing
*** Problem saving to xml
** Used [http://python-future.org/ python-future] to run futurize stage 1 to update legacy (pre 2.6) code ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized unicode-futurized])
*** Updates print to functions 'from __future__ import print_function'
*** Updates exception calls to use 'as'
*** removes most usages of 'long' (mostly used unnecessarily)
**** Only needed for 32-bit support
*** Fixes relative imports (from __future__ import absolute_import)
** Fixing code that is deprecated in Qt 4.8 and removed in Qt 5 ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized-qt5 unicode-futurized-qt5])
*** Updated all signals to new-style
* If we go 2 to 3, this could break packages
** means we should schedule any package format changes for the same time
** e.g., imports should be unrelated to code path (function to load module from package identifier?) (take them out of vistrails.* [https://github.com/VisTrails/VisTrails/pull/1002 #1002])
** any structural changes (e.g. the __init__ versus init thing) (RR thinks it makes sense, though having both named "init" is unfortunate)
** putting package identifier as xml?
*** Python not so bad, plus some stuff in there is Python code (checking dependencies)
** version the APIs?
*** RR planning on versioning vistrails_module.Module, no point versioning the whole package?
* file formats on 2 to 3:
** no real translation/upgrade, but non-ascii values that work on 3 won't load in 2

=== January 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://gist.github.com/rexissimus/dfd27e466427529c385c Porting to Python 3 / PyQt5]
** Basic GUI and execution works
** Minimal work to support 2to3
** Hard to support both PyQt4 and PyQt5

=== January 6, 2016 ===
'''Updates'''
'''Items to Discuss'''
* Updating VisTrails dependencies
** Successfully built [https://gist.github.com/rexissimus/f1a1aada7de1c00a57c7 Win7-64/Python3/PyQt5/Qt5/WebEngine/VTK7]
*** VTK 7 is the first supporting Python 3 but is only in release candidate phase.
**** Next version of VTK 6 is rumored to support Python 3
**** There is a development branch of VTK 6 supporting Python 3
*** Can travis build this?
**** We can skip tests for WebEngine and VTK if needed
** Python 3 [https://python3wos.appspot.com/ showstoppers]
*** No MySQL-python (sqlalchemy supports mysql through other drivers)
*** No suds (there are active forks but we could also drop support?)
* Options for python2/3 support:
** Interpreter could be python2/python3 based on packages
** six layer works but not the easiest to maintain (e.g. in reprozip)
* Drop support for win-64
* Update copyright headers to 2016

== 2015 ==

=== December 30, 2015 ===
'''Updates'''
* Bokeh package finished
** Can output to Browser/IPython/Spreadsheet (Limited functionality in spreadsheet)
'''Items to Discuss'''
* Updating VisTrails dependencies
** Bokeh needs QWebEngine (Chromium) in Qt5 which requires PyQt5
*** Many plotting libraries only work in browsers
*** But Chromium may be a big and controversial dependency
*** Or create a browser version of the spreadsheet?
** Some users have requested Python 3
** Not backwards compatible?
** Target for VisTrails 3.0 with new interpreter?

=== December 16, 2015 ===
'''Updates'''
'''Items to Discuss'''
* Users list question
* [TE] Wrapping Bokeh
** Added bokeh property parser
*** complements numpydoc parser
*** Not all attributes are available, partially because I am using a pre-release version.
** Wrapped modules
*** bokeh.plotting finished (Backwards like matplotlib: Create plot then draw on it)
*** bokeh.charts mostly done (Missing arguments)
** QWebView mostly works (but no zooming or buttons)
*** It would be better to use external browser or QWebEngineView
** Added improvements to wrapper
*** Generalized port translations (Color/Path to native types)
*** Can use multiple docstring/property parsers simultaneously

=== December 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Looking into wrapper
** Will port TensorFlow
** Doing a pass on the wrapper code & doc
*** UX improvements
** Factorize high-level docstring parsers into core.wrapper? (sphinx, numpy, google)
** Problem with name vs module_name (fails sklearn tests because class_by_name() is broken)
** Looking into compressing specs, lazy registration of modules

=== December 2, 2015 ===
'''Updates'''
* [TE] Package wrapping
** Wrapped most of numpy/scipy using __all__
** Added class attribute and method access for classes (Can add to class or to separate inspector module)
** TODO: Document wrapping procedure

'''Items to Discuss'''

=== November 25, 2015 ===
'''Updates'''
* [RR] New interpreter is coming along
** Everything is a stream
** Task system, eventually work-stealing parallelism
** Streams no longer advance in lock-step
*** Allows for constructions like filter, join, sorted-merge
** depth>1 still to be tested, no current plan to allow this through the module interface
*** Through looping though, can do streams of streams

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapped most numpy functions (no polynomials)
** and half of scipy classes and functions
** Added functions manually from documentation (no parseable lists?)
** Focusing on data flow constructs (no property/method access for classes)
*** Using spec diff (empty for now) and dynamic parser (stores spec in .vistrails/)
** Python class/function wrapper now stable
** Add google doc parser?
*** Is there a parser available?

=== November 18, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Numpy class wrapping works
*** Basic type is List, since most types are array_likes.
*** TODO: More classes and functions
*** Some operations are in-place and some aren't, and docstring not super clear
*** [RR] It seems only methods mutate, and most have a numpy.xx function equivalent; just manually go through the methods and remove the mutating ones?
** Class wrapper is modular
*** Docstring parser and type string parser can be customized
*** Classes can have optional attribute/method ports
**** Inspectors and attribute/method modules can be created separately
** Use PythonCalc as an example
*** Can be re-implemented as a function with a parseable docstring
*** [RR] PythonCalc is just an example, and it might actually make sense to get rid of it, or do a proper math package with scalar operations (as separate modules, no combobox)
** [RR] TensorFlow to use wrapping as well
*** Very simple (only types 'tensor' & 'variable')

=== November 11, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapping numpy's classes using numpydoc (ndarray)
*** Wrapping constructor arguments, attribute getters/setters as module ports
**** Then how to access attributes afterwards?
***** Use input value port to class modules?
*** Wrap methods as modules? E.g., `ndarray.shape`.
*** Function wrapping is almost a subset of class wrapping
**** May be able to use the same parsing/execution methods
** VTK's non-getter/setter methods could be wrapped as modules
*** We could then remove extra logic in interpreter for keeping function order
** Bokeh uses autogenerated docstrings
*** We may be able to read the specification directly

* [RR] [https://github.com/VisTrails/VisTrails/pull/1138 TensorFlow package]
** Basic setup working, can execute the Mandelbrot example
** Will autogenerate the operations

=== November 4, 2015 ===
'''Updates'''
* [RR] Interpreter work requires a fix for [https://github.com/VisTrails/VisTrails/issues/1137 DB issue #1137]
* [DK] Kitware's Resonant [http://www.kitware.com/source/home/post/173]
** [https://github.com/girder/girder Girder]: data management system
** [https://github.com/Kitware/romanesco Romanesco]: execution engine, uses [http://www.celeryproject.org/ Celery] for task management
** Resonant Flow: web app for editing and executing workflows

'''Items to Discuss'''
* [TE] Added OSX Lion (10.7) VM on build machine using vagrant (seems ok with license?)
** New builds works on Lion
** Change the minimum requirement to 10.7?
* [TE] Package wrapping
* Added upgrade suggestions using 2 spec versions ([http://pastebin.com/30XUU8Gp example])
** using name edit distance to find matches
** Could use something better like port similarity for modules, and type similarity for ports
** Should write python upgrade code?
** Added spec to sklearn package
*** Can now diff spec versions and keep the spec static
*** There will be problems with downgrades and package versions

=== October 29, 2015 ===
'''Updates'''
* [TE] nightly-build-mac fixed (Needed to approve xcode license)

'''Items to Discuss'''
* [TE] matplotlib wrapper
** ported to general spec
** Diff can be used on general spec
*** Only needed minor changes
*** Fixed indexing bug that corrupted specs
*** Can now move diff tools to core/wrapper
** Add new plots?
*** New plots in mpl 1.3: eventplot
*** New plots in mpl 1.4: angle_spectrum, magnitude_spectrum, phase_spectrum', violinplot
*** No new plots in mpl 1.5 (from looking at boilerplate.py)

=== October 21, 2015 ===
'''Updates'''
* [RR] Alexis has arrived, will be working with [RR] on a more efficient interpreter

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package]
** Supporting multiple package versions
*** Check which version can be loaded [https://github.com/VisTrails/VisTrails/pull/1135 #1135]
*** We cannot show version requirements in the list of packages because old packages are loaded when importing the codepath
** Visual diff does not work well, but we can use the spec differ to see differences.
** Unifying vtk and matplotlib wrapping specs (WIP)
*** And porting matplotlibs spec differ to work on the general spec
*** Spec differ can then be used on vtk and other packages in the future
*** Will enable automatic upgrade generation
* [RR] Rework interpreter
** restore abstraction between interpreter/module code
** build looping, streaming, caching into the interpreter
** rework cache
** look into parallelism once basic functionality is there

=== October 14, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package] (adding numpydoc parser)

=== October 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/tree/fix-matplotlib-parser New matplotlib parser] (adding numpydoc parser)
** Added numpydoc attribute parser for plots.
*** TODO: Need better port spec reconciliation with call signature parser.
*** We can create a general numpydoc parser, but attribute types are unique to matplotlib.
** Needs package versioning
*** New spec will not support matplotlib < v1.4 due to changed path to axes classes.
*** Load spec version corresponding to installed matplotlib version?
*** Need version downgrades?

=== September 30, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Updating Matplotlib parser
** Matplotlib docstring parser fails on numpy docstrings
** I have [https://github.com/VisTrails/VisTrails/commit/eae8b0c16260810587e47c41cab53552cbb3cf0a added basic numpydoc parsing]
*** Only used by a few docstrings so far
*** Parsing uses many sources (class tables, signatures, ACCEPTS, method docstrings, definition parsing).
** Caswell said they were thinking about moving to traitlets, but this is not ready yet

=== September 23, 2015 ===
'''Updates'''
* [TE] VisTrails 2.2.3 released
** Also have pushed to PyPI, binstar, etc.
** Sourceforge vs. GitHub
*** should be able to host releases on GitHub
*** nightly binaries pushed to sf each night
*** old binaries?
* [TE] Re-wrapping MatPlotlib
** Keep static generation - Docstrings are brittle beween matplotlib versions
** Keep generating the executable classes - but create functions, not vistrails Modules
*** Why is there so much patching?
** Re-implemented Alternate PortSpec for InputPortSpec
*** It will now inherit specs from parent (No need to reimplement)
** Module upgrades?

'''Items to Discuss'''

=== September 16, 2015 ===
'''Updates'''
* [TE] Job Monitor tests and documentation done
** OK to leave document package in packages directory?

'''Items to Discuss'''
* [TE] Library wrapping: How to do code patching? [https://docs.google.com/drawings/d/1Sh3eOXot6v2y880jHKQrqXqAwr-0aoqYligg3z8G8MY/edit?usp=sharing Wrapping diagram]
** Insert code into module template (Old VTK code)
** Patch the library that is called (New VTK code)
** Somehow store code in spec and apply when executed?
*** Executed code needs at a minimum access to inputs, outputs, current class
*** Use standard input/output dict and obj reference that the code operates on?
*** Can this be done while keeping the execution abstract?

* Do new release now?

=== September 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* New release?
** [RR] wants reprounzip
** tej changes & doc
** job monitor & jobmixin fixes
** mongodb
** reprounzip
** warning: MplFigure type is int
** tabledata: add Reshape, DictoToTable & ListToTable, fix ListToTable with numpy arrays
** PythonSource can have same name for an input & output
** don't show spreadsheet at exit

=== September 2, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Limit autosaves? [https://github.com/VisTrails/VisTrails/pull/1126 #1126]

=== August 26, 2015 ===
'''Updates'''
* [TE] Added Job support to Parameter Explorations (Requested by Colin), and Mashups
** specify job ids, need to specify different ids for parameter explorations since they have the same version id
** how to deal with parameters passed in on command line
* [General] provenance: should be creating a new version when we execute workflow with changed parameters?
** currently, custom_params annotation stores this in provenance currently
** [RR] API doesn't record provenance if passing in parameters: http://git.io/vsAA5
'''Items to Discuss'''

=== August 19, 2015 ===
'''Updates'''
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [TE] Working on Job Monitor documentation

'''Items to Discuss'''
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [TE] Stop testing VisTrails 2.0?

=== August 12, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Build broken on Travis; because of IPython 4 released today? ([https://travis-ci.org/VisTrails/VisTrails/builds/75279795 build 992]; [https://github.com/VisTrails/VisTrails/issues/1123 #1123])

=== August 5, 2015 ===
'''Updates'''
* [TE] Fixes to Jobs
** Could not delete jobs
** Could not run job in group
** Job not reset when calling ModuleSuspended
** Added deleting job from context menu
* [RR] Writing documentation for everything [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

'''Items to Discuss'''

=== July 29, 2015 ===
'''Updates'''
* RR still looking into new interpreter thing
** Goal is to take out scheduling logic from Module so it can be split in multiple processes, and so that smarter strategies can be added in time
** This means some work on packages
** Spreadsheet can live in kernel process? Still some UI stuff that will take work (changing configuration, persistent archive's viewer, ...)
* [TE] Problems running examples [https://github.com/VisTrails/VisTrails/pull/1111 #1111]
** Testing of more examples requires additional packages on the test machines.
** Fixed faulty line-ending in PythonSource:s failing on Python 2.6.
** Test suite now testing SUDSWebServices (If web service is down, test suite will fail)
** preferences.py test failed reloading 'dialogs' package, switched to using 'URL'.

'''Items to Discuss'''

=== July 22, 2015 ===
'''Updates'''
* [TE] mailing lists back online
* [TE] Working on [https://github.com/VisTrails/VisTrails/issues/1107 #1107]
* [RR] Working on ReproZip package

'''Items to Discuss'''
* [RR] MongoDB package [https://github.com/VisTrails/VisTrails/pull/1106 #1106]
* [RR] Example for tej docs? [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

=== July 15, 2015 ===
'''Updates'''
* 2.2.2 released

'''Items to Discuss'''
* RR is considering executing everything in an IPython kernel (i.e. separate Python interpreter, like the one spawned for a notebook)
** It's a separate process that we can restart without restarting the app/gui
** We can isolate the execution environment (e.g. for the server)
** We can run the whole thing remotely (if your data is elsewhere, just run VisTrails locally and the pipeline elsewhere)
** Pipeline execution no longer makes the interface hang, it just makes the kernel hang (but that's fine)
** We can use notebooks as modules (probably way nicer than the PythonSource module)
** We can run multiple kernels so long as the ports carry things that are serializable
*** meaning we can put the multithreaded-interpreter without all the hacky parts it has now
*** we can run IPython kernels in all the languages IPython supports, [https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages currently 46]

=== July 8, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Buildbot github hook not working after IP address change
* [TE] No reference to VistrailsApplication ([https://github.com/VisTrails/VisTrails/issues/1103 #1103])
** [RR] Added PR [https://github.com/VisTrails/VisTrails/pull/1104 #1104]
* [TE] Reopening VT file after saving with bundled subworkflow won't offer subworkflow upgrade ([https://github.com/VisTrails/VisTrails/issues/1102 #1102])
** allow manual delete to fix right now
** fix this on top of the use-uuid branch
* [TE] Release VisTrails 2.2.1? ([https://github.com/VisTrails/VisTrails/blob/v2.2/CHANGELOG CHANGELOG])
** [https://github.com/VisTrails/VisTrails/pull/1093 output-modules-use-global-dir]
** [https://github.com/VisTrails/VisTrails/milestones/version%202.2 Current issues for 2.2]

=== July 1, 2015 ===
'''Updates'''
* [TE] PROV fixed
* [TE] Working on subworkflow issues
* [RR] Considering reworking the controller (log vs exception problem, retained upgrades causing interferences) and also the interpreter (IPython?)

'''Items to Discuss'''

=== June 24, 2015 ===
'''Updates'''

'''Items to Discuss'''
* UV-CDAT
* [TE] Can a cyclic workflow be valid? ([https://github.com/VisTrails/VisTrails/issues/1097 #1097])
** focus on disabling the ability to create cyclic pipelines because more things break than just this with a cyclic pipeline
* [RR] Relative paths ([https://github.com/VisTrails/VisTrails/pull/1057 #1057])
** This interacts with the new bundle; how do handle packing files inside the VT bundle?

=== June 17, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] current_version and reusing existing upgrades are broken ([https://github.com/VisTrails/VisTrails/issues/1095 ticket #1095])
** Could be that export to PROV is using an unflushed upgrade pipeline?
** current_version would then be correct.
** It may work to flush the actions before exporting?

=== June 10, 2015 ===
'''Updates'''
* DAT: fixed VTK issue on Linux and Mac
* Still crashes on Windows. Need help! Reminder: this works in the VisTrails spreadsheet (QCellPresenter), although no widget get changed there during a drag
** Is it a VTK bug?
** Is it simply impossible to change widgets during the drag, should we do it a different way?
** Did I miss something that is done in VisTrails but somehow not in DAT?
** Low prio, UV-CDAT doesn't run on Windows anyway

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 Updated pull request])
* Single instance code and batch mode

=== June 3, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 pr])
** Requires fixes to command line parameters, Output modules, and batch mode
** How to test this
** Updated missing/outdated flags
** Fixed view issues when generating graphs
* [TE] batch mode
** SpreadsheetOutput not enabled in batch mode. Should we check is_running_gui instead?
** Other instance setting flags from caller
** Is graphsAsPdf replacing spreadsheetDumpPdf?
** graphsAsPdf true by Default?
** Batch mode executing by default (Not needed when generating graphs)
** Re-added workflowInfo as withWorkflowInfo for writing graph and xml workflow
** [DK] batch mode should be outputting to files or stdout, shouldn't always trigger SpreadsheetMode
** execute flag, maybe make execution the default and allow a "--no-execute" if you only want to capture graphs, for example

=== May 27, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] API question
** http://lists.vistrails.org/pipermail/vistrails-users/2015-May/000357.html
* Status of DAT
** Can add VCS plot to DAT but need to work on configuration windows
** Documentation for graphics templates for UV-CDAT/vcs?
* Qt support?

=== May 20, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Reviving the DAT, integrating scripting & porting UV-CDAT!
** On [https://github.com/VisTrails/DAT GitHub] ([https://github.com/VisTrails/DAT/issues issues])
** Merging 2 years of development taking longer than expected, but getting there. The plan is to get the patches in VisTrails and never fork again, we never want to get in UV-CDAT's situation (and don't need to).
** VTK cell works fine on Linux but there was flickering on Mac & Windows before; still issues on Mac (Windows status unknown)
** Can get a VCS plot soon (but will need VTK cell fix)
** Integrate in UV-CDAT's build system (so we have cdms, VCS, ...) -> RR can do this, low priority
** How do we integrate scripting?
*** We want to be able to seamlessly make changes to a plot by changing Python code
*** Define new plots by entering Python code without writing modules/packages?
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 13, 2015 ===
'''Updates'''
* [RR] Test skipping whitelist ([https://github.com/VisTrails/VisTrails/pull/1069 #1069]) -- low priority
* [RR] Custom matplotlib modules can't be compatible with both 2.1 and 2.2 ([https://github.com/VisTrails/VisTrails/issues/1067 #1067]); should be fixed for ALPS ([https://github.com/VisTrails/VisTrails/issues/1070 #1070])

'''Items to Discuss'''
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 7, 2015 ===
'''Updates'''
* [RR] Export/import workflow to Python working!

'''Items to Discuss'''
* [Claudio] UV-CDAT
** The UV-CDAT project is the biggest user base of VisTrails
** VisTrails package management provides a lot of friction towards people plugging in their code
** Need to make it easy to integrate your random Python scripts in the system without having to deal with all the boilerplate, at least in the first step
** [RR] argues that modules are still good; UV-CDAT shouldn't move towards a purely script-based backend
** [RR] export/import with Python could reduce a lot of that friction by allowing 1) to edit workflow as Python 2) to open up boxes automatically if needed code doesn't match actual modules
** ...

=== April 29, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] <strike>Abstractions</strike> subworkflows status ([https://github.com/VisTrails/VisTrails/labels/subworkflows tickets])
* [RR] matplotlib compatibility (2.1 & 2.2), [https://github.com/VisTrails/VisTrails/issues/1067 #1067]
** RR to try and fix ALPS matplotlib modules

=== April 22, 2015 ===
'''Updates'''
* 2.2.0 has been released!
* Windows issue (via email from Ryan)
** issue with manifest file (may be a new file in VTK6?)
** Tommy has regenerated new Windows builds
* Binaries, pypi, and conda released
* [RR] Export as script
* Python sources using VTK need to switch to SetInputData (users should be aware of this)

=== April 15, 2015 ===
'''Updates'''
* Ready for 2.2.0 (apart from binary/deps issues)
** Missing some libs (scikit-learn, tej, tdparser, SQLAlchemy+connectors
** Windows: runvistrails.py is no longer used, so the PATH is wrong
** Windows: pip is broken, but it probably wouldn't work anyway because of permission issues (disable this?)
* Queries, upgrades and getPipeline() usage ([https://github.com/VisTrails/VisTrails/issues/1054 #1054])
** Getting a pipeline with getPipeline() is not safe: it might return an invalid pipeline
** This is used in many places throughout the code, like queries
** Upgrading would require going through the controller, but that creates new actions
* [TC] Avoid copying a module's output if it's used as input by exactly one downstream module ([https://github.com/VisTrails/VisTrails/issues/1060 #1060]) (useful for big numpy arrays you can update in-place)

=== April 8, 2015 ===
'''Updates'''
* [DK] Merged RR's changes for output modules (1012 and 1013)
** RR will merge remaining changes, then create v2.2 branch!

'''Items to Discuss'''
* BNL need numpy array to VTK image
** Looks like VTK has some helpers for this
** We will help if issues arise
** Will contribute back to VisTrails package
* Upgrade issue: [https://github.com/VisTrails/VisTrails/issues/1017 #1017]
** Automatic upgrades should happen between versions of provided upgrades
** Our existing upgrades work around this so it doesn't need to be 2.2.0
* Corner-case VTK modules
** No longer need VTKCell input port, so don't interfere with registry and API anymore
** Still work weirdly, people probably shouldn't use them
** But we have lots of clunky modules since we wrap the whole of VTK; some people might rely on this and know how to use them, let's keep them anyway
** Ready for 2.2.0

=== April 1, 2015 ===
'''Updates'''
* [RR] UV-CDAT: bugfixing for 2.2, long-term plans: implement scripting import/export in VisTrails, port to UV-CDAT
* Possibly, try to move to regular VisTrails to use new features

'''Items to Discuss'''
* 2.2 release: nothing much is pending anymore, release next week?
** [TE] vtkExporter classes [https://github.com/VisTrails/VisTrails/issues/1032 #1032]
** [RR] Hiding upgrades in version tree might make it (or might be 2.2.1 so we can test it out) [https://github.com/VisTrails/VisTrails/issues/949 #949]
** Output modules changes to go in
* add note to documentation about order of parameters in VTK
* add issue about exporter upgrades if not already there

=== March 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* 2.2 release
** Checklist on Github: https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist
** Review output modules
** RR has a couple more issues to fix
** Ready to go -- sign app package for OSX? [https://github.com/VisTrails/VisTrails/issues/984 #984] We need access to the Apple Membership team

=== March 18, 2015 ===
'''Updates'''
* [TE] VTK6 works

'''Items to Discuss'''
* [RR] Release v2.1.5 with backported tabledata?
** MTA example needs updated tabledata (for JoinTables)
** Google Maps package still not available
* [RR] Work torward v2.2.0?
** changes:
*** new persistence
*** API changes
*** output module changes (upgrades?), maintain cells but try to upgrade
*** not wrapping stuff
*** VTK6? yes
*** JobSubmission stuff?
*** relabeling for upgrades [https://github.com/VisTrails/VisTrails/issues/949 #949]
** makes sense, needs the tree view code to be updated, check selection
** See [https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist 2.2 checklist]
* Discussion of [https://github.com/VisTrails/VisTrails/issues/1016 #1016]
** plumbing between outputs and output modes, how to define a mode that works for many outputs without writing for each output?

=== March 11, 2015 ===
'''Updates'''
* [RR] persistent_archive done; merge? ([https://github.com/VisTrails/VisTrails/pull/755 #755])
** note about the focus events for widgets
** TE be aware of file_archive for future binaries that include persistent_archive
* [TE] [https://github.com/VisTrails/VisTrails/pull/998 New VTK package] finished

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails? (see last week; decision needed)
** RR email to JF about this
** yes; email sent to Github
* [RR] Switching order of output ports ([https://github.com/VisTrails/VisTrails/pull/1006 #1006])
** added port specs are sorted at a separate spot (Module.*_port_specs properties) than those in the registry (which are sorted in the registry), but those two lists are just combined without respect to sort keys
** need to determine whether the two lists should be merged or remain distinct
** should make sure that order of input ports and output ports makes parallel connections for things with same order
** DK suggests breaking backward compatibility here: workflows still run, can fix easily if a problem in an existing package.
* [RR] Question about output modes ([https://github.com/VisTrails/VisTrails/pull/1007 #1007]), how to integrate in API ([https://github.com/VisTrails/VisTrails/pull/24 #24])
** Should ImageFileMode be removed? ("image" is not a mode, "file" is)
** ImageOutput missing?
** Feel free to change how formats works
* [TE] Test suite segfaults on Fedora 17 virtualbox. Install newer version? (Support ended in 2013)

=== March 4, 2015 ===
'''Updates'''
* [TE] VTK wrapper
** Works on VTK 5.10
** Still need to test VTK 6
** New general wrappers for python functions and classes

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails?
** When [http://i.imgur.com/UTY2qfg.png filing a pull request] from UV-CDAT/VisTrails, VisTrails/VisTrails is selected by default
** People keep forgetting to change the default ([https://github.com/VisTrails/VisTrails/pull/956 #956] [https://github.com/VisTrails/VisTrails/pull/968 #968] [https://github.com/VisTrails/VisTrails/pull/999 #999] [https://github.com/VisTrails/VisTrails/pull/1000 #1000] [https://github.com/VisTrails/VisTrails/pull/1003 #1003] [https://github.com/VisTrails/VisTrails/pull/1004 #1004] [https://github.com/VisTrails/VisTrails/pull/1005 #1005])
** Only way to change that is to not have it marked as a fork of VisTrails/VisTrails
** Github staff [https://gist.github.com/remram44/b364c24ef1e462ce6e2f can make that change for us]; should we do it?
** Juliana: comments on this? visibility vs. convenience/annoyance for developers
* [RR] What about [https://github.com/VisTrails/VisTrails/issues/991 #991]?

=== February 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] vtkviewcell for infovis support, can we unify with VTKCell?
** need to test this
* [TE] vtk wrapping
** Mostly finished
** VTK 5.10 produce incorrect results with old wrapping
*** Old wrapper is based mostly on VTK 4
*** Most vtk_examples affected
*** [http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Replacement_of_SetInput]
*** should be able to upgrade from SetInput to SetInputData (need to drop GetOutput and replace with self ports)
*** can we change vtkInstance to just return self and not wrap things
** terminator example not working under 5.8?
* How does VTK wrapping fit into general wrapping framework?
* [RR] new persistence package

=== February 18, 2015 ===
'''Updates'''
* [RR] New VisTrails API and IPython integration ([https://github.com/VisTrails/VisTrails/pull/24 #24])

'''Items to Discuss'''
* [TE] VTK wrapping
** [https://gist.github.com/rexissimus/16b74693545b5e7c1035 Benchmarking vtk package]
*** Old: 24.7 seconds
*** New: 10.5 seconds (Except first time that adds 8 sec)
**** The parsing that calls is_abstract (that tries to instanciate all vtk classes) is now only run the first time.
**** get_items_from_sigstring takes 2 seconds, maybe we can use a lookup dict for already computed sigstrings?
** Now using a general python function wrapper
*** VTK classes are wrapped into python function that does not depend on vistrails
*** VTK functions can be executed without vistrails
*** The spec maps functions into vistrails modules, but can also describe wrapping
*** A general python function wrapper that supports
**** kwarg inputs
**** single, list, dict outputs
**** callback for progress reporting
**** temporary file generator for using FilePool
**** optional output generation
*** Creating specs:
***** Create spec by hand
***** Auto-create spec outline (TODO) and manually finish it
***** Dynamically create spec (VTK)
***** Implement documentation wrappers (Can use scikitlearn wrapper to wrap numpydoc) (TODO)
***** Classes as bad functions needs to be wrapped in new functions before they are wrapped. This is different for each package.
****** Classes is hard: Like VTK, and matplotlib. Scikit-learn does still not wrap classes
***** Spec diffing and patching could be done using code from matplotlib.
** Still needs upgrades from old VTK package
*** Is it possible to dynamically wrap functions, e.g, you see a SetFunc and just remove the 'Set' prefix. Or do you need to create a complete mapping?

=== February 11, 2015 ===
'''Updates'''
* Update from Friday's meeting
** discussed VisTrails internals
** discussed wrapping
*** xml discussion, hard to modify because tied to db code
*** TE has made it possible to add the schema-defined attributes to the intermediate representation
*** higher-level operations on the port specs
** make sure the simple case works
*** [JF] take a simple package with documentation and figure out what the base case for wrapping is

'''Items to Discuss'''
* [TE] VTK wrapping
** Dynamic loading works
** Reading XML is fast enough, but [https://gist.github.com/rexissimus/8272d3c776ccfa115d82 unserializing data is slow]
** Working on patterns for patching
** Matplotlib has many advanced patterns like argument ordering, nested arguments, alternateSpecs, output types.
*** Having all this in a general wrapper might confuse users?
** [RR] Delay module (except for identifiers) until you need it---e.g. don't deal with port specs, etc. until necessary
* Scripting Support [https://github.com/VisTrails/VisTrails/pull/950 #950]
** [RR] Issue with getting code from modules
** Design a simple solution
** [JF] Couldn't you use modules as black boxes without conversion, just to call into modules/subworkflows easily from e.g. IPython?
*** [RR] This is a job for the API, and a very separate use case. See [https://github.com/VisTrails/VisTrails/pull/24 #24]

=== February 4, 2015 ===
'''Updates'''

'''Items to Discuss'''
* Wrapping
** Format to use? Currently XML (like current matplotlib)
*** JSON and YAML have simple "to python dictionary" methods
*** But don't stream
*** YAML a lot easier for humans
** [DK] vtk-new-package also changes parameter names, creates enumerations
*** intermediate schema needs to be extensible
*** packages will want to store there specific infos for compute() method generation
*** also might have specs-altering info, like matplotlib's alternateSpec
** representation to code , registry already has schema for some aspects
** [RR] We might want to see if Module subclasses can be created lazily
*** no need to create all the classes just to register them in the registry and never actually use most of them
*** future effort
* [RR] Where should VisTrails packages live?
** tej installs as 'vistrailspkg.tej', TE installed it as 'userpackages.tej'
** Currently, standard packages are 'vistrails.packages.', user packages are 'userpackages.' and packages loaded through pkg_resources might be anything
** [RR] Use 'vistrailspkg.' everywhere?
** Long-term effort to simplify package distribution/installation (and have VisTrails get them automatically?)

=== January 28, 2015 ===
'''Updates'''
* T. Caswell to come visit on Fri 6 to discuss wrapping work

'''Items to Discuss'''
* [TE] New VTK wrapping
** Current code by DK seems a good deal faster
** Generates XML that can be patched/tweaked, generates Python code from it, VisTrails only loads generated Python code
** RR would rather have VisTrails load intermediate representation (= XML) directly, wants to make sure this is not slower
** The goal is to turn the intermediate step into something generic that would be used for every wrapped package (vtk, numpy, matplotlib, sklearn, java) instead of each having its own
** TC has its own code at [https://github.com/Nikea/VTTools/blob/master/vttools/wrap_lib.py github:VTTools] which parses numpy docstrings and generates modules, doesn't yet handle classes or persist anything
* Web crawler
** Right now, TE starts jobs for "start crawler", "stop crawler", "install classifier"
** RR would rather have the crawling be a job as far as VisTrails and tej are concerned
** The whole thing would be one pipeline: load examples, train classifier, start crawler [check for job, kill previous one, upload model, start processes], get snapshot, visualize
*** Need some support in tej and job submission system: long-running jobs, stop a job (wait for it to finish?), restart a job even though results are cached

=== January 21, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Unified wrapping method discussion [https://github.com/VisTrails/VisTrails/issues/991 #991]
** TE to work on reusable method with intermediate representation, starting with VTK
* [RR] Examples for scikit-learn: JF has an old example using Weka with parameter exploration (not currently in source tree)
** AM's examples are enough
* [AM] scikit-learn package is done, merge it in? [https://github.com/VisTrails/VisTrails/pull/955#issuecomment-70286788 #955]
** RR will merge
* [RR] What should copyright headers say? [https://github.com/VisTrails/VisTrails/pull/994#issuecomment-70173935 #994]
** Let's keep everything in there: Utah/Poly/NYU

=== January 14, 2015 ===
'''Updates'''
* [TE] Working on classifier
* [RR] Scripting integration, work in progress

'''Items to Discuss'''
* [RR] Unified wrapping method discussion ([https://github.com/VisTrails/VisTrails/issues/991 #991])
** Let's talk next week, [AM] and [DK] are not here

=== January 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* make sure that we address critical issues, questions, and pending review branches in a timely manner
* scripting support
** [RR] no issues if we want to just keep annotations in the generated code to allow the link back to a workflow
** [RR] can translate from workflow to script, working on script to workflow
** will work for parameter value changes, structural changes require changes to the annotations
** need to publish best practices here
** would be cool to do looping in scripts (easier interface than with workflows)
* notebook support (convert form notebook to workflow)
** RR will sync with FC on this
* Issue with console in built-from-scratch
** [TC] iPython rearranged some of the completion stuff in 2.2 and 2.3
** binary has old version of iPython -> 1.0.0, should we update?
* [TC] automated wrapping of numpy and scipy
** discovered a bunch of malformed documentation in numpy and scipy
** has github repo for vistrails tools
** example modules wrap a bunch of R stuff (not baked in, just how things are)
** will be pushing wrapping logic up
** port names forbidden (window and domain)
** have an import hook to get from yaml directly to VisTrails Modules
** should work for any python modules with well-formed numpy docstrings.
* [Action] should make it clear in documentation that Constant now means serializable not that the value doesn't change (e.g. List)
* [TC] might be interesting to try to build components of matplotlib and accumulate in figure (long-term project, but thinking about how this might work)
* [TE] build and build scripts
** completely automatic, buildbot
** need to set the build machines for the environment we want for the binary
** would virtualenv work here?
** [TC] anaconda can pin versions, potential path to test different configurations
** Q: upload nightly binary builds? A: makes sense, make sure they are well-labeled
* sourceforge stats: e.g. http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07
* package issues (see Remi's message)
* [TE] Scope of tej
** Support single ssh commands?
** Queue can be used as a remote machine (crawler is using queue.call*)
* SourceForge stats: http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07

== Older meetings ==
* [[Development/2014]]
* [[Development/2013]]
* [[Development/2012]]
* [[Development/2011]]
* [[Development/2010]]

Development

2016-07-27T14:44:10Z

Tommy: /* 2016 */

<div class="nonumtoc toclimit-1">
__TOC__
</div>

See also the [https://github.com/VisTrails/VisTrails/wiki/Development Github wiki]

== 2016 ==

=== July 27, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Finished using patch in script [https://github.com/VisTrails/VisTrails/tree/python-wrapper-script-patches python-wrapper-script-patches]
** [https://gist.github.com/rexissimus/f0d6b026aa5a2a770847f3321744645d new pathching example] vs [https://gist.github.com/rexissimus/b28d83ae516a519167f5751bb8ab3739 old patching example]
** [https://github.com/VisTrails/VisTrails/blob/python-wrapper-script-patches/vistrails/packages/vtk/vtk_wrapper/parse.py#L135-L273 Example of new patches]
** Legacy '.vtkInstance' is now added as a patch "self.vtkInstance=self" (see new patching example)
** [https://github.com/VisTrails/VisTrails/blob/python-wrapper-script-patches/vistrails/core/scripting/api.py New api for executing standalone modules]
*** Accessing module was disabled for core/api, but a different api for this is probably better anyway.
*** api.Package now gives [https://gist.github.com/rexissimus/f0d6b026aa5a2a770847f3321744645d#file-new_patching-py-L26 directly callable module compute functions]
*** Only works on modules not using interpreter functionality ('.interpreter', etc.)
** Fixed more renaming issues - [https://github.com/VisTrails/VisTrails/blob/python-wrapper-script-patches/vistrails/core/scripting/scripts.py#L63-L64 function argument names should not be replaced]
** Still need to do something nicer for the patch formatting
*** patch keys currently contain non-python-variable characters but this can be fixed
*** Need to replace string template with python variables that is replacable using RedBaron
**** Patches could then look like:

def vtkInstance():
self.vtkInstance = self

=== July 20, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] New patch method for python-wrapper [https://gist.github.com/rexissimus/009b303e4cadcd4b8f2fec6cf848cb2b example]
** A patch is a string template with self/input/output variables for patching a class method
** Patches are stored in xml specification
** Patches are assigned to methods in ClassSpec's
** Used both for execution in vistrails and when exporting as script
*** Executed with "exec" when run in vistrails
*** Turns patches into natural calls in script
** Wrapping VTK library no longer needed
*** Removes ".vtkInstance" (Automatically removed from PythonSources and vtkInteractionHandlers)
** Removed fix_classes.py (Subclassing of VTK classes to patch methods directly)
** Also used for port translations (With patch names like "basic:Color#input") (No more ugly input_t method definitions)
** TODO's
*** Add to export_as_script
*** Patch Modules that represent Python functions as well

* [vistrails-users] Read data from SQL example?

=== July 13, 2016 ===

'''Updates'''

* [DK] bundles on sql-alchemy branch
** Bundle, BundleMapping, and BundleSerializer
** New BaseSerializers to deal with versions of directory, zip, db serializers
** Can register the BundleSerializers with the base serializers
** Translation between bundle versions
** Bundle.add_object "just works" if an appropriate mapping was registered

'''Items to Discuss'''
* [TE] Simplified running module using API for scripting [https://gist.github.com/rexissimus/b28d83ae516a519167f5751bb8ab3739 example]
** API Module can be executed using '''compute''' method
*** Takes list of outputs to compute + inputs as keyword arguments
* Status of general cell synchronization (vistrails-users)

=== July 6, 2016 ===

'''Updates'''

* [DK] Working on bundles

'''Items to Discuss'''
* [TE] Using vistrails API in scripting [https://gist.github.com/rexissimus/034d9c4dedc3299a079e84981dedd8c7 example 1 (API with VTK)] [https://gist.github.com/rexissimus/a4a9ca6c08d4058c64967d2b35415fd5 example 2 (DownloadFile only)]
** Call module in script using vistrails API
** Can be used when no export method is defined.
* [TE] [https://github.com/VisTrails/VisTrails/commit/c76c109349769fee1280f85c22678380a2f9cd39 Server news bug] Critical?
**[RR] No, unreleased
* [DK] New bundle organization
** BundleMapping contains individual mappings from raw objects to BundleObj
** Must be separate in order to have in-memory, separate from serializer settings

=== June 29, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Export VTK as python script
** Works on Terminator (Isosurface, Volume Rendering, clipping plane, combined rendering) [https://gist.github.com/rexissimus/16caf5200802e150296f62a0c7844c5a example]
** Preludes (imports) still need improvements
** Works with vtkInteractionHandler (clipping plane)
** Resulting clipping plane is incorrect? (supposed to hide one side of the plane)
** vtkRendererOutput Uses VTKRenderWindow as output
*** Should support different output modes?
*** Does not work with multiple outputs (Next cell is displayed when current is closed)
*** Uses wrapped vtkInstance (as vvtk)
**** Create new patch system with code that can be used both in vistrails and in a python script?

=== June 22, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Fix for upgraded analogies (PR [https://github.com/VisTrails/VisTrails/pull/1177 #1177])
** Uses module location to find module remap (The best we can do right now?)
** Also fixes remapped port names for connections to existing modules
** May still fail on complex upgrades like adding a function on an upgraded module that has a different port name

* [TE] Working on exporting wrapped libraries (VTK)

=== June 15, 2016 ===

'''Updates'''
* [TE] Added depth logic to python script exporter ([https://github.com/VisTrails/VisTrails/commit/50f220e4f6abe5a7bb8689f73f456f43df2dbc12 full commit])
** Fully implements connection merging and list looping

'''Items to Discuss'''

* [TE] Making analogy work on upgraded workflows ([https://github.com/VisTrails/VisTrails/issues/1175 #1175])
** Analogy only works We need to use the non-upgraded action chain
** But pipelines need to be valid (matcher uses module portspecs)
** Tried to get upgrade remap from upgrade action, but this seems impossible
** Use module location instead?
*** Location should be identical for one-to-one module upgrades

=== June 1, 2016 ===

'''Updates'''
* VisTrails 2.2.4 announced (finally)
** 5 survey replies
** 47 downloads last week

'''Items to Discuss'''
* [TE] Export VTK as script (python-wrapper)
** to_python_script
*** needs the pipeline (or at least the connections)
**** Should not generate code for any possible VTK method (exporter detects which ports is used in the source)
**** VTK needs to know connection order
**** Adding functions directly to the script results in nicer code
** Add support for multiple input connections
** Add support for list looping

=== May 25, 2016 ===

'''Updates'''
* Mailing-list fixed
* Getting stats from the "server news" mechanism (via [https://github.com/remram44/apache-log-info parser])

'''Items to Discuss'''
* [RR] Alexis doing writeup on VisTrails, curious about interesting streaming use-cases (and potential future users)
* [TE] Union ports
** Show union ports in pipeline (DEMO)

=== May 18, 2016 ===

'''Items to Discuss'''
* [TE] mailing list still down - Julio working on it
* [TE] Improved union port
** New schema 1.0.5 adds portitem.union string attribute
** Works with pipeline view, parameter exploration view, and mashup view
** Should work well for matplotlib
** Use with VTK ports?
*** It uses [item_1,item_2] style ports usually with different tuple length.
* [TE] Remove emacs dependency from db generate [https://github.com/VisTrails/VisTrails/issues/1173 #1173]

=== May 11, 2016 ===

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]
** GUI-based solution [https://github.com/VisTrails/VisTrails/tree/union-port Branch union-port] Demo?
*** Shows single port for all ports with same sort_key
*** Select specific type when adding/showing
*** Only one type should be visible on the module at any time
*** Making tuple parameters union types is probably too complicated
*** Should work with alternate specs like matplotlib (if sort_key is defined correctly)

* [TE] Feature suggestion: Let connections connect to functions/parameters
** Show functions and parameters as ports and toggle port visibility directly for functions and parameters
** Use separate views for ports and functions (like before)
*** Allow rearranging of functions
** Pros:
*** Supports ordered connections. Create 2 functions, make them visible as ports, make connections to them.
**** We can also have, e.g., a line joining the ports on the module to indicate they are part of a list.
**** Makes List module simpler
*** Connect to parameter in tuple
*** Functions that are visible on the module can connect to an actual function, and not just to the first one it finds.
*** Can replace operation modules (in python-wrapper) in some cases for, e.g., numpy.
** Cons:
*** Interface more complicated and crowded
*** More difficult for users to grasp?
*** No immediate use case
*** Makes no union type for tuple parameters a bigger problem.

* [TE] Publish user survey?
** No response from vistrails release yet
** Not announced on vistrails-users yet.

=== May 4, 2016 ===
'''Updates'''
* VisTrails 2.2.4 released

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]

=== April 27, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Wrapping Bokeh
** New method type "operation"
*** Transforms Figure->Glyph->Output into Glyph->Figure->Output
**** Glyph sets function name and arguments as output
***** Not serializable, but should always be computed together with the subject of the operation.
**** Figure applies Glyph operation on itself
*** Useful for matplotlib?
**** matplotlib currently find actors by searching upstream?
**** But this is more difficult since matplotlib is not function-based.
** New "union" port type
*** Turns "x(float), x(list)" into "x (float, list)" and uses first set value
**** Uses only first value in tuple
**** Bokeh have many properties that support (list, string, Float)
*** Does not work with depth=1 types (e.g. Float of depth 1)
**** Turn Depth 1 types with known type into lists?

* [TE] New bugfix release
** Finalize survey

=== April 20, 2016 ===
'''Updates'''
* Merged upgrade fixes
** Now has infinite loop test
** loop test now correctly loops 5 times
*** remap_module used wrong (current) package version when creating ModuleDescriptor
* Fixed multi-step group upgrades (PR: [https://github.com/VisTrails/VisTrails/issues/1168 #1168])

'''Items to Discuss'''
* New bugfix release
** Merge usagestats
** Need to finalize survey

=== April 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Chaining upgrades done ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Replace "Upgrade" description annotation with "upgraded_from" annotation to identify which tags to hide?

* [TE] Iterating handle_invalid_pipeline ([https://github.com/VisTrails/VisTrails/pull/1165 #1165])
** Not based on [https://github.com/VisTrails/VisTrails/tree/chain-upgrades-loop chain-upgrades-loop]
** Cherry-pick test to preserve source?
** Need maxPipelineFixAttempts option?
*** The code is now smarter about recursion, so max attempts will "probably" never be reached.
** Need [https://github.com/VisTrails/VisTrails/commit/0ef0667426937eddb1d1c1e397f0657ffec039a9 debug messages]?
*** Would need to be moved into handle_invalid_pipeline

=== April 6, 2016 ===
'''Updates'''
* [TE] Query View improvements
** Done except for displaying "Version Info" and #1164
* [RR] Working on finishing new interpreter (finally!)

'''Items to Discuss'''
* [TE] Chaining upgrades ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Try latest upgrade first, then previous.
** If all fail, select latest upgrade?

=== March 30, 2016 ===
'''Updates'''

'''Items to Discuss'''

* [TE] Query View improvements
** Unified do_version_switch and get_upgrades as validate_version()
** Problems with query view using its own controller
*** Fixed module info not being displayed for query results
*** Still no version info for query results
*** Still an issue with version query view not being updated

=== March 23, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Usage reporting almost ready to go
** Need to record whether specific features are used: paramexpore, mashup, query
*** [DK] Record if LaTeX extension is used? But hard to distinguish from direct batch invocation
** How to record size of vistrail?
*** [DK] IdScope already walks over vistrail, use that
*** but total number of modules and versions doesn't give an idea of average size of individual pipelines

=== March 16, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Upgrades in Query Mode
** Now using code similar to do_version_switch
*** Uses handle_invalid_pipeline
*** Differences: Not using current_pipeline, flushes changes
*** New controller method get_pipeline optimized using cached pipelines (but not current_pipeline)
*** Integrate to avoid repeated code?
*** Use this for query mode?
* [TE] VisTrails 2.2.4 ready for release?
** tej package updated. Others?
* [JF] upgrades and the version tree
* [JF] provenance in Jupyter
* [DK] bundles: [https://github.com/VisTrails/VisTrails/pull/1092 #1092]

=== March 9, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixing search mode
** String query now matches all by default
*** This caused pipeline queries to never match
** String query can search: User/Notes/Tagname/Time/Module name
*** Should we search module names by default? (Disabled by default because it is expensive)
*** Fixed notes search
** '>' parameter queries in documentation but has been removed
** Fixed module matches for upgraded pipelines (By not upgrading pipeline)
*** Upgrades still a problem
*** Add "Upgrade all menu option?" (Or upgrade all on open when `hideUpgrades`)
*** [JF] Allow search on past tags

* [TE] Create new bugfix release
** Finish querying
** Path issue on windows

* [DK] Look into sqlalchemy and new bundle branches

=== March 2, 2016 ===
'''Updates'''
* [TE] Fixed cache bug with port specs
* [TE] VisTrails Next
** Most packages now work
** No qgis for Python 3

'''Items to Discuss'''
** Always dereference symlinks? [https://github.com/VisTrails/VisTrails/issues/1146 #1146]

=== February 23, 2016 ===
'''Updates'''
* [TE] Fixed PythonSource 100% CPU bug
* [TE] VisTrails Next
** Updated [http://opendap.co-ops.nos.noaa.gov/axis/webservices/wind/ NOAA Web Service] examples
*** Now uses REST service, tabledata, and Google Maps
*** Web Service replaced with DownloadFile

'''Items to Discuss'''
* [RR] Couple of fixes are in for API, and tej&reprounzip on the Mac binary. Also new release of tej, and working on anonymous usage reports.
** New 2.2 release soon?
* [RR] Anonymous usage reports
** Sends out info like number of modules & versions, packages used, Python & libs versions, execution time, specific features [https://github.com/VisTrails/VisTrails/pull/1154 #1154]
* [JF] Bring in noWorkflow to track variable dependencies, for the considered Jupyter integration?
* noWorkflow - provenance for python scripts
** Recent work on tracking dependencies
* Also integrates ReproZip with Jupyter
** [http://mybinder.org mybinder]
*** Use with ReproZip to automatically build Jupyter notebook interfaces
* Daves comments on Jupyter integration
** It is possible to identify cell order on the server side
** Not trivial to track order of cells on client side
* How does Galaxy workflows relate to VisTrails?
** Packaging in Galaxy is hard
** Galaxy for biomedical workflows, difficulty making it general
* Action items
** How difficult to track cell dependencies in Jupyter notebooks?
** Use noWorkflow to track cell dependencies?
** How difficult to modify mybinder to use ReproZip packages?

=== February 17, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixed Group memory usage
** Modules in groups are supposed to be freed when done executing
*** Prevented by logger that stored references to the modules (fixed, now using id(module))
*** Prevented by list iterator bug that stored list of modules on the 'self' port bug (fixed)
* [TE] VisTrails Next
** Removed deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** PythonSources will be upgraded
*** Fixes for Python < 3
*** fixes for VTK < 6
** TODOs
*** Remove RemoteQ
**** Port Hadoop to tej (Already have pbs)
*** Merge package wrapper
*** Finish SQLAlchemy branch
*** Finish new bundle branch
** [JF] Will contact Jeff and Matthias about moving to Python 3
* [JF] Query by Example is broken
* [JF] VisTrails Data Cleaning Project
** Use VisTrails to process and explore task-specific data while keeping provenance.
** Remi's Idea
*** Use VisTrails as the backend in a Jupyter notebook
*** Overcome problems with executing cells in random order
**** Interesting research topic, but little interest has yet been noted
*** Interesting to study how such a notebook would be used (Is there notebook usage data available?)
*** Impose restrictions to notebook cell boundaries
*** It will only work for functional operations
*** Can we fix, or detect, non-functional (mutating) operations?
*** Analyse code and data flow and see if it mutates data in unexpected ways?
*** Mutable operations can be created in many ways in Python
* Next meeting Tuesday 11:30

=== February 10, 2016 ===
'''Updates'''

'''Items to Discuss'''
* VisTrails Next
** Test suite passes
*** Python 3 less deterministic, module upgrade order random.
** [RR] updating packages: Reprounzip (pushed), tej, persistent_archive, ...
** All of our packages should run fine :)
** VTK thumbnail comparison works
*** Rendering bug on some systems
**** QVTKCell now inherits QGLWidget
*** Old thumbnails had wrong height due to spreadsheetwindow being too small
**** Fixed by regenerating thumbnails
*** Silenced deprecation messages when generating modules
*** Many new classes in VTK 7
** Remove deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** Will break existing PythonSources
**** Try to upgrade?
*** Old-style packages
**** Or only allow a new style, like __init__.py renamed to info.py? (merge with identifiers.py?)
***** Read info.py without importing package?
*** Fixes for Python < 3
*** Fixes for Qt < 5
*** fixes for VTK < 7
*** Remove self port?

=== February 3, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] [http://lists.vistrails.org/pipermail/vistrails-users/2016-January/000402.html Rendering a .pvd (ParaView) file?]

* VisTrails Next
** All tests but thumbnail comparison passes
** Still issues with gui and more packages needs to be tested
** PythonSource and MplSource upgraded with lib2to3
** Keep contrib packages? Update?
** [https://blog.kitware.com/vtk-7-0-0/ VTK 7 is released]
*** Supports Python 3
*** Will hopefully get into conda and others soon
*** Deprecates a bunch of modules

* [https://travis-ci.org/VisTrails/VisTrails/builds/106743348 Travis builder] for VisTrails Next
** Runs!
** Uses conda
*** Many levels of requirements
**** apt packages
**** conda packages
**** python packages in requirements.txt
**** python packages in setup.py
*** Can probably drop conda. Default builder does not have Qt5, but beta builder do!
*** But useful if we want to use conda in our own build process.
** Lots of errors I do not get locally?

* [http://goo.gl/forms/Z4HBrwaBWL User Survey]
** Have you used any alternatives to vistrails?
*** Relevant? More options?
** How often do you use any of these particular features in VisTrails?
*** Add/Remove alternatives?
** How important would you rank the following potential improvements to VisTrails?
*** Add alternatives?

=== January 27, 2016 ===
'''Updates'''
* New interpreter
** Working prototype soon
** Looping not completely done (and port combination mode: pairwise/cartesian...)
** Need to integrate with VisTrails
*** Compatibility with existing modules
*** Use log controller
*** Want to cache at multiple levels (whole stream/single element of stream)
*** Non-runtime attributes of modules (cache check, automatic conversion check, constant from/to string)

'''Items to Discuss'''
* User Survey

* ZMQ failing on windows (vistrails-users)

* [TE] [https://github.com/VisTrails/VisTrails/pull/1143 Python 3 branch]
** Testsuite almost passes
*** Failing are unicode filenames, some users guide examples, and thumbnail comparisons.
** Fixed issues
*** Signatures are now bytes (convert to string to show in widget)
*** Cannot compare different types, e.g., (None < 1)
**** PortSpec.depth and min/maxConn could be None. (Backport!)
**** cell.row could be None
*** Lots of unicode/bytes fixes to serializations
**** We have encryption implementations in the code! (keychain)
*** Lots of small fixes to package method differences
** Current issues
*** logging widget empty?
*** version tree signals messed up
*** provenance view legend icons black
*** Text do not fit in some widgets
*** VTK thumbnail comparison fails
**** VTK Cells have some faces in wrong direction?
**** Because running in VM?
** Installing on Ubuntu LTS/Latest Mint
*** Install latest matplotlib from pip
*** Install VTK 7.0.0rc2 from source
*** No QtWebEngine binary (controversial) (Must install sip/PyQt5/Qt5 from source)

=== January 20, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Backporting features from Python 3 + PyQt5 + Qt5
** Merged unicode with master ([https://github.com/VisTrails/VisTrails/tree/unicode unicode])
*** One unicode test failing
*** Problem saving to xml
** Used [http://python-future.org/ python-future] to run futurize stage 1 to update legacy (pre 2.6) code ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized unicode-futurized])
*** Updates print to functions 'from __future__ import print_function'
*** Updates exception calls to use 'as'
*** removes most usages of 'long' (mostly used unnecessarily)
**** Only needed for 32-bit support
*** Fixes relative imports (from __future__ import absolute_import)
** Fixing code that is deprecated in Qt 4.8 and removed in Qt 5 ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized-qt5 unicode-futurized-qt5])
*** Updated all signals to new-style
* If we go 2 to 3, this could break packages
** means we should schedule any package format changes for the same time
** e.g., imports should be unrelated to code path (function to load module from package identifier?) (take them out of vistrails.* [https://github.com/VisTrails/VisTrails/pull/1002 #1002])
** any structural changes (e.g. the __init__ versus init thing) (RR thinks it makes sense, though having both named "init" is unfortunate)
** putting package identifier as xml?
*** Python not so bad, plus some stuff in there is Python code (checking dependencies)
** version the APIs?
*** RR planning on versioning vistrails_module.Module, no point versioning the whole package?
* file formats on 2 to 3:
** no real translation/upgrade, but non-ascii values that work on 3 won't load in 2

=== January 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://gist.github.com/rexissimus/dfd27e466427529c385c Porting to Python 3 / PyQt5]
** Basic GUI and execution works
** Minimal work to support 2to3
** Hard to support both PyQt4 and PyQt5

=== January 6, 2016 ===
'''Updates'''
'''Items to Discuss'''
* Updating VisTrails dependencies
** Successfully built [https://gist.github.com/rexissimus/f1a1aada7de1c00a57c7 Win7-64/Python3/PyQt5/Qt5/WebEngine/VTK7]
*** VTK 7 is the first supporting Python 3 but is only in release candidate phase.
**** Next version of VTK 6 is rumored to support Python 3
**** There is a development branch of VTK 6 supporting Python 3
*** Can travis build this?
**** We can skip tests for WebEngine and VTK if needed
** Python 3 [https://python3wos.appspot.com/ showstoppers]
*** No MySQL-python (sqlalchemy supports mysql through other drivers)
*** No suds (there are active forks but we could also drop support?)
* Options for python2/3 support:
** Interpreter could be python2/python3 based on packages
** six layer works but not the easiest to maintain (e.g. in reprozip)
* Drop support for win-64
* Update copyright headers to 2016

== 2015 ==

=== December 30, 2015 ===
'''Updates'''
* Bokeh package finished
** Can output to Browser/IPython/Spreadsheet (Limited functionality in spreadsheet)
'''Items to Discuss'''
* Updating VisTrails dependencies
** Bokeh needs QWebEngine (Chromium) in Qt5 which requires PyQt5
*** Many plotting libraries only work in browsers
*** But Chromium may be a big and controversial dependency
*** Or create a browser version of the spreadsheet?
** Some users have requested Python 3
** Not backwards compatible?
** Target for VisTrails 3.0 with new interpreter?

=== December 16, 2015 ===
'''Updates'''
'''Items to Discuss'''
* Users list question
* [TE] Wrapping Bokeh
** Added bokeh property parser
*** complements numpydoc parser
*** Not all attributes are available, partially because I am using a pre-release version.
** Wrapped modules
*** bokeh.plotting finished (Backwards like matplotlib: Create plot then draw on it)
*** bokeh.charts mostly done (Missing arguments)
** QWebView mostly works (but no zooming or buttons)
*** It would be better to use external browser or QWebEngineView
** Added improvements to wrapper
*** Generalized port translations (Color/Path to native types)
*** Can use multiple docstring/property parsers simultaneously

=== December 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Looking into wrapper
** Will port TensorFlow
** Doing a pass on the wrapper code & doc
*** UX improvements
** Factorize high-level docstring parsers into core.wrapper? (sphinx, numpy, google)
** Problem with name vs module_name (fails sklearn tests because class_by_name() is broken)
** Looking into compressing specs, lazy registration of modules

=== December 2, 2015 ===
'''Updates'''
* [TE] Package wrapping
** Wrapped most of numpy/scipy using __all__
** Added class attribute and method access for classes (Can add to class or to separate inspector module)
** TODO: Document wrapping procedure

'''Items to Discuss'''

=== November 25, 2015 ===
'''Updates'''
* [RR] New interpreter is coming along
** Everything is a stream
** Task system, eventually work-stealing parallelism
** Streams no longer advance in lock-step
*** Allows for constructions like filter, join, sorted-merge
** depth>1 still to be tested, no current plan to allow this through the module interface
*** Through looping though, can do streams of streams

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapped most numpy functions (no polynomials)
** and half of scipy classes and functions
** Added functions manually from documentation (no parseable lists?)
** Focusing on data flow constructs (no property/method access for classes)
*** Using spec diff (empty for now) and dynamic parser (stores spec in .vistrails/)
** Python class/function wrapper now stable
** Add google doc parser?
*** Is there a parser available?

=== November 18, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Numpy class wrapping works
*** Basic type is List, since most types are array_likes.
*** TODO: More classes and functions
*** Some operations are in-place and some aren't, and docstring not super clear
*** [RR] It seems only methods mutate, and most have a numpy.xx function equivalent; just manually go through the methods and remove the mutating ones?
** Class wrapper is modular
*** Docstring parser and type string parser can be customized
*** Classes can have optional attribute/method ports
**** Inspectors and attribute/method modules can be created separately
** Use PythonCalc as an example
*** Can be re-implemented as a function with a parseable docstring
*** [RR] PythonCalc is just an example, and it might actually make sense to get rid of it, or do a proper math package with scalar operations (as separate modules, no combobox)
** [RR] TensorFlow to use wrapping as well
*** Very simple (only types 'tensor' & 'variable')

=== November 11, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapping numpy's classes using numpydoc (ndarray)
*** Wrapping constructor arguments, attribute getters/setters as module ports
**** Then how to access attributes afterwards?
***** Use input value port to class modules?
*** Wrap methods as modules? E.g., `ndarray.shape`.
*** Function wrapping is almost a subset of class wrapping
**** May be able to use the same parsing/execution methods
** VTK's non-getter/setter methods could be wrapped as modules
*** We could then remove extra logic in interpreter for keeping function order
** Bokeh uses autogenerated docstrings
*** We may be able to read the specification directly

* [RR] [https://github.com/VisTrails/VisTrails/pull/1138 TensorFlow package]
** Basic setup working, can execute the Mandelbrot example
** Will autogenerate the operations

=== November 4, 2015 ===
'''Updates'''
* [RR] Interpreter work requires a fix for [https://github.com/VisTrails/VisTrails/issues/1137 DB issue #1137]
* [DK] Kitware's Resonant [http://www.kitware.com/source/home/post/173]
** [https://github.com/girder/girder Girder]: data management system
** [https://github.com/Kitware/romanesco Romanesco]: execution engine, uses [http://www.celeryproject.org/ Celery] for task management
** Resonant Flow: web app for editing and executing workflows

'''Items to Discuss'''
* [TE] Added OSX Lion (10.7) VM on build machine using vagrant (seems ok with license?)
** New builds works on Lion
** Change the minimum requirement to 10.7?
* [TE] Package wrapping
* Added upgrade suggestions using 2 spec versions ([http://pastebin.com/30XUU8Gp example])
** using name edit distance to find matches
** Could use something better like port similarity for modules, and type similarity for ports
** Should write python upgrade code?
** Added spec to sklearn package
*** Can now diff spec versions and keep the spec static
*** There will be problems with downgrades and package versions

=== October 29, 2015 ===
'''Updates'''
* [TE] nightly-build-mac fixed (Needed to approve xcode license)

'''Items to Discuss'''
* [TE] matplotlib wrapper
** ported to general spec
** Diff can be used on general spec
*** Only needed minor changes
*** Fixed indexing bug that corrupted specs
*** Can now move diff tools to core/wrapper
** Add new plots?
*** New plots in mpl 1.3: eventplot
*** New plots in mpl 1.4: angle_spectrum, magnitude_spectrum, phase_spectrum', violinplot
*** No new plots in mpl 1.5 (from looking at boilerplate.py)

=== October 21, 2015 ===
'''Updates'''
* [RR] Alexis has arrived, will be working with [RR] on a more efficient interpreter

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package]
** Supporting multiple package versions
*** Check which version can be loaded [https://github.com/VisTrails/VisTrails/pull/1135 #1135]
*** We cannot show version requirements in the list of packages because old packages are loaded when importing the codepath
** Visual diff does not work well, but we can use the spec differ to see differences.
** Unifying vtk and matplotlib wrapping specs (WIP)
*** And porting matplotlibs spec differ to work on the general spec
*** Spec differ can then be used on vtk and other packages in the future
*** Will enable automatic upgrade generation
* [RR] Rework interpreter
** restore abstraction between interpreter/module code
** build looping, streaming, caching into the interpreter
** rework cache
** look into parallelism once basic functionality is there

=== October 14, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package] (adding numpydoc parser)

=== October 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/tree/fix-matplotlib-parser New matplotlib parser] (adding numpydoc parser)
** Added numpydoc attribute parser for plots.
*** TODO: Need better port spec reconciliation with call signature parser.
*** We can create a general numpydoc parser, but attribute types are unique to matplotlib.
** Needs package versioning
*** New spec will not support matplotlib < v1.4 due to changed path to axes classes.
*** Load spec version corresponding to installed matplotlib version?
*** Need version downgrades?

=== September 30, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Updating Matplotlib parser
** Matplotlib docstring parser fails on numpy docstrings
** I have [https://github.com/VisTrails/VisTrails/commit/eae8b0c16260810587e47c41cab53552cbb3cf0a added basic numpydoc parsing]
*** Only used by a few docstrings so far
*** Parsing uses many sources (class tables, signatures, ACCEPTS, method docstrings, definition parsing).
** Caswell said they were thinking about moving to traitlets, but this is not ready yet

=== September 23, 2015 ===
'''Updates'''
* [TE] VisTrails 2.2.3 released
** Also have pushed to PyPI, binstar, etc.
** Sourceforge vs. GitHub
*** should be able to host releases on GitHub
*** nightly binaries pushed to sf each night
*** old binaries?
* [TE] Re-wrapping MatPlotlib
** Keep static generation - Docstrings are brittle beween matplotlib versions
** Keep generating the executable classes - but create functions, not vistrails Modules
*** Why is there so much patching?
** Re-implemented Alternate PortSpec for InputPortSpec
*** It will now inherit specs from parent (No need to reimplement)
** Module upgrades?

'''Items to Discuss'''

=== September 16, 2015 ===
'''Updates'''
* [TE] Job Monitor tests and documentation done
** OK to leave document package in packages directory?

'''Items to Discuss'''
* [TE] Library wrapping: How to do code patching? [https://docs.google.com/drawings/d/1Sh3eOXot6v2y880jHKQrqXqAwr-0aoqYligg3z8G8MY/edit?usp=sharing Wrapping diagram]
** Insert code into module template (Old VTK code)
** Patch the library that is called (New VTK code)
** Somehow store code in spec and apply when executed?
*** Executed code needs at a minimum access to inputs, outputs, current class
*** Use standard input/output dict and obj reference that the code operates on?
*** Can this be done while keeping the execution abstract?

* Do new release now?

=== September 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* New release?
** [RR] wants reprounzip
** tej changes & doc
** job monitor & jobmixin fixes
** mongodb
** reprounzip
** warning: MplFigure type is int
** tabledata: add Reshape, DictoToTable & ListToTable, fix ListToTable with numpy arrays
** PythonSource can have same name for an input & output
** don't show spreadsheet at exit

=== September 2, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Limit autosaves? [https://github.com/VisTrails/VisTrails/pull/1126 #1126]

=== August 26, 2015 ===
'''Updates'''
* [TE] Added Job support to Parameter Explorations (Requested by Colin), and Mashups
** specify job ids, need to specify different ids for parameter explorations since they have the same version id
** how to deal with parameters passed in on command line
* [General] provenance: should be creating a new version when we execute workflow with changed parameters?
** currently, custom_params annotation stores this in provenance currently
** [RR] API doesn't record provenance if passing in parameters: http://git.io/vsAA5
'''Items to Discuss'''

=== August 19, 2015 ===
'''Updates'''
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [TE] Working on Job Monitor documentation

'''Items to Discuss'''
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [TE] Stop testing VisTrails 2.0?

=== August 12, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Build broken on Travis; because of IPython 4 released today? ([https://travis-ci.org/VisTrails/VisTrails/builds/75279795 build 992]; [https://github.com/VisTrails/VisTrails/issues/1123 #1123])

=== August 5, 2015 ===
'''Updates'''
* [TE] Fixes to Jobs
** Could not delete jobs
** Could not run job in group
** Job not reset when calling ModuleSuspended
** Added deleting job from context menu
* [RR] Writing documentation for everything [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

'''Items to Discuss'''

=== July 29, 2015 ===
'''Updates'''
* RR still looking into new interpreter thing
** Goal is to take out scheduling logic from Module so it can be split in multiple processes, and so that smarter strategies can be added in time
** This means some work on packages
** Spreadsheet can live in kernel process? Still some UI stuff that will take work (changing configuration, persistent archive's viewer, ...)
* [TE] Problems running examples [https://github.com/VisTrails/VisTrails/pull/1111 #1111]
** Testing of more examples requires additional packages on the test machines.
** Fixed faulty line-ending in PythonSource:s failing on Python 2.6.
** Test suite now testing SUDSWebServices (If web service is down, test suite will fail)
** preferences.py test failed reloading 'dialogs' package, switched to using 'URL'.

'''Items to Discuss'''

=== July 22, 2015 ===
'''Updates'''
* [TE] mailing lists back online
* [TE] Working on [https://github.com/VisTrails/VisTrails/issues/1107 #1107]
* [RR] Working on ReproZip package

'''Items to Discuss'''
* [RR] MongoDB package [https://github.com/VisTrails/VisTrails/pull/1106 #1106]
* [RR] Example for tej docs? [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

=== July 15, 2015 ===
'''Updates'''
* 2.2.2 released

'''Items to Discuss'''
* RR is considering executing everything in an IPython kernel (i.e. separate Python interpreter, like the one spawned for a notebook)
** It's a separate process that we can restart without restarting the app/gui
** We can isolate the execution environment (e.g. for the server)
** We can run the whole thing remotely (if your data is elsewhere, just run VisTrails locally and the pipeline elsewhere)
** Pipeline execution no longer makes the interface hang, it just makes the kernel hang (but that's fine)
** We can use notebooks as modules (probably way nicer than the PythonSource module)
** We can run multiple kernels so long as the ports carry things that are serializable
*** meaning we can put the multithreaded-interpreter without all the hacky parts it has now
*** we can run IPython kernels in all the languages IPython supports, [https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages currently 46]

=== July 8, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Buildbot github hook not working after IP address change
* [TE] No reference to VistrailsApplication ([https://github.com/VisTrails/VisTrails/issues/1103 #1103])
** [RR] Added PR [https://github.com/VisTrails/VisTrails/pull/1104 #1104]
* [TE] Reopening VT file after saving with bundled subworkflow won't offer subworkflow upgrade ([https://github.com/VisTrails/VisTrails/issues/1102 #1102])
** allow manual delete to fix right now
** fix this on top of the use-uuid branch
* [TE] Release VisTrails 2.2.1? ([https://github.com/VisTrails/VisTrails/blob/v2.2/CHANGELOG CHANGELOG])
** [https://github.com/VisTrails/VisTrails/pull/1093 output-modules-use-global-dir]
** [https://github.com/VisTrails/VisTrails/milestones/version%202.2 Current issues for 2.2]

=== July 1, 2015 ===
'''Updates'''
* [TE] PROV fixed
* [TE] Working on subworkflow issues
* [RR] Considering reworking the controller (log vs exception problem, retained upgrades causing interferences) and also the interpreter (IPython?)

'''Items to Discuss'''

=== June 24, 2015 ===
'''Updates'''

'''Items to Discuss'''
* UV-CDAT
* [TE] Can a cyclic workflow be valid? ([https://github.com/VisTrails/VisTrails/issues/1097 #1097])
** focus on disabling the ability to create cyclic pipelines because more things break than just this with a cyclic pipeline
* [RR] Relative paths ([https://github.com/VisTrails/VisTrails/pull/1057 #1057])
** This interacts with the new bundle; how do handle packing files inside the VT bundle?

=== June 17, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] current_version and reusing existing upgrades are broken ([https://github.com/VisTrails/VisTrails/issues/1095 ticket #1095])
** Could be that export to PROV is using an unflushed upgrade pipeline?
** current_version would then be correct.
** It may work to flush the actions before exporting?

=== June 10, 2015 ===
'''Updates'''
* DAT: fixed VTK issue on Linux and Mac
* Still crashes on Windows. Need help! Reminder: this works in the VisTrails spreadsheet (QCellPresenter), although no widget get changed there during a drag
** Is it a VTK bug?
** Is it simply impossible to change widgets during the drag, should we do it a different way?
** Did I miss something that is done in VisTrails but somehow not in DAT?
** Low prio, UV-CDAT doesn't run on Windows anyway

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 Updated pull request])
* Single instance code and batch mode

=== June 3, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 pr])
** Requires fixes to command line parameters, Output modules, and batch mode
** How to test this
** Updated missing/outdated flags
** Fixed view issues when generating graphs
* [TE] batch mode
** SpreadsheetOutput not enabled in batch mode. Should we check is_running_gui instead?
** Other instance setting flags from caller
** Is graphsAsPdf replacing spreadsheetDumpPdf?
** graphsAsPdf true by Default?
** Batch mode executing by default (Not needed when generating graphs)
** Re-added workflowInfo as withWorkflowInfo for writing graph and xml workflow
** [DK] batch mode should be outputting to files or stdout, shouldn't always trigger SpreadsheetMode
** execute flag, maybe make execution the default and allow a "--no-execute" if you only want to capture graphs, for example

=== May 27, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] API question
** http://lists.vistrails.org/pipermail/vistrails-users/2015-May/000357.html
* Status of DAT
** Can add VCS plot to DAT but need to work on configuration windows
** Documentation for graphics templates for UV-CDAT/vcs?
* Qt support?

=== May 20, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Reviving the DAT, integrating scripting & porting UV-CDAT!
** On [https://github.com/VisTrails/DAT GitHub] ([https://github.com/VisTrails/DAT/issues issues])
** Merging 2 years of development taking longer than expected, but getting there. The plan is to get the patches in VisTrails and never fork again, we never want to get in UV-CDAT's situation (and don't need to).
** VTK cell works fine on Linux but there was flickering on Mac & Windows before; still issues on Mac (Windows status unknown)
** Can get a VCS plot soon (but will need VTK cell fix)
** Integrate in UV-CDAT's build system (so we have cdms, VCS, ...) -> RR can do this, low priority
** How do we integrate scripting?
*** We want to be able to seamlessly make changes to a plot by changing Python code
*** Define new plots by entering Python code without writing modules/packages?
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 13, 2015 ===
'''Updates'''
* [RR] Test skipping whitelist ([https://github.com/VisTrails/VisTrails/pull/1069 #1069]) -- low priority
* [RR] Custom matplotlib modules can't be compatible with both 2.1 and 2.2 ([https://github.com/VisTrails/VisTrails/issues/1067 #1067]); should be fixed for ALPS ([https://github.com/VisTrails/VisTrails/issues/1070 #1070])

'''Items to Discuss'''
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 7, 2015 ===
'''Updates'''
* [RR] Export/import workflow to Python working!

'''Items to Discuss'''
* [Claudio] UV-CDAT
** The UV-CDAT project is the biggest user base of VisTrails
** VisTrails package management provides a lot of friction towards people plugging in their code
** Need to make it easy to integrate your random Python scripts in the system without having to deal with all the boilerplate, at least in the first step
** [RR] argues that modules are still good; UV-CDAT shouldn't move towards a purely script-based backend
** [RR] export/import with Python could reduce a lot of that friction by allowing 1) to edit workflow as Python 2) to open up boxes automatically if needed code doesn't match actual modules
** ...

=== April 29, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] <strike>Abstractions</strike> subworkflows status ([https://github.com/VisTrails/VisTrails/labels/subworkflows tickets])
* [RR] matplotlib compatibility (2.1 & 2.2), [https://github.com/VisTrails/VisTrails/issues/1067 #1067]
** RR to try and fix ALPS matplotlib modules

=== April 22, 2015 ===
'''Updates'''
* 2.2.0 has been released!
* Windows issue (via email from Ryan)
** issue with manifest file (may be a new file in VTK6?)
** Tommy has regenerated new Windows builds
* Binaries, pypi, and conda released
* [RR] Export as script
* Python sources using VTK need to switch to SetInputData (users should be aware of this)

=== April 15, 2015 ===
'''Updates'''
* Ready for 2.2.0 (apart from binary/deps issues)
** Missing some libs (scikit-learn, tej, tdparser, SQLAlchemy+connectors
** Windows: runvistrails.py is no longer used, so the PATH is wrong
** Windows: pip is broken, but it probably wouldn't work anyway because of permission issues (disable this?)
* Queries, upgrades and getPipeline() usage ([https://github.com/VisTrails/VisTrails/issues/1054 #1054])
** Getting a pipeline with getPipeline() is not safe: it might return an invalid pipeline
** This is used in many places throughout the code, like queries
** Upgrading would require going through the controller, but that creates new actions
* [TC] Avoid copying a module's output if it's used as input by exactly one downstream module ([https://github.com/VisTrails/VisTrails/issues/1060 #1060]) (useful for big numpy arrays you can update in-place)

=== April 8, 2015 ===
'''Updates'''
* [DK] Merged RR's changes for output modules (1012 and 1013)
** RR will merge remaining changes, then create v2.2 branch!

'''Items to Discuss'''
* BNL need numpy array to VTK image
** Looks like VTK has some helpers for this
** We will help if issues arise
** Will contribute back to VisTrails package
* Upgrade issue: [https://github.com/VisTrails/VisTrails/issues/1017 #1017]
** Automatic upgrades should happen between versions of provided upgrades
** Our existing upgrades work around this so it doesn't need to be 2.2.0
* Corner-case VTK modules
** No longer need VTKCell input port, so don't interfere with registry and API anymore
** Still work weirdly, people probably shouldn't use them
** But we have lots of clunky modules since we wrap the whole of VTK; some people might rely on this and know how to use them, let's keep them anyway
** Ready for 2.2.0

=== April 1, 2015 ===
'''Updates'''
* [RR] UV-CDAT: bugfixing for 2.2, long-term plans: implement scripting import/export in VisTrails, port to UV-CDAT
* Possibly, try to move to regular VisTrails to use new features

'''Items to Discuss'''
* 2.2 release: nothing much is pending anymore, release next week?
** [TE] vtkExporter classes [https://github.com/VisTrails/VisTrails/issues/1032 #1032]
** [RR] Hiding upgrades in version tree might make it (or might be 2.2.1 so we can test it out) [https://github.com/VisTrails/VisTrails/issues/949 #949]
** Output modules changes to go in
* add note to documentation about order of parameters in VTK
* add issue about exporter upgrades if not already there

=== March 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* 2.2 release
** Checklist on Github: https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist
** Review output modules
** RR has a couple more issues to fix
** Ready to go -- sign app package for OSX? [https://github.com/VisTrails/VisTrails/issues/984 #984] We need access to the Apple Membership team

=== March 18, 2015 ===
'''Updates'''
* [TE] VTK6 works

'''Items to Discuss'''
* [RR] Release v2.1.5 with backported tabledata?
** MTA example needs updated tabledata (for JoinTables)
** Google Maps package still not available
* [RR] Work torward v2.2.0?
** changes:
*** new persistence
*** API changes
*** output module changes (upgrades?), maintain cells but try to upgrade
*** not wrapping stuff
*** VTK6? yes
*** JobSubmission stuff?
*** relabeling for upgrades [https://github.com/VisTrails/VisTrails/issues/949 #949]
** makes sense, needs the tree view code to be updated, check selection
** See [https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist 2.2 checklist]
* Discussion of [https://github.com/VisTrails/VisTrails/issues/1016 #1016]
** plumbing between outputs and output modes, how to define a mode that works for many outputs without writing for each output?

=== March 11, 2015 ===
'''Updates'''
* [RR] persistent_archive done; merge? ([https://github.com/VisTrails/VisTrails/pull/755 #755])
** note about the focus events for widgets
** TE be aware of file_archive for future binaries that include persistent_archive
* [TE] [https://github.com/VisTrails/VisTrails/pull/998 New VTK package] finished

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails? (see last week; decision needed)
** RR email to JF about this
** yes; email sent to Github
* [RR] Switching order of output ports ([https://github.com/VisTrails/VisTrails/pull/1006 #1006])
** added port specs are sorted at a separate spot (Module.*_port_specs properties) than those in the registry (which are sorted in the registry), but those two lists are just combined without respect to sort keys
** need to determine whether the two lists should be merged or remain distinct
** should make sure that order of input ports and output ports makes parallel connections for things with same order
** DK suggests breaking backward compatibility here: workflows still run, can fix easily if a problem in an existing package.
* [RR] Question about output modes ([https://github.com/VisTrails/VisTrails/pull/1007 #1007]), how to integrate in API ([https://github.com/VisTrails/VisTrails/pull/24 #24])
** Should ImageFileMode be removed? ("image" is not a mode, "file" is)
** ImageOutput missing?
** Feel free to change how formats works
* [TE] Test suite segfaults on Fedora 17 virtualbox. Install newer version? (Support ended in 2013)

=== March 4, 2015 ===
'''Updates'''
* [TE] VTK wrapper
** Works on VTK 5.10
** Still need to test VTK 6
** New general wrappers for python functions and classes

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails?
** When [http://i.imgur.com/UTY2qfg.png filing a pull request] from UV-CDAT/VisTrails, VisTrails/VisTrails is selected by default
** People keep forgetting to change the default ([https://github.com/VisTrails/VisTrails/pull/956 #956] [https://github.com/VisTrails/VisTrails/pull/968 #968] [https://github.com/VisTrails/VisTrails/pull/999 #999] [https://github.com/VisTrails/VisTrails/pull/1000 #1000] [https://github.com/VisTrails/VisTrails/pull/1003 #1003] [https://github.com/VisTrails/VisTrails/pull/1004 #1004] [https://github.com/VisTrails/VisTrails/pull/1005 #1005])
** Only way to change that is to not have it marked as a fork of VisTrails/VisTrails
** Github staff [https://gist.github.com/remram44/b364c24ef1e462ce6e2f can make that change for us]; should we do it?
** Juliana: comments on this? visibility vs. convenience/annoyance for developers
* [RR] What about [https://github.com/VisTrails/VisTrails/issues/991 #991]?

=== February 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] vtkviewcell for infovis support, can we unify with VTKCell?
** need to test this
* [TE] vtk wrapping
** Mostly finished
** VTK 5.10 produce incorrect results with old wrapping
*** Old wrapper is based mostly on VTK 4
*** Most vtk_examples affected
*** [http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Replacement_of_SetInput]
*** should be able to upgrade from SetInput to SetInputData (need to drop GetOutput and replace with self ports)
*** can we change vtkInstance to just return self and not wrap things
** terminator example not working under 5.8?
* How does VTK wrapping fit into general wrapping framework?
* [RR] new persistence package

=== February 18, 2015 ===
'''Updates'''
* [RR] New VisTrails API and IPython integration ([https://github.com/VisTrails/VisTrails/pull/24 #24])

'''Items to Discuss'''
* [TE] VTK wrapping
** [https://gist.github.com/rexissimus/16b74693545b5e7c1035 Benchmarking vtk package]
*** Old: 24.7 seconds
*** New: 10.5 seconds (Except first time that adds 8 sec)
**** The parsing that calls is_abstract (that tries to instanciate all vtk classes) is now only run the first time.
**** get_items_from_sigstring takes 2 seconds, maybe we can use a lookup dict for already computed sigstrings?
** Now using a general python function wrapper
*** VTK classes are wrapped into python function that does not depend on vistrails
*** VTK functions can be executed without vistrails
*** The spec maps functions into vistrails modules, but can also describe wrapping
*** A general python function wrapper that supports
**** kwarg inputs
**** single, list, dict outputs
**** callback for progress reporting
**** temporary file generator for using FilePool
**** optional output generation
*** Creating specs:
***** Create spec by hand
***** Auto-create spec outline (TODO) and manually finish it
***** Dynamically create spec (VTK)
***** Implement documentation wrappers (Can use scikitlearn wrapper to wrap numpydoc) (TODO)
***** Classes as bad functions needs to be wrapped in new functions before they are wrapped. This is different for each package.
****** Classes is hard: Like VTK, and matplotlib. Scikit-learn does still not wrap classes
***** Spec diffing and patching could be done using code from matplotlib.
** Still needs upgrades from old VTK package
*** Is it possible to dynamically wrap functions, e.g, you see a SetFunc and just remove the 'Set' prefix. Or do you need to create a complete mapping?

=== February 11, 2015 ===
'''Updates'''
* Update from Friday's meeting
** discussed VisTrails internals
** discussed wrapping
*** xml discussion, hard to modify because tied to db code
*** TE has made it possible to add the schema-defined attributes to the intermediate representation
*** higher-level operations on the port specs
** make sure the simple case works
*** [JF] take a simple package with documentation and figure out what the base case for wrapping is

'''Items to Discuss'''
* [TE] VTK wrapping
** Dynamic loading works
** Reading XML is fast enough, but [https://gist.github.com/rexissimus/8272d3c776ccfa115d82 unserializing data is slow]
** Working on patterns for patching
** Matplotlib has many advanced patterns like argument ordering, nested arguments, alternateSpecs, output types.
*** Having all this in a general wrapper might confuse users?
** [RR] Delay module (except for identifiers) until you need it---e.g. don't deal with port specs, etc. until necessary
* Scripting Support [https://github.com/VisTrails/VisTrails/pull/950 #950]
** [RR] Issue with getting code from modules
** Design a simple solution
** [JF] Couldn't you use modules as black boxes without conversion, just to call into modules/subworkflows easily from e.g. IPython?
*** [RR] This is a job for the API, and a very separate use case. See [https://github.com/VisTrails/VisTrails/pull/24 #24]

=== February 4, 2015 ===
'''Updates'''

'''Items to Discuss'''
* Wrapping
** Format to use? Currently XML (like current matplotlib)
*** JSON and YAML have simple "to python dictionary" methods
*** But don't stream
*** YAML a lot easier for humans
** [DK] vtk-new-package also changes parameter names, creates enumerations
*** intermediate schema needs to be extensible
*** packages will want to store there specific infos for compute() method generation
*** also might have specs-altering info, like matplotlib's alternateSpec
** representation to code , registry already has schema for some aspects
** [RR] We might want to see if Module subclasses can be created lazily
*** no need to create all the classes just to register them in the registry and never actually use most of them
*** future effort
* [RR] Where should VisTrails packages live?
** tej installs as 'vistrailspkg.tej', TE installed it as 'userpackages.tej'
** Currently, standard packages are 'vistrails.packages.', user packages are 'userpackages.' and packages loaded through pkg_resources might be anything
** [RR] Use 'vistrailspkg.' everywhere?
** Long-term effort to simplify package distribution/installation (and have VisTrails get them automatically?)

=== January 28, 2015 ===
'''Updates'''
* T. Caswell to come visit on Fri 6 to discuss wrapping work

'''Items to Discuss'''
* [TE] New VTK wrapping
** Current code by DK seems a good deal faster
** Generates XML that can be patched/tweaked, generates Python code from it, VisTrails only loads generated Python code
** RR would rather have VisTrails load intermediate representation (= XML) directly, wants to make sure this is not slower
** The goal is to turn the intermediate step into something generic that would be used for every wrapped package (vtk, numpy, matplotlib, sklearn, java) instead of each having its own
** TC has its own code at [https://github.com/Nikea/VTTools/blob/master/vttools/wrap_lib.py github:VTTools] which parses numpy docstrings and generates modules, doesn't yet handle classes or persist anything
* Web crawler
** Right now, TE starts jobs for "start crawler", "stop crawler", "install classifier"
** RR would rather have the crawling be a job as far as VisTrails and tej are concerned
** The whole thing would be one pipeline: load examples, train classifier, start crawler [check for job, kill previous one, upload model, start processes], get snapshot, visualize
*** Need some support in tej and job submission system: long-running jobs, stop a job (wait for it to finish?), restart a job even though results are cached

=== January 21, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Unified wrapping method discussion [https://github.com/VisTrails/VisTrails/issues/991 #991]
** TE to work on reusable method with intermediate representation, starting with VTK
* [RR] Examples for scikit-learn: JF has an old example using Weka with parameter exploration (not currently in source tree)
** AM's examples are enough
* [AM] scikit-learn package is done, merge it in? [https://github.com/VisTrails/VisTrails/pull/955#issuecomment-70286788 #955]
** RR will merge
* [RR] What should copyright headers say? [https://github.com/VisTrails/VisTrails/pull/994#issuecomment-70173935 #994]
** Let's keep everything in there: Utah/Poly/NYU

=== January 14, 2015 ===
'''Updates'''
* [TE] Working on classifier
* [RR] Scripting integration, work in progress

'''Items to Discuss'''
* [RR] Unified wrapping method discussion ([https://github.com/VisTrails/VisTrails/issues/991 #991])
** Let's talk next week, [AM] and [DK] are not here

=== January 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* make sure that we address critical issues, questions, and pending review branches in a timely manner
* scripting support
** [RR] no issues if we want to just keep annotations in the generated code to allow the link back to a workflow
** [RR] can translate from workflow to script, working on script to workflow
** will work for parameter value changes, structural changes require changes to the annotations
** need to publish best practices here
** would be cool to do looping in scripts (easier interface than with workflows)
* notebook support (convert form notebook to workflow)
** RR will sync with FC on this
* Issue with console in built-from-scratch
** [TC] iPython rearranged some of the completion stuff in 2.2 and 2.3
** binary has old version of iPython -> 1.0.0, should we update?
* [TC] automated wrapping of numpy and scipy
** discovered a bunch of malformed documentation in numpy and scipy
** has github repo for vistrails tools
** example modules wrap a bunch of R stuff (not baked in, just how things are)
** will be pushing wrapping logic up
** port names forbidden (window and domain)
** have an import hook to get from yaml directly to VisTrails Modules
** should work for any python modules with well-formed numpy docstrings.
* [Action] should make it clear in documentation that Constant now means serializable not that the value doesn't change (e.g. List)
* [TC] might be interesting to try to build components of matplotlib and accumulate in figure (long-term project, but thinking about how this might work)
* [TE] build and build scripts
** completely automatic, buildbot
** need to set the build machines for the environment we want for the binary
** would virtualenv work here?
** [TC] anaconda can pin versions, potential path to test different configurations
** Q: upload nightly binary builds? A: makes sense, make sure they are well-labeled
* sourceforge stats: e.g. http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07
* package issues (see Remi's message)
* [TE] Scope of tej
** Support single ssh commands?
** Queue can be used as a remote machine (crawler is using queue.call*)
* SourceForge stats: http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07

== Older meetings ==
* [[Development/2014]]
* [[Development/2013]]
* [[Development/2012]]
* [[Development/2011]]
* [[Development/2010]]

Development

2016-07-20T15:00:58Z

Tommy: /* July 20, 2016 */

<div class="nonumtoc toclimit-1">
__TOC__
</div>

See also the [https://github.com/VisTrails/VisTrails/wiki/Development Github wiki]

== 2016 ==

=== July 20, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] New patch method for python-wrapper [https://gist.github.com/rexissimus/009b303e4cadcd4b8f2fec6cf848cb2b example]
** A patch is a string template with self/input/output variables for patching a class method
** Patches are stored in xml specification
** Patches are assigned to methods in ClassSpec's
** Used both for execution in vistrails and when exporting as script
*** Executed with "exec" when run in vistrails
*** Turns patches into natural calls in script
** Wrapping VTK library no longer needed
*** Removes ".vtkInstance" (Automatically removed from PythonSources and vtkInteractionHandlers)
** Removed fix_classes.py (Subclassing of VTK classes to patch methods directly)
** Also used for port translations (With patch names like "basic:Color#input") (No more ugly input_t method definitions)
** TODO's
*** Add to export_as_script
*** Patch Modules that represent Python functions as well

* [vistrails-users] Read data from SQL example?

=== July 13, 2016 ===

'''Updates'''

* [DK] bundles on sql-alchemy branch
** Bundle, BundleMapping, and BundleSerializer
** New BaseSerializers to deal with versions of directory, zip, db serializers
** Can register the BundleSerializers with the base serializers
** Translation between bundle versions
** Bundle.add_object "just works" if an appropriate mapping was registered

'''Items to Discuss'''
* [TE] Simplified running module using API for scripting [https://gist.github.com/rexissimus/b28d83ae516a519167f5751bb8ab3739 example]
** API Module can be executed using '''compute''' method
*** Takes list of outputs to compute + inputs as keyword arguments
* Status of general cell synchronization (vistrails-users)

=== July 6, 2016 ===

'''Updates'''

* [DK] Working on bundles

'''Items to Discuss'''
* [TE] Using vistrails API in scripting [https://gist.github.com/rexissimus/034d9c4dedc3299a079e84981dedd8c7 example 1 (API with VTK)] [https://gist.github.com/rexissimus/a4a9ca6c08d4058c64967d2b35415fd5 example 2 (DownloadFile only)]
** Call module in script using vistrails API
** Can be used when no export method is defined.
* [TE] [https://github.com/VisTrails/VisTrails/commit/c76c109349769fee1280f85c22678380a2f9cd39 Server news bug] Critical?
**[RR] No, unreleased
* [DK] New bundle organization
** BundleMapping contains individual mappings from raw objects to BundleObj
** Must be separate in order to have in-memory, separate from serializer settings

=== June 29, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Export VTK as python script
** Works on Terminator (Isosurface, Volume Rendering, clipping plane, combined rendering) [https://gist.github.com/rexissimus/16caf5200802e150296f62a0c7844c5a example]
** Preludes (imports) still need improvements
** Works with vtkInteractionHandler (clipping plane)
** Resulting clipping plane is incorrect? (supposed to hide one side of the plane)
** vtkRendererOutput Uses VTKRenderWindow as output
*** Should support different output modes?
*** Does not work with multiple outputs (Next cell is displayed when current is closed)
*** Uses wrapped vtkInstance (as vvtk)
**** Create new patch system with code that can be used both in vistrails and in a python script?

=== June 22, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Fix for upgraded analogies (PR [https://github.com/VisTrails/VisTrails/pull/1177 #1177])
** Uses module location to find module remap (The best we can do right now?)
** Also fixes remapped port names for connections to existing modules
** May still fail on complex upgrades like adding a function on an upgraded module that has a different port name

* [TE] Working on exporting wrapped libraries (VTK)

=== June 15, 2016 ===

'''Updates'''
* [TE] Added depth logic to python script exporter ([https://github.com/VisTrails/VisTrails/commit/50f220e4f6abe5a7bb8689f73f456f43df2dbc12 full commit])
** Fully implements connection merging and list looping

'''Items to Discuss'''

* [TE] Making analogy work on upgraded workflows ([https://github.com/VisTrails/VisTrails/issues/1175 #1175])
** Analogy only works We need to use the non-upgraded action chain
** But pipelines need to be valid (matcher uses module portspecs)
** Tried to get upgrade remap from upgrade action, but this seems impossible
** Use module location instead?
*** Location should be identical for one-to-one module upgrades

=== June 1, 2016 ===

'''Updates'''
* VisTrails 2.2.4 announced (finally)
** 5 survey replies
** 47 downloads last week

'''Items to Discuss'''
* [TE] Export VTK as script (python-wrapper)
** to_python_script
*** needs the pipeline (or at least the connections)
**** Should not generate code for any possible VTK method (exporter detects which ports is used in the source)
**** VTK needs to know connection order
**** Adding functions directly to the script results in nicer code
** Add support for multiple input connections
** Add support for list looping

=== May 25, 2016 ===

'''Updates'''
* Mailing-list fixed
* Getting stats from the "server news" mechanism (via [https://github.com/remram44/apache-log-info parser])

'''Items to Discuss'''
* [RR] Alexis doing writeup on VisTrails, curious about interesting streaming use-cases (and potential future users)
* [TE] Union ports
** Show union ports in pipeline (DEMO)

=== May 18, 2016 ===

'''Items to Discuss'''
* [TE] mailing list still down - Julio working on it
* [TE] Improved union port
** New schema 1.0.5 adds portitem.union string attribute
** Works with pipeline view, parameter exploration view, and mashup view
** Should work well for matplotlib
** Use with VTK ports?
*** It uses [item_1,item_2] style ports usually with different tuple length.
* [TE] Remove emacs dependency from db generate [https://github.com/VisTrails/VisTrails/issues/1173 #1173]

=== May 11, 2016 ===

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]
** GUI-based solution [https://github.com/VisTrails/VisTrails/tree/union-port Branch union-port] Demo?
*** Shows single port for all ports with same sort_key
*** Select specific type when adding/showing
*** Only one type should be visible on the module at any time
*** Making tuple parameters union types is probably too complicated
*** Should work with alternate specs like matplotlib (if sort_key is defined correctly)

* [TE] Feature suggestion: Let connections connect to functions/parameters
** Show functions and parameters as ports and toggle port visibility directly for functions and parameters
** Use separate views for ports and functions (like before)
*** Allow rearranging of functions
** Pros:
*** Supports ordered connections. Create 2 functions, make them visible as ports, make connections to them.
**** We can also have, e.g., a line joining the ports on the module to indicate they are part of a list.
**** Makes List module simpler
*** Connect to parameter in tuple
*** Functions that are visible on the module can connect to an actual function, and not just to the first one it finds.
*** Can replace operation modules (in python-wrapper) in some cases for, e.g., numpy.
** Cons:
*** Interface more complicated and crowded
*** More difficult for users to grasp?
*** No immediate use case
*** Makes no union type for tuple parameters a bigger problem.

* [TE] Publish user survey?
** No response from vistrails release yet
** Not announced on vistrails-users yet.

=== May 4, 2016 ===
'''Updates'''
* VisTrails 2.2.4 released

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]

=== April 27, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Wrapping Bokeh
** New method type "operation"
*** Transforms Figure->Glyph->Output into Glyph->Figure->Output
**** Glyph sets function name and arguments as output
***** Not serializable, but should always be computed together with the subject of the operation.
**** Figure applies Glyph operation on itself
*** Useful for matplotlib?
**** matplotlib currently find actors by searching upstream?
**** But this is more difficult since matplotlib is not function-based.
** New "union" port type
*** Turns "x(float), x(list)" into "x (float, list)" and uses first set value
**** Uses only first value in tuple
**** Bokeh have many properties that support (list, string, Float)
*** Does not work with depth=1 types (e.g. Float of depth 1)
**** Turn Depth 1 types with known type into lists?

* [TE] New bugfix release
** Finalize survey

=== April 20, 2016 ===
'''Updates'''
* Merged upgrade fixes
** Now has infinite loop test
** loop test now correctly loops 5 times
*** remap_module used wrong (current) package version when creating ModuleDescriptor
* Fixed multi-step group upgrades (PR: [https://github.com/VisTrails/VisTrails/issues/1168 #1168])

'''Items to Discuss'''
* New bugfix release
** Merge usagestats
** Need to finalize survey

=== April 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Chaining upgrades done ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Replace "Upgrade" description annotation with "upgraded_from" annotation to identify which tags to hide?

* [TE] Iterating handle_invalid_pipeline ([https://github.com/VisTrails/VisTrails/pull/1165 #1165])
** Not based on [https://github.com/VisTrails/VisTrails/tree/chain-upgrades-loop chain-upgrades-loop]
** Cherry-pick test to preserve source?
** Need maxPipelineFixAttempts option?
*** The code is now smarter about recursion, so max attempts will "probably" never be reached.
** Need [https://github.com/VisTrails/VisTrails/commit/0ef0667426937eddb1d1c1e397f0657ffec039a9 debug messages]?
*** Would need to be moved into handle_invalid_pipeline

=== April 6, 2016 ===
'''Updates'''
* [TE] Query View improvements
** Done except for displaying "Version Info" and #1164
* [RR] Working on finishing new interpreter (finally!)

'''Items to Discuss'''
* [TE] Chaining upgrades ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Try latest upgrade first, then previous.
** If all fail, select latest upgrade?

=== March 30, 2016 ===
'''Updates'''

'''Items to Discuss'''

* [TE] Query View improvements
** Unified do_version_switch and get_upgrades as validate_version()
** Problems with query view using its own controller
*** Fixed module info not being displayed for query results
*** Still no version info for query results
*** Still an issue with version query view not being updated

=== March 23, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Usage reporting almost ready to go
** Need to record whether specific features are used: paramexpore, mashup, query
*** [DK] Record if LaTeX extension is used? But hard to distinguish from direct batch invocation
** How to record size of vistrail?
*** [DK] IdScope already walks over vistrail, use that
*** but total number of modules and versions doesn't give an idea of average size of individual pipelines

=== March 16, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Upgrades in Query Mode
** Now using code similar to do_version_switch
*** Uses handle_invalid_pipeline
*** Differences: Not using current_pipeline, flushes changes
*** New controller method get_pipeline optimized using cached pipelines (but not current_pipeline)
*** Integrate to avoid repeated code?
*** Use this for query mode?
* [TE] VisTrails 2.2.4 ready for release?
** tej package updated. Others?
* [JF] upgrades and the version tree
* [JF] provenance in Jupyter
* [DK] bundles: [https://github.com/VisTrails/VisTrails/pull/1092 #1092]

=== March 9, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixing search mode
** String query now matches all by default
*** This caused pipeline queries to never match
** String query can search: User/Notes/Tagname/Time/Module name
*** Should we search module names by default? (Disabled by default because it is expensive)
*** Fixed notes search
** '>' parameter queries in documentation but has been removed
** Fixed module matches for upgraded pipelines (By not upgrading pipeline)
*** Upgrades still a problem
*** Add "Upgrade all menu option?" (Or upgrade all on open when `hideUpgrades`)
*** [JF] Allow search on past tags

* [TE] Create new bugfix release
** Finish querying
** Path issue on windows

* [DK] Look into sqlalchemy and new bundle branches

=== March 2, 2016 ===
'''Updates'''
* [TE] Fixed cache bug with port specs
* [TE] VisTrails Next
** Most packages now work
** No qgis for Python 3

'''Items to Discuss'''
** Always dereference symlinks? [https://github.com/VisTrails/VisTrails/issues/1146 #1146]

=== February 23, 2016 ===
'''Updates'''
* [TE] Fixed PythonSource 100% CPU bug
* [TE] VisTrails Next
** Updated [http://opendap.co-ops.nos.noaa.gov/axis/webservices/wind/ NOAA Web Service] examples
*** Now uses REST service, tabledata, and Google Maps
*** Web Service replaced with DownloadFile

'''Items to Discuss'''
* [RR] Couple of fixes are in for API, and tej&reprounzip on the Mac binary. Also new release of tej, and working on anonymous usage reports.
** New 2.2 release soon?
* [RR] Anonymous usage reports
** Sends out info like number of modules & versions, packages used, Python & libs versions, execution time, specific features [https://github.com/VisTrails/VisTrails/pull/1154 #1154]
* [JF] Bring in noWorkflow to track variable dependencies, for the considered Jupyter integration?
* noWorkflow - provenance for python scripts
** Recent work on tracking dependencies
* Also integrates ReproZip with Jupyter
** [http://mybinder.org mybinder]
*** Use with ReproZip to automatically build Jupyter notebook interfaces
* Daves comments on Jupyter integration
** It is possible to identify cell order on the server side
** Not trivial to track order of cells on client side
* How does Galaxy workflows relate to VisTrails?
** Packaging in Galaxy is hard
** Galaxy for biomedical workflows, difficulty making it general
* Action items
** How difficult to track cell dependencies in Jupyter notebooks?
** Use noWorkflow to track cell dependencies?
** How difficult to modify mybinder to use ReproZip packages?

=== February 17, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixed Group memory usage
** Modules in groups are supposed to be freed when done executing
*** Prevented by logger that stored references to the modules (fixed, now using id(module))
*** Prevented by list iterator bug that stored list of modules on the 'self' port bug (fixed)
* [TE] VisTrails Next
** Removed deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** PythonSources will be upgraded
*** Fixes for Python < 3
*** fixes for VTK < 6
** TODOs
*** Remove RemoteQ
**** Port Hadoop to tej (Already have pbs)
*** Merge package wrapper
*** Finish SQLAlchemy branch
*** Finish new bundle branch
** [JF] Will contact Jeff and Matthias about moving to Python 3
* [JF] Query by Example is broken
* [JF] VisTrails Data Cleaning Project
** Use VisTrails to process and explore task-specific data while keeping provenance.
** Remi's Idea
*** Use VisTrails as the backend in a Jupyter notebook
*** Overcome problems with executing cells in random order
**** Interesting research topic, but little interest has yet been noted
*** Interesting to study how such a notebook would be used (Is there notebook usage data available?)
*** Impose restrictions to notebook cell boundaries
*** It will only work for functional operations
*** Can we fix, or detect, non-functional (mutating) operations?
*** Analyse code and data flow and see if it mutates data in unexpected ways?
*** Mutable operations can be created in many ways in Python
* Next meeting Tuesday 11:30

=== February 10, 2016 ===
'''Updates'''

'''Items to Discuss'''
* VisTrails Next
** Test suite passes
*** Python 3 less deterministic, module upgrade order random.
** [RR] updating packages: Reprounzip (pushed), tej, persistent_archive, ...
** All of our packages should run fine :)
** VTK thumbnail comparison works
*** Rendering bug on some systems
**** QVTKCell now inherits QGLWidget
*** Old thumbnails had wrong height due to spreadsheetwindow being too small
**** Fixed by regenerating thumbnails
*** Silenced deprecation messages when generating modules
*** Many new classes in VTK 7
** Remove deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** Will break existing PythonSources
**** Try to upgrade?
*** Old-style packages
**** Or only allow a new style, like __init__.py renamed to info.py? (merge with identifiers.py?)
***** Read info.py without importing package?
*** Fixes for Python < 3
*** Fixes for Qt < 5
*** fixes for VTK < 7
*** Remove self port?

=== February 3, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] [http://lists.vistrails.org/pipermail/vistrails-users/2016-January/000402.html Rendering a .pvd (ParaView) file?]

* VisTrails Next
** All tests but thumbnail comparison passes
** Still issues with gui and more packages needs to be tested
** PythonSource and MplSource upgraded with lib2to3
** Keep contrib packages? Update?
** [https://blog.kitware.com/vtk-7-0-0/ VTK 7 is released]
*** Supports Python 3
*** Will hopefully get into conda and others soon
*** Deprecates a bunch of modules

* [https://travis-ci.org/VisTrails/VisTrails/builds/106743348 Travis builder] for VisTrails Next
** Runs!
** Uses conda
*** Many levels of requirements
**** apt packages
**** conda packages
**** python packages in requirements.txt
**** python packages in setup.py
*** Can probably drop conda. Default builder does not have Qt5, but beta builder do!
*** But useful if we want to use conda in our own build process.
** Lots of errors I do not get locally?

* [http://goo.gl/forms/Z4HBrwaBWL User Survey]
** Have you used any alternatives to vistrails?
*** Relevant? More options?
** How often do you use any of these particular features in VisTrails?
*** Add/Remove alternatives?
** How important would you rank the following potential improvements to VisTrails?
*** Add alternatives?

=== January 27, 2016 ===
'''Updates'''
* New interpreter
** Working prototype soon
** Looping not completely done (and port combination mode: pairwise/cartesian...)
** Need to integrate with VisTrails
*** Compatibility with existing modules
*** Use log controller
*** Want to cache at multiple levels (whole stream/single element of stream)
*** Non-runtime attributes of modules (cache check, automatic conversion check, constant from/to string)

'''Items to Discuss'''
* User Survey

* ZMQ failing on windows (vistrails-users)

* [TE] [https://github.com/VisTrails/VisTrails/pull/1143 Python 3 branch]
** Testsuite almost passes
*** Failing are unicode filenames, some users guide examples, and thumbnail comparisons.
** Fixed issues
*** Signatures are now bytes (convert to string to show in widget)
*** Cannot compare different types, e.g., (None < 1)
**** PortSpec.depth and min/maxConn could be None. (Backport!)
**** cell.row could be None
*** Lots of unicode/bytes fixes to serializations
**** We have encryption implementations in the code! (keychain)
*** Lots of small fixes to package method differences
** Current issues
*** logging widget empty?
*** version tree signals messed up
*** provenance view legend icons black
*** Text do not fit in some widgets
*** VTK thumbnail comparison fails
**** VTK Cells have some faces in wrong direction?
**** Because running in VM?
** Installing on Ubuntu LTS/Latest Mint
*** Install latest matplotlib from pip
*** Install VTK 7.0.0rc2 from source
*** No QtWebEngine binary (controversial) (Must install sip/PyQt5/Qt5 from source)

=== January 20, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Backporting features from Python 3 + PyQt5 + Qt5
** Merged unicode with master ([https://github.com/VisTrails/VisTrails/tree/unicode unicode])
*** One unicode test failing
*** Problem saving to xml
** Used [http://python-future.org/ python-future] to run futurize stage 1 to update legacy (pre 2.6) code ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized unicode-futurized])
*** Updates print to functions 'from __future__ import print_function'
*** Updates exception calls to use 'as'
*** removes most usages of 'long' (mostly used unnecessarily)
**** Only needed for 32-bit support
*** Fixes relative imports (from __future__ import absolute_import)
** Fixing code that is deprecated in Qt 4.8 and removed in Qt 5 ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized-qt5 unicode-futurized-qt5])
*** Updated all signals to new-style
* If we go 2 to 3, this could break packages
** means we should schedule any package format changes for the same time
** e.g., imports should be unrelated to code path (function to load module from package identifier?) (take them out of vistrails.* [https://github.com/VisTrails/VisTrails/pull/1002 #1002])
** any structural changes (e.g. the __init__ versus init thing) (RR thinks it makes sense, though having both named "init" is unfortunate)
** putting package identifier as xml?
*** Python not so bad, plus some stuff in there is Python code (checking dependencies)
** version the APIs?
*** RR planning on versioning vistrails_module.Module, no point versioning the whole package?
* file formats on 2 to 3:
** no real translation/upgrade, but non-ascii values that work on 3 won't load in 2

=== January 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://gist.github.com/rexissimus/dfd27e466427529c385c Porting to Python 3 / PyQt5]
** Basic GUI and execution works
** Minimal work to support 2to3
** Hard to support both PyQt4 and PyQt5

=== January 6, 2016 ===
'''Updates'''
'''Items to Discuss'''
* Updating VisTrails dependencies
** Successfully built [https://gist.github.com/rexissimus/f1a1aada7de1c00a57c7 Win7-64/Python3/PyQt5/Qt5/WebEngine/VTK7]
*** VTK 7 is the first supporting Python 3 but is only in release candidate phase.
**** Next version of VTK 6 is rumored to support Python 3
**** There is a development branch of VTK 6 supporting Python 3
*** Can travis build this?
**** We can skip tests for WebEngine and VTK if needed
** Python 3 [https://python3wos.appspot.com/ showstoppers]
*** No MySQL-python (sqlalchemy supports mysql through other drivers)
*** No suds (there are active forks but we could also drop support?)
* Options for python2/3 support:
** Interpreter could be python2/python3 based on packages
** six layer works but not the easiest to maintain (e.g. in reprozip)
* Drop support for win-64
* Update copyright headers to 2016

== 2015 ==

=== December 30, 2015 ===
'''Updates'''
* Bokeh package finished
** Can output to Browser/IPython/Spreadsheet (Limited functionality in spreadsheet)
'''Items to Discuss'''
* Updating VisTrails dependencies
** Bokeh needs QWebEngine (Chromium) in Qt5 which requires PyQt5
*** Many plotting libraries only work in browsers
*** But Chromium may be a big and controversial dependency
*** Or create a browser version of the spreadsheet?
** Some users have requested Python 3
** Not backwards compatible?
** Target for VisTrails 3.0 with new interpreter?

=== December 16, 2015 ===
'''Updates'''
'''Items to Discuss'''
* Users list question
* [TE] Wrapping Bokeh
** Added bokeh property parser
*** complements numpydoc parser
*** Not all attributes are available, partially because I am using a pre-release version.
** Wrapped modules
*** bokeh.plotting finished (Backwards like matplotlib: Create plot then draw on it)
*** bokeh.charts mostly done (Missing arguments)
** QWebView mostly works (but no zooming or buttons)
*** It would be better to use external browser or QWebEngineView
** Added improvements to wrapper
*** Generalized port translations (Color/Path to native types)
*** Can use multiple docstring/property parsers simultaneously

=== December 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Looking into wrapper
** Will port TensorFlow
** Doing a pass on the wrapper code & doc
*** UX improvements
** Factorize high-level docstring parsers into core.wrapper? (sphinx, numpy, google)
** Problem with name vs module_name (fails sklearn tests because class_by_name() is broken)
** Looking into compressing specs, lazy registration of modules

=== December 2, 2015 ===
'''Updates'''
* [TE] Package wrapping
** Wrapped most of numpy/scipy using __all__
** Added class attribute and method access for classes (Can add to class or to separate inspector module)
** TODO: Document wrapping procedure

'''Items to Discuss'''

=== November 25, 2015 ===
'''Updates'''
* [RR] New interpreter is coming along
** Everything is a stream
** Task system, eventually work-stealing parallelism
** Streams no longer advance in lock-step
*** Allows for constructions like filter, join, sorted-merge
** depth>1 still to be tested, no current plan to allow this through the module interface
*** Through looping though, can do streams of streams

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapped most numpy functions (no polynomials)
** and half of scipy classes and functions
** Added functions manually from documentation (no parseable lists?)
** Focusing on data flow constructs (no property/method access for classes)
*** Using spec diff (empty for now) and dynamic parser (stores spec in .vistrails/)
** Python class/function wrapper now stable
** Add google doc parser?
*** Is there a parser available?

=== November 18, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Numpy class wrapping works
*** Basic type is List, since most types are array_likes.
*** TODO: More classes and functions
*** Some operations are in-place and some aren't, and docstring not super clear
*** [RR] It seems only methods mutate, and most have a numpy.xx function equivalent; just manually go through the methods and remove the mutating ones?
** Class wrapper is modular
*** Docstring parser and type string parser can be customized
*** Classes can have optional attribute/method ports
**** Inspectors and attribute/method modules can be created separately
** Use PythonCalc as an example
*** Can be re-implemented as a function with a parseable docstring
*** [RR] PythonCalc is just an example, and it might actually make sense to get rid of it, or do a proper math package with scalar operations (as separate modules, no combobox)
** [RR] TensorFlow to use wrapping as well
*** Very simple (only types 'tensor' & 'variable')

=== November 11, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapping numpy's classes using numpydoc (ndarray)
*** Wrapping constructor arguments, attribute getters/setters as module ports
**** Then how to access attributes afterwards?
***** Use input value port to class modules?
*** Wrap methods as modules? E.g., `ndarray.shape`.
*** Function wrapping is almost a subset of class wrapping
**** May be able to use the same parsing/execution methods
** VTK's non-getter/setter methods could be wrapped as modules
*** We could then remove extra logic in interpreter for keeping function order
** Bokeh uses autogenerated docstrings
*** We may be able to read the specification directly

* [RR] [https://github.com/VisTrails/VisTrails/pull/1138 TensorFlow package]
** Basic setup working, can execute the Mandelbrot example
** Will autogenerate the operations

=== November 4, 2015 ===
'''Updates'''
* [RR] Interpreter work requires a fix for [https://github.com/VisTrails/VisTrails/issues/1137 DB issue #1137]
* [DK] Kitware's Resonant [http://www.kitware.com/source/home/post/173]
** [https://github.com/girder/girder Girder]: data management system
** [https://github.com/Kitware/romanesco Romanesco]: execution engine, uses [http://www.celeryproject.org/ Celery] for task management
** Resonant Flow: web app for editing and executing workflows

'''Items to Discuss'''
* [TE] Added OSX Lion (10.7) VM on build machine using vagrant (seems ok with license?)
** New builds works on Lion
** Change the minimum requirement to 10.7?
* [TE] Package wrapping
* Added upgrade suggestions using 2 spec versions ([http://pastebin.com/30XUU8Gp example])
** using name edit distance to find matches
** Could use something better like port similarity for modules, and type similarity for ports
** Should write python upgrade code?
** Added spec to sklearn package
*** Can now diff spec versions and keep the spec static
*** There will be problems with downgrades and package versions

=== October 29, 2015 ===
'''Updates'''
* [TE] nightly-build-mac fixed (Needed to approve xcode license)

'''Items to Discuss'''
* [TE] matplotlib wrapper
** ported to general spec
** Diff can be used on general spec
*** Only needed minor changes
*** Fixed indexing bug that corrupted specs
*** Can now move diff tools to core/wrapper
** Add new plots?
*** New plots in mpl 1.3: eventplot
*** New plots in mpl 1.4: angle_spectrum, magnitude_spectrum, phase_spectrum', violinplot
*** No new plots in mpl 1.5 (from looking at boilerplate.py)

=== October 21, 2015 ===
'''Updates'''
* [RR] Alexis has arrived, will be working with [RR] on a more efficient interpreter

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package]
** Supporting multiple package versions
*** Check which version can be loaded [https://github.com/VisTrails/VisTrails/pull/1135 #1135]
*** We cannot show version requirements in the list of packages because old packages are loaded when importing the codepath
** Visual diff does not work well, but we can use the spec differ to see differences.
** Unifying vtk and matplotlib wrapping specs (WIP)
*** And porting matplotlibs spec differ to work on the general spec
*** Spec differ can then be used on vtk and other packages in the future
*** Will enable automatic upgrade generation
* [RR] Rework interpreter
** restore abstraction between interpreter/module code
** build looping, streaming, caching into the interpreter
** rework cache
** look into parallelism once basic functionality is there

=== October 14, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package] (adding numpydoc parser)

=== October 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/tree/fix-matplotlib-parser New matplotlib parser] (adding numpydoc parser)
** Added numpydoc attribute parser for plots.
*** TODO: Need better port spec reconciliation with call signature parser.
*** We can create a general numpydoc parser, but attribute types are unique to matplotlib.
** Needs package versioning
*** New spec will not support matplotlib < v1.4 due to changed path to axes classes.
*** Load spec version corresponding to installed matplotlib version?
*** Need version downgrades?

=== September 30, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Updating Matplotlib parser
** Matplotlib docstring parser fails on numpy docstrings
** I have [https://github.com/VisTrails/VisTrails/commit/eae8b0c16260810587e47c41cab53552cbb3cf0a added basic numpydoc parsing]
*** Only used by a few docstrings so far
*** Parsing uses many sources (class tables, signatures, ACCEPTS, method docstrings, definition parsing).
** Caswell said they were thinking about moving to traitlets, but this is not ready yet

=== September 23, 2015 ===
'''Updates'''
* [TE] VisTrails 2.2.3 released
** Also have pushed to PyPI, binstar, etc.
** Sourceforge vs. GitHub
*** should be able to host releases on GitHub
*** nightly binaries pushed to sf each night
*** old binaries?
* [TE] Re-wrapping MatPlotlib
** Keep static generation - Docstrings are brittle beween matplotlib versions
** Keep generating the executable classes - but create functions, not vistrails Modules
*** Why is there so much patching?
** Re-implemented Alternate PortSpec for InputPortSpec
*** It will now inherit specs from parent (No need to reimplement)
** Module upgrades?

'''Items to Discuss'''

=== September 16, 2015 ===
'''Updates'''
* [TE] Job Monitor tests and documentation done
** OK to leave document package in packages directory?

'''Items to Discuss'''
* [TE] Library wrapping: How to do code patching? [https://docs.google.com/drawings/d/1Sh3eOXot6v2y880jHKQrqXqAwr-0aoqYligg3z8G8MY/edit?usp=sharing Wrapping diagram]
** Insert code into module template (Old VTK code)
** Patch the library that is called (New VTK code)
** Somehow store code in spec and apply when executed?
*** Executed code needs at a minimum access to inputs, outputs, current class
*** Use standard input/output dict and obj reference that the code operates on?
*** Can this be done while keeping the execution abstract?

* Do new release now?

=== September 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* New release?
** [RR] wants reprounzip
** tej changes & doc
** job monitor & jobmixin fixes
** mongodb
** reprounzip
** warning: MplFigure type is int
** tabledata: add Reshape, DictoToTable & ListToTable, fix ListToTable with numpy arrays
** PythonSource can have same name for an input & output
** don't show spreadsheet at exit

=== September 2, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Limit autosaves? [https://github.com/VisTrails/VisTrails/pull/1126 #1126]

=== August 26, 2015 ===
'''Updates'''
* [TE] Added Job support to Parameter Explorations (Requested by Colin), and Mashups
** specify job ids, need to specify different ids for parameter explorations since they have the same version id
** how to deal with parameters passed in on command line
* [General] provenance: should be creating a new version when we execute workflow with changed parameters?
** currently, custom_params annotation stores this in provenance currently
** [RR] API doesn't record provenance if passing in parameters: http://git.io/vsAA5
'''Items to Discuss'''

=== August 19, 2015 ===
'''Updates'''
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [TE] Working on Job Monitor documentation

'''Items to Discuss'''
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [TE] Stop testing VisTrails 2.0?

=== August 12, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Build broken on Travis; because of IPython 4 released today? ([https://travis-ci.org/VisTrails/VisTrails/builds/75279795 build 992]; [https://github.com/VisTrails/VisTrails/issues/1123 #1123])

=== August 5, 2015 ===
'''Updates'''
* [TE] Fixes to Jobs
** Could not delete jobs
** Could not run job in group
** Job not reset when calling ModuleSuspended
** Added deleting job from context menu
* [RR] Writing documentation for everything [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

'''Items to Discuss'''

=== July 29, 2015 ===
'''Updates'''
* RR still looking into new interpreter thing
** Goal is to take out scheduling logic from Module so it can be split in multiple processes, and so that smarter strategies can be added in time
** This means some work on packages
** Spreadsheet can live in kernel process? Still some UI stuff that will take work (changing configuration, persistent archive's viewer, ...)
* [TE] Problems running examples [https://github.com/VisTrails/VisTrails/pull/1111 #1111]
** Testing of more examples requires additional packages on the test machines.
** Fixed faulty line-ending in PythonSource:s failing on Python 2.6.
** Test suite now testing SUDSWebServices (If web service is down, test suite will fail)
** preferences.py test failed reloading 'dialogs' package, switched to using 'URL'.

'''Items to Discuss'''

=== July 22, 2015 ===
'''Updates'''
* [TE] mailing lists back online
* [TE] Working on [https://github.com/VisTrails/VisTrails/issues/1107 #1107]
* [RR] Working on ReproZip package

'''Items to Discuss'''
* [RR] MongoDB package [https://github.com/VisTrails/VisTrails/pull/1106 #1106]
* [RR] Example for tej docs? [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

=== July 15, 2015 ===
'''Updates'''
* 2.2.2 released

'''Items to Discuss'''
* RR is considering executing everything in an IPython kernel (i.e. separate Python interpreter, like the one spawned for a notebook)
** It's a separate process that we can restart without restarting the app/gui
** We can isolate the execution environment (e.g. for the server)
** We can run the whole thing remotely (if your data is elsewhere, just run VisTrails locally and the pipeline elsewhere)
** Pipeline execution no longer makes the interface hang, it just makes the kernel hang (but that's fine)
** We can use notebooks as modules (probably way nicer than the PythonSource module)
** We can run multiple kernels so long as the ports carry things that are serializable
*** meaning we can put the multithreaded-interpreter without all the hacky parts it has now
*** we can run IPython kernels in all the languages IPython supports, [https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages currently 46]

=== July 8, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Buildbot github hook not working after IP address change
* [TE] No reference to VistrailsApplication ([https://github.com/VisTrails/VisTrails/issues/1103 #1103])
** [RR] Added PR [https://github.com/VisTrails/VisTrails/pull/1104 #1104]
* [TE] Reopening VT file after saving with bundled subworkflow won't offer subworkflow upgrade ([https://github.com/VisTrails/VisTrails/issues/1102 #1102])
** allow manual delete to fix right now
** fix this on top of the use-uuid branch
* [TE] Release VisTrails 2.2.1? ([https://github.com/VisTrails/VisTrails/blob/v2.2/CHANGELOG CHANGELOG])
** [https://github.com/VisTrails/VisTrails/pull/1093 output-modules-use-global-dir]
** [https://github.com/VisTrails/VisTrails/milestones/version%202.2 Current issues for 2.2]

=== July 1, 2015 ===
'''Updates'''
* [TE] PROV fixed
* [TE] Working on subworkflow issues
* [RR] Considering reworking the controller (log vs exception problem, retained upgrades causing interferences) and also the interpreter (IPython?)

'''Items to Discuss'''

=== June 24, 2015 ===
'''Updates'''

'''Items to Discuss'''
* UV-CDAT
* [TE] Can a cyclic workflow be valid? ([https://github.com/VisTrails/VisTrails/issues/1097 #1097])
** focus on disabling the ability to create cyclic pipelines because more things break than just this with a cyclic pipeline
* [RR] Relative paths ([https://github.com/VisTrails/VisTrails/pull/1057 #1057])
** This interacts with the new bundle; how do handle packing files inside the VT bundle?

=== June 17, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] current_version and reusing existing upgrades are broken ([https://github.com/VisTrails/VisTrails/issues/1095 ticket #1095])
** Could be that export to PROV is using an unflushed upgrade pipeline?
** current_version would then be correct.
** It may work to flush the actions before exporting?

=== June 10, 2015 ===
'''Updates'''
* DAT: fixed VTK issue on Linux and Mac
* Still crashes on Windows. Need help! Reminder: this works in the VisTrails spreadsheet (QCellPresenter), although no widget get changed there during a drag
** Is it a VTK bug?
** Is it simply impossible to change widgets during the drag, should we do it a different way?
** Did I miss something that is done in VisTrails but somehow not in DAT?
** Low prio, UV-CDAT doesn't run on Windows anyway

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 Updated pull request])
* Single instance code and batch mode

=== June 3, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 pr])
** Requires fixes to command line parameters, Output modules, and batch mode
** How to test this
** Updated missing/outdated flags
** Fixed view issues when generating graphs
* [TE] batch mode
** SpreadsheetOutput not enabled in batch mode. Should we check is_running_gui instead?
** Other instance setting flags from caller
** Is graphsAsPdf replacing spreadsheetDumpPdf?
** graphsAsPdf true by Default?
** Batch mode executing by default (Not needed when generating graphs)
** Re-added workflowInfo as withWorkflowInfo for writing graph and xml workflow
** [DK] batch mode should be outputting to files or stdout, shouldn't always trigger SpreadsheetMode
** execute flag, maybe make execution the default and allow a "--no-execute" if you only want to capture graphs, for example

=== May 27, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] API question
** http://lists.vistrails.org/pipermail/vistrails-users/2015-May/000357.html
* Status of DAT
** Can add VCS plot to DAT but need to work on configuration windows
** Documentation for graphics templates for UV-CDAT/vcs?
* Qt support?

=== May 20, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Reviving the DAT, integrating scripting & porting UV-CDAT!
** On [https://github.com/VisTrails/DAT GitHub] ([https://github.com/VisTrails/DAT/issues issues])
** Merging 2 years of development taking longer than expected, but getting there. The plan is to get the patches in VisTrails and never fork again, we never want to get in UV-CDAT's situation (and don't need to).
** VTK cell works fine on Linux but there was flickering on Mac & Windows before; still issues on Mac (Windows status unknown)
** Can get a VCS plot soon (but will need VTK cell fix)
** Integrate in UV-CDAT's build system (so we have cdms, VCS, ...) -> RR can do this, low priority
** How do we integrate scripting?
*** We want to be able to seamlessly make changes to a plot by changing Python code
*** Define new plots by entering Python code without writing modules/packages?
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 13, 2015 ===
'''Updates'''
* [RR] Test skipping whitelist ([https://github.com/VisTrails/VisTrails/pull/1069 #1069]) -- low priority
* [RR] Custom matplotlib modules can't be compatible with both 2.1 and 2.2 ([https://github.com/VisTrails/VisTrails/issues/1067 #1067]); should be fixed for ALPS ([https://github.com/VisTrails/VisTrails/issues/1070 #1070])

'''Items to Discuss'''
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 7, 2015 ===
'''Updates'''
* [RR] Export/import workflow to Python working!

'''Items to Discuss'''
* [Claudio] UV-CDAT
** The UV-CDAT project is the biggest user base of VisTrails
** VisTrails package management provides a lot of friction towards people plugging in their code
** Need to make it easy to integrate your random Python scripts in the system without having to deal with all the boilerplate, at least in the first step
** [RR] argues that modules are still good; UV-CDAT shouldn't move towards a purely script-based backend
** [RR] export/import with Python could reduce a lot of that friction by allowing 1) to edit workflow as Python 2) to open up boxes automatically if needed code doesn't match actual modules
** ...

=== April 29, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] <strike>Abstractions</strike> subworkflows status ([https://github.com/VisTrails/VisTrails/labels/subworkflows tickets])
* [RR] matplotlib compatibility (2.1 & 2.2), [https://github.com/VisTrails/VisTrails/issues/1067 #1067]
** RR to try and fix ALPS matplotlib modules

=== April 22, 2015 ===
'''Updates'''
* 2.2.0 has been released!
* Windows issue (via email from Ryan)
** issue with manifest file (may be a new file in VTK6?)
** Tommy has regenerated new Windows builds
* Binaries, pypi, and conda released
* [RR] Export as script
* Python sources using VTK need to switch to SetInputData (users should be aware of this)

=== April 15, 2015 ===
'''Updates'''
* Ready for 2.2.0 (apart from binary/deps issues)
** Missing some libs (scikit-learn, tej, tdparser, SQLAlchemy+connectors
** Windows: runvistrails.py is no longer used, so the PATH is wrong
** Windows: pip is broken, but it probably wouldn't work anyway because of permission issues (disable this?)
* Queries, upgrades and getPipeline() usage ([https://github.com/VisTrails/VisTrails/issues/1054 #1054])
** Getting a pipeline with getPipeline() is not safe: it might return an invalid pipeline
** This is used in many places throughout the code, like queries
** Upgrading would require going through the controller, but that creates new actions
* [TC] Avoid copying a module's output if it's used as input by exactly one downstream module ([https://github.com/VisTrails/VisTrails/issues/1060 #1060]) (useful for big numpy arrays you can update in-place)

=== April 8, 2015 ===
'''Updates'''
* [DK] Merged RR's changes for output modules (1012 and 1013)
** RR will merge remaining changes, then create v2.2 branch!

'''Items to Discuss'''
* BNL need numpy array to VTK image
** Looks like VTK has some helpers for this
** We will help if issues arise
** Will contribute back to VisTrails package
* Upgrade issue: [https://github.com/VisTrails/VisTrails/issues/1017 #1017]
** Automatic upgrades should happen between versions of provided upgrades
** Our existing upgrades work around this so it doesn't need to be 2.2.0
* Corner-case VTK modules
** No longer need VTKCell input port, so don't interfere with registry and API anymore
** Still work weirdly, people probably shouldn't use them
** But we have lots of clunky modules since we wrap the whole of VTK; some people might rely on this and know how to use them, let's keep them anyway
** Ready for 2.2.0

=== April 1, 2015 ===
'''Updates'''
* [RR] UV-CDAT: bugfixing for 2.2, long-term plans: implement scripting import/export in VisTrails, port to UV-CDAT
* Possibly, try to move to regular VisTrails to use new features

'''Items to Discuss'''
* 2.2 release: nothing much is pending anymore, release next week?
** [TE] vtkExporter classes [https://github.com/VisTrails/VisTrails/issues/1032 #1032]
** [RR] Hiding upgrades in version tree might make it (or might be 2.2.1 so we can test it out) [https://github.com/VisTrails/VisTrails/issues/949 #949]
** Output modules changes to go in
* add note to documentation about order of parameters in VTK
* add issue about exporter upgrades if not already there

=== March 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* 2.2 release
** Checklist on Github: https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist
** Review output modules
** RR has a couple more issues to fix
** Ready to go -- sign app package for OSX? [https://github.com/VisTrails/VisTrails/issues/984 #984] We need access to the Apple Membership team

=== March 18, 2015 ===
'''Updates'''
* [TE] VTK6 works

'''Items to Discuss'''
* [RR] Release v2.1.5 with backported tabledata?
** MTA example needs updated tabledata (for JoinTables)
** Google Maps package still not available
* [RR] Work torward v2.2.0?
** changes:
*** new persistence
*** API changes
*** output module changes (upgrades?), maintain cells but try to upgrade
*** not wrapping stuff
*** VTK6? yes
*** JobSubmission stuff?
*** relabeling for upgrades [https://github.com/VisTrails/VisTrails/issues/949 #949]
** makes sense, needs the tree view code to be updated, check selection
** See [https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist 2.2 checklist]
* Discussion of [https://github.com/VisTrails/VisTrails/issues/1016 #1016]
** plumbing between outputs and output modes, how to define a mode that works for many outputs without writing for each output?

=== March 11, 2015 ===
'''Updates'''
* [RR] persistent_archive done; merge? ([https://github.com/VisTrails/VisTrails/pull/755 #755])
** note about the focus events for widgets
** TE be aware of file_archive for future binaries that include persistent_archive
* [TE] [https://github.com/VisTrails/VisTrails/pull/998 New VTK package] finished

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails? (see last week; decision needed)
** RR email to JF about this
** yes; email sent to Github
* [RR] Switching order of output ports ([https://github.com/VisTrails/VisTrails/pull/1006 #1006])
** added port specs are sorted at a separate spot (Module.*_port_specs properties) than those in the registry (which are sorted in the registry), but those two lists are just combined without respect to sort keys
** need to determine whether the two lists should be merged or remain distinct
** should make sure that order of input ports and output ports makes parallel connections for things with same order
** DK suggests breaking backward compatibility here: workflows still run, can fix easily if a problem in an existing package.
* [RR] Question about output modes ([https://github.com/VisTrails/VisTrails/pull/1007 #1007]), how to integrate in API ([https://github.com/VisTrails/VisTrails/pull/24 #24])
** Should ImageFileMode be removed? ("image" is not a mode, "file" is)
** ImageOutput missing?
** Feel free to change how formats works
* [TE] Test suite segfaults on Fedora 17 virtualbox. Install newer version? (Support ended in 2013)

=== March 4, 2015 ===
'''Updates'''
* [TE] VTK wrapper
** Works on VTK 5.10
** Still need to test VTK 6
** New general wrappers for python functions and classes

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails?
** When [http://i.imgur.com/UTY2qfg.png filing a pull request] from UV-CDAT/VisTrails, VisTrails/VisTrails is selected by default
** People keep forgetting to change the default ([https://github.com/VisTrails/VisTrails/pull/956 #956] [https://github.com/VisTrails/VisTrails/pull/968 #968] [https://github.com/VisTrails/VisTrails/pull/999 #999] [https://github.com/VisTrails/VisTrails/pull/1000 #1000] [https://github.com/VisTrails/VisTrails/pull/1003 #1003] [https://github.com/VisTrails/VisTrails/pull/1004 #1004] [https://github.com/VisTrails/VisTrails/pull/1005 #1005])
** Only way to change that is to not have it marked as a fork of VisTrails/VisTrails
** Github staff [https://gist.github.com/remram44/b364c24ef1e462ce6e2f can make that change for us]; should we do it?
** Juliana: comments on this? visibility vs. convenience/annoyance for developers
* [RR] What about [https://github.com/VisTrails/VisTrails/issues/991 #991]?

=== February 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] vtkviewcell for infovis support, can we unify with VTKCell?
** need to test this
* [TE] vtk wrapping
** Mostly finished
** VTK 5.10 produce incorrect results with old wrapping
*** Old wrapper is based mostly on VTK 4
*** Most vtk_examples affected
*** [http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Replacement_of_SetInput]
*** should be able to upgrade from SetInput to SetInputData (need to drop GetOutput and replace with self ports)
*** can we change vtkInstance to just return self and not wrap things
** terminator example not working under 5.8?
* How does VTK wrapping fit into general wrapping framework?
* [RR] new persistence package

=== February 18, 2015 ===
'''Updates'''
* [RR] New VisTrails API and IPython integration ([https://github.com/VisTrails/VisTrails/pull/24 #24])

'''Items to Discuss'''
* [TE] VTK wrapping
** [https://gist.github.com/rexissimus/16b74693545b5e7c1035 Benchmarking vtk package]
*** Old: 24.7 seconds
*** New: 10.5 seconds (Except first time that adds 8 sec)
**** The parsing that calls is_abstract (that tries to instanciate all vtk classes) is now only run the first time.
**** get_items_from_sigstring takes 2 seconds, maybe we can use a lookup dict for already computed sigstrings?
** Now using a general python function wrapper
*** VTK classes are wrapped into python function that does not depend on vistrails
*** VTK functions can be executed without vistrails
*** The spec maps functions into vistrails modules, but can also describe wrapping
*** A general python function wrapper that supports
**** kwarg inputs
**** single, list, dict outputs
**** callback for progress reporting
**** temporary file generator for using FilePool
**** optional output generation
*** Creating specs:
***** Create spec by hand
***** Auto-create spec outline (TODO) and manually finish it
***** Dynamically create spec (VTK)
***** Implement documentation wrappers (Can use scikitlearn wrapper to wrap numpydoc) (TODO)
***** Classes as bad functions needs to be wrapped in new functions before they are wrapped. This is different for each package.
****** Classes is hard: Like VTK, and matplotlib. Scikit-learn does still not wrap classes
***** Spec diffing and patching could be done using code from matplotlib.
** Still needs upgrades from old VTK package
*** Is it possible to dynamically wrap functions, e.g, you see a SetFunc and just remove the 'Set' prefix. Or do you need to create a complete mapping?

=== February 11, 2015 ===
'''Updates'''
* Update from Friday's meeting
** discussed VisTrails internals
** discussed wrapping
*** xml discussion, hard to modify because tied to db code
*** TE has made it possible to add the schema-defined attributes to the intermediate representation
*** higher-level operations on the port specs
** make sure the simple case works
*** [JF] take a simple package with documentation and figure out what the base case for wrapping is

'''Items to Discuss'''
* [TE] VTK wrapping
** Dynamic loading works
** Reading XML is fast enough, but [https://gist.github.com/rexissimus/8272d3c776ccfa115d82 unserializing data is slow]
** Working on patterns for patching
** Matplotlib has many advanced patterns like argument ordering, nested arguments, alternateSpecs, output types.
*** Having all this in a general wrapper might confuse users?
** [RR] Delay module (except for identifiers) until you need it---e.g. don't deal with port specs, etc. until necessary
* Scripting Support [https://github.com/VisTrails/VisTrails/pull/950 #950]
** [RR] Issue with getting code from modules
** Design a simple solution
** [JF] Couldn't you use modules as black boxes without conversion, just to call into modules/subworkflows easily from e.g. IPython?
*** [RR] This is a job for the API, and a very separate use case. See [https://github.com/VisTrails/VisTrails/pull/24 #24]

=== February 4, 2015 ===
'''Updates'''

'''Items to Discuss'''
* Wrapping
** Format to use? Currently XML (like current matplotlib)
*** JSON and YAML have simple "to python dictionary" methods
*** But don't stream
*** YAML a lot easier for humans
** [DK] vtk-new-package also changes parameter names, creates enumerations
*** intermediate schema needs to be extensible
*** packages will want to store there specific infos for compute() method generation
*** also might have specs-altering info, like matplotlib's alternateSpec
** representation to code , registry already has schema for some aspects
** [RR] We might want to see if Module subclasses can be created lazily
*** no need to create all the classes just to register them in the registry and never actually use most of them
*** future effort
* [RR] Where should VisTrails packages live?
** tej installs as 'vistrailspkg.tej', TE installed it as 'userpackages.tej'
** Currently, standard packages are 'vistrails.packages.', user packages are 'userpackages.' and packages loaded through pkg_resources might be anything
** [RR] Use 'vistrailspkg.' everywhere?
** Long-term effort to simplify package distribution/installation (and have VisTrails get them automatically?)

=== January 28, 2015 ===
'''Updates'''
* T. Caswell to come visit on Fri 6 to discuss wrapping work

'''Items to Discuss'''
* [TE] New VTK wrapping
** Current code by DK seems a good deal faster
** Generates XML that can be patched/tweaked, generates Python code from it, VisTrails only loads generated Python code
** RR would rather have VisTrails load intermediate representation (= XML) directly, wants to make sure this is not slower
** The goal is to turn the intermediate step into something generic that would be used for every wrapped package (vtk, numpy, matplotlib, sklearn, java) instead of each having its own
** TC has its own code at [https://github.com/Nikea/VTTools/blob/master/vttools/wrap_lib.py github:VTTools] which parses numpy docstrings and generates modules, doesn't yet handle classes or persist anything
* Web crawler
** Right now, TE starts jobs for "start crawler", "stop crawler", "install classifier"
** RR would rather have the crawling be a job as far as VisTrails and tej are concerned
** The whole thing would be one pipeline: load examples, train classifier, start crawler [check for job, kill previous one, upload model, start processes], get snapshot, visualize
*** Need some support in tej and job submission system: long-running jobs, stop a job (wait for it to finish?), restart a job even though results are cached

=== January 21, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Unified wrapping method discussion [https://github.com/VisTrails/VisTrails/issues/991 #991]
** TE to work on reusable method with intermediate representation, starting with VTK
* [RR] Examples for scikit-learn: JF has an old example using Weka with parameter exploration (not currently in source tree)
** AM's examples are enough
* [AM] scikit-learn package is done, merge it in? [https://github.com/VisTrails/VisTrails/pull/955#issuecomment-70286788 #955]
** RR will merge
* [RR] What should copyright headers say? [https://github.com/VisTrails/VisTrails/pull/994#issuecomment-70173935 #994]
** Let's keep everything in there: Utah/Poly/NYU

=== January 14, 2015 ===
'''Updates'''
* [TE] Working on classifier
* [RR] Scripting integration, work in progress

'''Items to Discuss'''
* [RR] Unified wrapping method discussion ([https://github.com/VisTrails/VisTrails/issues/991 #991])
** Let's talk next week, [AM] and [DK] are not here

=== January 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* make sure that we address critical issues, questions, and pending review branches in a timely manner
* scripting support
** [RR] no issues if we want to just keep annotations in the generated code to allow the link back to a workflow
** [RR] can translate from workflow to script, working on script to workflow
** will work for parameter value changes, structural changes require changes to the annotations
** need to publish best practices here
** would be cool to do looping in scripts (easier interface than with workflows)
* notebook support (convert form notebook to workflow)
** RR will sync with FC on this
* Issue with console in built-from-scratch
** [TC] iPython rearranged some of the completion stuff in 2.2 and 2.3
** binary has old version of iPython -> 1.0.0, should we update?
* [TC] automated wrapping of numpy and scipy
** discovered a bunch of malformed documentation in numpy and scipy
** has github repo for vistrails tools
** example modules wrap a bunch of R stuff (not baked in, just how things are)
** will be pushing wrapping logic up
** port names forbidden (window and domain)
** have an import hook to get from yaml directly to VisTrails Modules
** should work for any python modules with well-formed numpy docstrings.
* [Action] should make it clear in documentation that Constant now means serializable not that the value doesn't change (e.g. List)
* [TC] might be interesting to try to build components of matplotlib and accumulate in figure (long-term project, but thinking about how this might work)
* [TE] build and build scripts
** completely automatic, buildbot
** need to set the build machines for the environment we want for the binary
** would virtualenv work here?
** [TC] anaconda can pin versions, potential path to test different configurations
** Q: upload nightly binary builds? A: makes sense, make sure they are well-labeled
* sourceforge stats: e.g. http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07
* package issues (see Remi's message)
* [TE] Scope of tej
** Support single ssh commands?
** Queue can be used as a remote machine (crawler is using queue.call*)
* SourceForge stats: http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07

== Older meetings ==
* [[Development/2014]]
* [[Development/2013]]
* [[Development/2012]]
* [[Development/2011]]
* [[Development/2010]]

Development

2016-07-20T14:57:01Z

Tommy: /* July 13, 2016 */

<div class="nonumtoc toclimit-1">
__TOC__
</div>

See also the [https://github.com/VisTrails/VisTrails/wiki/Development Github wiki]

== 2016 ==

=== July 20, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] New patch method for python-wrapper [https://gist.github.com/rexissimus/009b303e4cadcd4b8f2fec6cf848cb2b example]
** A patch is a string template with self/input/output variables for patching a class method
** Patches are stored in xml specification
** Patches are assigned to methods in ClassSpec's
** Used both for execution in vistrails and when exporting as script
*** Executed with "exec" when run in vistrails
*** Turns patches into natural calls in script
** Wrapping VTK library no longer needed
** Removes ".vtkInstance" (Automatically removed from PythonSources and vtkInteractionHandlers)
** Also used for port translations (With patch names like "basic:Color#input") (No more ugly input_t method definitions)
** TODO's
*** Add to export_as_script
*** Patch Modules that represent Python functions as well

* [vistrails-users] Read data from SQL example?

=== July 13, 2016 ===

'''Updates'''

* [DK] bundles on sql-alchemy branch
** Bundle, BundleMapping, and BundleSerializer
** New BaseSerializers to deal with versions of directory, zip, db serializers
** Can register the BundleSerializers with the base serializers
** Translation between bundle versions
** Bundle.add_object "just works" if an appropriate mapping was registered

'''Items to Discuss'''
* [TE] Simplified running module using API for scripting [https://gist.github.com/rexissimus/b28d83ae516a519167f5751bb8ab3739 example]
** API Module can be executed using '''compute''' method
*** Takes list of outputs to compute + inputs as keyword arguments
* Status of general cell synchronization (vistrails-users)

=== July 6, 2016 ===

'''Updates'''

* [DK] Working on bundles

'''Items to Discuss'''
* [TE] Using vistrails API in scripting [https://gist.github.com/rexissimus/034d9c4dedc3299a079e84981dedd8c7 example 1 (API with VTK)] [https://gist.github.com/rexissimus/a4a9ca6c08d4058c64967d2b35415fd5 example 2 (DownloadFile only)]
** Call module in script using vistrails API
** Can be used when no export method is defined.
* [TE] [https://github.com/VisTrails/VisTrails/commit/c76c109349769fee1280f85c22678380a2f9cd39 Server news bug] Critical?
**[RR] No, unreleased
* [DK] New bundle organization
** BundleMapping contains individual mappings from raw objects to BundleObj
** Must be separate in order to have in-memory, separate from serializer settings

=== June 29, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Export VTK as python script
** Works on Terminator (Isosurface, Volume Rendering, clipping plane, combined rendering) [https://gist.github.com/rexissimus/16caf5200802e150296f62a0c7844c5a example]
** Preludes (imports) still need improvements
** Works with vtkInteractionHandler (clipping plane)
** Resulting clipping plane is incorrect? (supposed to hide one side of the plane)
** vtkRendererOutput Uses VTKRenderWindow as output
*** Should support different output modes?
*** Does not work with multiple outputs (Next cell is displayed when current is closed)
*** Uses wrapped vtkInstance (as vvtk)
**** Create new patch system with code that can be used both in vistrails and in a python script?

=== June 22, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Fix for upgraded analogies (PR [https://github.com/VisTrails/VisTrails/pull/1177 #1177])
** Uses module location to find module remap (The best we can do right now?)
** Also fixes remapped port names for connections to existing modules
** May still fail on complex upgrades like adding a function on an upgraded module that has a different port name

* [TE] Working on exporting wrapped libraries (VTK)

=== June 15, 2016 ===

'''Updates'''
* [TE] Added depth logic to python script exporter ([https://github.com/VisTrails/VisTrails/commit/50f220e4f6abe5a7bb8689f73f456f43df2dbc12 full commit])
** Fully implements connection merging and list looping

'''Items to Discuss'''

* [TE] Making analogy work on upgraded workflows ([https://github.com/VisTrails/VisTrails/issues/1175 #1175])
** Analogy only works We need to use the non-upgraded action chain
** But pipelines need to be valid (matcher uses module portspecs)
** Tried to get upgrade remap from upgrade action, but this seems impossible
** Use module location instead?
*** Location should be identical for one-to-one module upgrades

=== June 1, 2016 ===

'''Updates'''
* VisTrails 2.2.4 announced (finally)
** 5 survey replies
** 47 downloads last week

'''Items to Discuss'''
* [TE] Export VTK as script (python-wrapper)
** to_python_script
*** needs the pipeline (or at least the connections)
**** Should not generate code for any possible VTK method (exporter detects which ports is used in the source)
**** VTK needs to know connection order
**** Adding functions directly to the script results in nicer code
** Add support for multiple input connections
** Add support for list looping

=== May 25, 2016 ===

'''Updates'''
* Mailing-list fixed
* Getting stats from the "server news" mechanism (via [https://github.com/remram44/apache-log-info parser])

'''Items to Discuss'''
* [RR] Alexis doing writeup on VisTrails, curious about interesting streaming use-cases (and potential future users)
* [TE] Union ports
** Show union ports in pipeline (DEMO)

=== May 18, 2016 ===

'''Items to Discuss'''
* [TE] mailing list still down - Julio working on it
* [TE] Improved union port
** New schema 1.0.5 adds portitem.union string attribute
** Works with pipeline view, parameter exploration view, and mashup view
** Should work well for matplotlib
** Use with VTK ports?
*** It uses [item_1,item_2] style ports usually with different tuple length.
* [TE] Remove emacs dependency from db generate [https://github.com/VisTrails/VisTrails/issues/1173 #1173]

=== May 11, 2016 ===

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]
** GUI-based solution [https://github.com/VisTrails/VisTrails/tree/union-port Branch union-port] Demo?
*** Shows single port for all ports with same sort_key
*** Select specific type when adding/showing
*** Only one type should be visible on the module at any time
*** Making tuple parameters union types is probably too complicated
*** Should work with alternate specs like matplotlib (if sort_key is defined correctly)

* [TE] Feature suggestion: Let connections connect to functions/parameters
** Show functions and parameters as ports and toggle port visibility directly for functions and parameters
** Use separate views for ports and functions (like before)
*** Allow rearranging of functions
** Pros:
*** Supports ordered connections. Create 2 functions, make them visible as ports, make connections to them.
**** We can also have, e.g., a line joining the ports on the module to indicate they are part of a list.
**** Makes List module simpler
*** Connect to parameter in tuple
*** Functions that are visible on the module can connect to an actual function, and not just to the first one it finds.
*** Can replace operation modules (in python-wrapper) in some cases for, e.g., numpy.
** Cons:
*** Interface more complicated and crowded
*** More difficult for users to grasp?
*** No immediate use case
*** Makes no union type for tuple parameters a bigger problem.

* [TE] Publish user survey?
** No response from vistrails release yet
** Not announced on vistrails-users yet.

=== May 4, 2016 ===
'''Updates'''
* VisTrails 2.2.4 released

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]

=== April 27, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Wrapping Bokeh
** New method type "operation"
*** Transforms Figure->Glyph->Output into Glyph->Figure->Output
**** Glyph sets function name and arguments as output
***** Not serializable, but should always be computed together with the subject of the operation.
**** Figure applies Glyph operation on itself
*** Useful for matplotlib?
**** matplotlib currently find actors by searching upstream?
**** But this is more difficult since matplotlib is not function-based.
** New "union" port type
*** Turns "x(float), x(list)" into "x (float, list)" and uses first set value
**** Uses only first value in tuple
**** Bokeh have many properties that support (list, string, Float)
*** Does not work with depth=1 types (e.g. Float of depth 1)
**** Turn Depth 1 types with known type into lists?

* [TE] New bugfix release
** Finalize survey

=== April 20, 2016 ===
'''Updates'''
* Merged upgrade fixes
** Now has infinite loop test
** loop test now correctly loops 5 times
*** remap_module used wrong (current) package version when creating ModuleDescriptor
* Fixed multi-step group upgrades (PR: [https://github.com/VisTrails/VisTrails/issues/1168 #1168])

'''Items to Discuss'''
* New bugfix release
** Merge usagestats
** Need to finalize survey

=== April 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Chaining upgrades done ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Replace "Upgrade" description annotation with "upgraded_from" annotation to identify which tags to hide?

* [TE] Iterating handle_invalid_pipeline ([https://github.com/VisTrails/VisTrails/pull/1165 #1165])
** Not based on [https://github.com/VisTrails/VisTrails/tree/chain-upgrades-loop chain-upgrades-loop]
** Cherry-pick test to preserve source?
** Need maxPipelineFixAttempts option?
*** The code is now smarter about recursion, so max attempts will "probably" never be reached.
** Need [https://github.com/VisTrails/VisTrails/commit/0ef0667426937eddb1d1c1e397f0657ffec039a9 debug messages]?
*** Would need to be moved into handle_invalid_pipeline

=== April 6, 2016 ===
'''Updates'''
* [TE] Query View improvements
** Done except for displaying "Version Info" and #1164
* [RR] Working on finishing new interpreter (finally!)

'''Items to Discuss'''
* [TE] Chaining upgrades ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Try latest upgrade first, then previous.
** If all fail, select latest upgrade?

=== March 30, 2016 ===
'''Updates'''

'''Items to Discuss'''

* [TE] Query View improvements
** Unified do_version_switch and get_upgrades as validate_version()
** Problems with query view using its own controller
*** Fixed module info not being displayed for query results
*** Still no version info for query results
*** Still an issue with version query view not being updated

=== March 23, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Usage reporting almost ready to go
** Need to record whether specific features are used: paramexpore, mashup, query
*** [DK] Record if LaTeX extension is used? But hard to distinguish from direct batch invocation
** How to record size of vistrail?
*** [DK] IdScope already walks over vistrail, use that
*** but total number of modules and versions doesn't give an idea of average size of individual pipelines

=== March 16, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Upgrades in Query Mode
** Now using code similar to do_version_switch
*** Uses handle_invalid_pipeline
*** Differences: Not using current_pipeline, flushes changes
*** New controller method get_pipeline optimized using cached pipelines (but not current_pipeline)
*** Integrate to avoid repeated code?
*** Use this for query mode?
* [TE] VisTrails 2.2.4 ready for release?
** tej package updated. Others?
* [JF] upgrades and the version tree
* [JF] provenance in Jupyter
* [DK] bundles: [https://github.com/VisTrails/VisTrails/pull/1092 #1092]

=== March 9, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixing search mode
** String query now matches all by default
*** This caused pipeline queries to never match
** String query can search: User/Notes/Tagname/Time/Module name
*** Should we search module names by default? (Disabled by default because it is expensive)
*** Fixed notes search
** '>' parameter queries in documentation but has been removed
** Fixed module matches for upgraded pipelines (By not upgrading pipeline)
*** Upgrades still a problem
*** Add "Upgrade all menu option?" (Or upgrade all on open when `hideUpgrades`)
*** [JF] Allow search on past tags

* [TE] Create new bugfix release
** Finish querying
** Path issue on windows

* [DK] Look into sqlalchemy and new bundle branches

=== March 2, 2016 ===
'''Updates'''
* [TE] Fixed cache bug with port specs
* [TE] VisTrails Next
** Most packages now work
** No qgis for Python 3

'''Items to Discuss'''
** Always dereference symlinks? [https://github.com/VisTrails/VisTrails/issues/1146 #1146]

=== February 23, 2016 ===
'''Updates'''
* [TE] Fixed PythonSource 100% CPU bug
* [TE] VisTrails Next
** Updated [http://opendap.co-ops.nos.noaa.gov/axis/webservices/wind/ NOAA Web Service] examples
*** Now uses REST service, tabledata, and Google Maps
*** Web Service replaced with DownloadFile

'''Items to Discuss'''
* [RR] Couple of fixes are in for API, and tej&reprounzip on the Mac binary. Also new release of tej, and working on anonymous usage reports.
** New 2.2 release soon?
* [RR] Anonymous usage reports
** Sends out info like number of modules & versions, packages used, Python & libs versions, execution time, specific features [https://github.com/VisTrails/VisTrails/pull/1154 #1154]
* [JF] Bring in noWorkflow to track variable dependencies, for the considered Jupyter integration?
* noWorkflow - provenance for python scripts
** Recent work on tracking dependencies
* Also integrates ReproZip with Jupyter
** [http://mybinder.org mybinder]
*** Use with ReproZip to automatically build Jupyter notebook interfaces
* Daves comments on Jupyter integration
** It is possible to identify cell order on the server side
** Not trivial to track order of cells on client side
* How does Galaxy workflows relate to VisTrails?
** Packaging in Galaxy is hard
** Galaxy for biomedical workflows, difficulty making it general
* Action items
** How difficult to track cell dependencies in Jupyter notebooks?
** Use noWorkflow to track cell dependencies?
** How difficult to modify mybinder to use ReproZip packages?

=== February 17, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixed Group memory usage
** Modules in groups are supposed to be freed when done executing
*** Prevented by logger that stored references to the modules (fixed, now using id(module))
*** Prevented by list iterator bug that stored list of modules on the 'self' port bug (fixed)
* [TE] VisTrails Next
** Removed deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** PythonSources will be upgraded
*** Fixes for Python < 3
*** fixes for VTK < 6
** TODOs
*** Remove RemoteQ
**** Port Hadoop to tej (Already have pbs)
*** Merge package wrapper
*** Finish SQLAlchemy branch
*** Finish new bundle branch
** [JF] Will contact Jeff and Matthias about moving to Python 3
* [JF] Query by Example is broken
* [JF] VisTrails Data Cleaning Project
** Use VisTrails to process and explore task-specific data while keeping provenance.
** Remi's Idea
*** Use VisTrails as the backend in a Jupyter notebook
*** Overcome problems with executing cells in random order
**** Interesting research topic, but little interest has yet been noted
*** Interesting to study how such a notebook would be used (Is there notebook usage data available?)
*** Impose restrictions to notebook cell boundaries
*** It will only work for functional operations
*** Can we fix, or detect, non-functional (mutating) operations?
*** Analyse code and data flow and see if it mutates data in unexpected ways?
*** Mutable operations can be created in many ways in Python
* Next meeting Tuesday 11:30

=== February 10, 2016 ===
'''Updates'''

'''Items to Discuss'''
* VisTrails Next
** Test suite passes
*** Python 3 less deterministic, module upgrade order random.
** [RR] updating packages: Reprounzip (pushed), tej, persistent_archive, ...
** All of our packages should run fine :)
** VTK thumbnail comparison works
*** Rendering bug on some systems
**** QVTKCell now inherits QGLWidget
*** Old thumbnails had wrong height due to spreadsheetwindow being too small
**** Fixed by regenerating thumbnails
*** Silenced deprecation messages when generating modules
*** Many new classes in VTK 7
** Remove deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** Will break existing PythonSources
**** Try to upgrade?
*** Old-style packages
**** Or only allow a new style, like __init__.py renamed to info.py? (merge with identifiers.py?)
***** Read info.py without importing package?
*** Fixes for Python < 3
*** Fixes for Qt < 5
*** fixes for VTK < 7
*** Remove self port?

=== February 3, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] [http://lists.vistrails.org/pipermail/vistrails-users/2016-January/000402.html Rendering a .pvd (ParaView) file?]

* VisTrails Next
** All tests but thumbnail comparison passes
** Still issues with gui and more packages needs to be tested
** PythonSource and MplSource upgraded with lib2to3
** Keep contrib packages? Update?
** [https://blog.kitware.com/vtk-7-0-0/ VTK 7 is released]
*** Supports Python 3
*** Will hopefully get into conda and others soon
*** Deprecates a bunch of modules

* [https://travis-ci.org/VisTrails/VisTrails/builds/106743348 Travis builder] for VisTrails Next
** Runs!
** Uses conda
*** Many levels of requirements
**** apt packages
**** conda packages
**** python packages in requirements.txt
**** python packages in setup.py
*** Can probably drop conda. Default builder does not have Qt5, but beta builder do!
*** But useful if we want to use conda in our own build process.
** Lots of errors I do not get locally?

* [http://goo.gl/forms/Z4HBrwaBWL User Survey]
** Have you used any alternatives to vistrails?
*** Relevant? More options?
** How often do you use any of these particular features in VisTrails?
*** Add/Remove alternatives?
** How important would you rank the following potential improvements to VisTrails?
*** Add alternatives?

=== January 27, 2016 ===
'''Updates'''
* New interpreter
** Working prototype soon
** Looping not completely done (and port combination mode: pairwise/cartesian...)
** Need to integrate with VisTrails
*** Compatibility with existing modules
*** Use log controller
*** Want to cache at multiple levels (whole stream/single element of stream)
*** Non-runtime attributes of modules (cache check, automatic conversion check, constant from/to string)

'''Items to Discuss'''
* User Survey

* ZMQ failing on windows (vistrails-users)

* [TE] [https://github.com/VisTrails/VisTrails/pull/1143 Python 3 branch]
** Testsuite almost passes
*** Failing are unicode filenames, some users guide examples, and thumbnail comparisons.
** Fixed issues
*** Signatures are now bytes (convert to string to show in widget)
*** Cannot compare different types, e.g., (None < 1)
**** PortSpec.depth and min/maxConn could be None. (Backport!)
**** cell.row could be None
*** Lots of unicode/bytes fixes to serializations
**** We have encryption implementations in the code! (keychain)
*** Lots of small fixes to package method differences
** Current issues
*** logging widget empty?
*** version tree signals messed up
*** provenance view legend icons black
*** Text do not fit in some widgets
*** VTK thumbnail comparison fails
**** VTK Cells have some faces in wrong direction?
**** Because running in VM?
** Installing on Ubuntu LTS/Latest Mint
*** Install latest matplotlib from pip
*** Install VTK 7.0.0rc2 from source
*** No QtWebEngine binary (controversial) (Must install sip/PyQt5/Qt5 from source)

=== January 20, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Backporting features from Python 3 + PyQt5 + Qt5
** Merged unicode with master ([https://github.com/VisTrails/VisTrails/tree/unicode unicode])
*** One unicode test failing
*** Problem saving to xml
** Used [http://python-future.org/ python-future] to run futurize stage 1 to update legacy (pre 2.6) code ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized unicode-futurized])
*** Updates print to functions 'from __future__ import print_function'
*** Updates exception calls to use 'as'
*** removes most usages of 'long' (mostly used unnecessarily)
**** Only needed for 32-bit support
*** Fixes relative imports (from __future__ import absolute_import)
** Fixing code that is deprecated in Qt 4.8 and removed in Qt 5 ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized-qt5 unicode-futurized-qt5])
*** Updated all signals to new-style
* If we go 2 to 3, this could break packages
** means we should schedule any package format changes for the same time
** e.g., imports should be unrelated to code path (function to load module from package identifier?) (take them out of vistrails.* [https://github.com/VisTrails/VisTrails/pull/1002 #1002])
** any structural changes (e.g. the __init__ versus init thing) (RR thinks it makes sense, though having both named "init" is unfortunate)
** putting package identifier as xml?
*** Python not so bad, plus some stuff in there is Python code (checking dependencies)
** version the APIs?
*** RR planning on versioning vistrails_module.Module, no point versioning the whole package?
* file formats on 2 to 3:
** no real translation/upgrade, but non-ascii values that work on 3 won't load in 2

=== January 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://gist.github.com/rexissimus/dfd27e466427529c385c Porting to Python 3 / PyQt5]
** Basic GUI and execution works
** Minimal work to support 2to3
** Hard to support both PyQt4 and PyQt5

=== January 6, 2016 ===
'''Updates'''
'''Items to Discuss'''
* Updating VisTrails dependencies
** Successfully built [https://gist.github.com/rexissimus/f1a1aada7de1c00a57c7 Win7-64/Python3/PyQt5/Qt5/WebEngine/VTK7]
*** VTK 7 is the first supporting Python 3 but is only in release candidate phase.
**** Next version of VTK 6 is rumored to support Python 3
**** There is a development branch of VTK 6 supporting Python 3
*** Can travis build this?
**** We can skip tests for WebEngine and VTK if needed
** Python 3 [https://python3wos.appspot.com/ showstoppers]
*** No MySQL-python (sqlalchemy supports mysql through other drivers)
*** No suds (there are active forks but we could also drop support?)
* Options for python2/3 support:
** Interpreter could be python2/python3 based on packages
** six layer works but not the easiest to maintain (e.g. in reprozip)
* Drop support for win-64
* Update copyright headers to 2016

== 2015 ==

=== December 30, 2015 ===
'''Updates'''
* Bokeh package finished
** Can output to Browser/IPython/Spreadsheet (Limited functionality in spreadsheet)
'''Items to Discuss'''
* Updating VisTrails dependencies
** Bokeh needs QWebEngine (Chromium) in Qt5 which requires PyQt5
*** Many plotting libraries only work in browsers
*** But Chromium may be a big and controversial dependency
*** Or create a browser version of the spreadsheet?
** Some users have requested Python 3
** Not backwards compatible?
** Target for VisTrails 3.0 with new interpreter?

=== December 16, 2015 ===
'''Updates'''
'''Items to Discuss'''
* Users list question
* [TE] Wrapping Bokeh
** Added bokeh property parser
*** complements numpydoc parser
*** Not all attributes are available, partially because I am using a pre-release version.
** Wrapped modules
*** bokeh.plotting finished (Backwards like matplotlib: Create plot then draw on it)
*** bokeh.charts mostly done (Missing arguments)
** QWebView mostly works (but no zooming or buttons)
*** It would be better to use external browser or QWebEngineView
** Added improvements to wrapper
*** Generalized port translations (Color/Path to native types)
*** Can use multiple docstring/property parsers simultaneously

=== December 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Looking into wrapper
** Will port TensorFlow
** Doing a pass on the wrapper code & doc
*** UX improvements
** Factorize high-level docstring parsers into core.wrapper? (sphinx, numpy, google)
** Problem with name vs module_name (fails sklearn tests because class_by_name() is broken)
** Looking into compressing specs, lazy registration of modules

=== December 2, 2015 ===
'''Updates'''
* [TE] Package wrapping
** Wrapped most of numpy/scipy using __all__
** Added class attribute and method access for classes (Can add to class or to separate inspector module)
** TODO: Document wrapping procedure

'''Items to Discuss'''

=== November 25, 2015 ===
'''Updates'''
* [RR] New interpreter is coming along
** Everything is a stream
** Task system, eventually work-stealing parallelism
** Streams no longer advance in lock-step
*** Allows for constructions like filter, join, sorted-merge
** depth>1 still to be tested, no current plan to allow this through the module interface
*** Through looping though, can do streams of streams

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapped most numpy functions (no polynomials)
** and half of scipy classes and functions
** Added functions manually from documentation (no parseable lists?)
** Focusing on data flow constructs (no property/method access for classes)
*** Using spec diff (empty for now) and dynamic parser (stores spec in .vistrails/)
** Python class/function wrapper now stable
** Add google doc parser?
*** Is there a parser available?

=== November 18, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Numpy class wrapping works
*** Basic type is List, since most types are array_likes.
*** TODO: More classes and functions
*** Some operations are in-place and some aren't, and docstring not super clear
*** [RR] It seems only methods mutate, and most have a numpy.xx function equivalent; just manually go through the methods and remove the mutating ones?
** Class wrapper is modular
*** Docstring parser and type string parser can be customized
*** Classes can have optional attribute/method ports
**** Inspectors and attribute/method modules can be created separately
** Use PythonCalc as an example
*** Can be re-implemented as a function with a parseable docstring
*** [RR] PythonCalc is just an example, and it might actually make sense to get rid of it, or do a proper math package with scalar operations (as separate modules, no combobox)
** [RR] TensorFlow to use wrapping as well
*** Very simple (only types 'tensor' & 'variable')

=== November 11, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapping numpy's classes using numpydoc (ndarray)
*** Wrapping constructor arguments, attribute getters/setters as module ports
**** Then how to access attributes afterwards?
***** Use input value port to class modules?
*** Wrap methods as modules? E.g., `ndarray.shape`.
*** Function wrapping is almost a subset of class wrapping
**** May be able to use the same parsing/execution methods
** VTK's non-getter/setter methods could be wrapped as modules
*** We could then remove extra logic in interpreter for keeping function order
** Bokeh uses autogenerated docstrings
*** We may be able to read the specification directly

* [RR] [https://github.com/VisTrails/VisTrails/pull/1138 TensorFlow package]
** Basic setup working, can execute the Mandelbrot example
** Will autogenerate the operations

=== November 4, 2015 ===
'''Updates'''
* [RR] Interpreter work requires a fix for [https://github.com/VisTrails/VisTrails/issues/1137 DB issue #1137]
* [DK] Kitware's Resonant [http://www.kitware.com/source/home/post/173]
** [https://github.com/girder/girder Girder]: data management system
** [https://github.com/Kitware/romanesco Romanesco]: execution engine, uses [http://www.celeryproject.org/ Celery] for task management
** Resonant Flow: web app for editing and executing workflows

'''Items to Discuss'''
* [TE] Added OSX Lion (10.7) VM on build machine using vagrant (seems ok with license?)
** New builds works on Lion
** Change the minimum requirement to 10.7?
* [TE] Package wrapping
* Added upgrade suggestions using 2 spec versions ([http://pastebin.com/30XUU8Gp example])
** using name edit distance to find matches
** Could use something better like port similarity for modules, and type similarity for ports
** Should write python upgrade code?
** Added spec to sklearn package
*** Can now diff spec versions and keep the spec static
*** There will be problems with downgrades and package versions

=== October 29, 2015 ===
'''Updates'''
* [TE] nightly-build-mac fixed (Needed to approve xcode license)

'''Items to Discuss'''
* [TE] matplotlib wrapper
** ported to general spec
** Diff can be used on general spec
*** Only needed minor changes
*** Fixed indexing bug that corrupted specs
*** Can now move diff tools to core/wrapper
** Add new plots?
*** New plots in mpl 1.3: eventplot
*** New plots in mpl 1.4: angle_spectrum, magnitude_spectrum, phase_spectrum', violinplot
*** No new plots in mpl 1.5 (from looking at boilerplate.py)

=== October 21, 2015 ===
'''Updates'''
* [RR] Alexis has arrived, will be working with [RR] on a more efficient interpreter

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package]
** Supporting multiple package versions
*** Check which version can be loaded [https://github.com/VisTrails/VisTrails/pull/1135 #1135]
*** We cannot show version requirements in the list of packages because old packages are loaded when importing the codepath
** Visual diff does not work well, but we can use the spec differ to see differences.
** Unifying vtk and matplotlib wrapping specs (WIP)
*** And porting matplotlibs spec differ to work on the general spec
*** Spec differ can then be used on vtk and other packages in the future
*** Will enable automatic upgrade generation
* [RR] Rework interpreter
** restore abstraction between interpreter/module code
** build looping, streaming, caching into the interpreter
** rework cache
** look into parallelism once basic functionality is there

=== October 14, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package] (adding numpydoc parser)

=== October 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/tree/fix-matplotlib-parser New matplotlib parser] (adding numpydoc parser)
** Added numpydoc attribute parser for plots.
*** TODO: Need better port spec reconciliation with call signature parser.
*** We can create a general numpydoc parser, but attribute types are unique to matplotlib.
** Needs package versioning
*** New spec will not support matplotlib < v1.4 due to changed path to axes classes.
*** Load spec version corresponding to installed matplotlib version?
*** Need version downgrades?

=== September 30, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Updating Matplotlib parser
** Matplotlib docstring parser fails on numpy docstrings
** I have [https://github.com/VisTrails/VisTrails/commit/eae8b0c16260810587e47c41cab53552cbb3cf0a added basic numpydoc parsing]
*** Only used by a few docstrings so far
*** Parsing uses many sources (class tables, signatures, ACCEPTS, method docstrings, definition parsing).
** Caswell said they were thinking about moving to traitlets, but this is not ready yet

=== September 23, 2015 ===
'''Updates'''
* [TE] VisTrails 2.2.3 released
** Also have pushed to PyPI, binstar, etc.
** Sourceforge vs. GitHub
*** should be able to host releases on GitHub
*** nightly binaries pushed to sf each night
*** old binaries?
* [TE] Re-wrapping MatPlotlib
** Keep static generation - Docstrings are brittle beween matplotlib versions
** Keep generating the executable classes - but create functions, not vistrails Modules
*** Why is there so much patching?
** Re-implemented Alternate PortSpec for InputPortSpec
*** It will now inherit specs from parent (No need to reimplement)
** Module upgrades?

'''Items to Discuss'''

=== September 16, 2015 ===
'''Updates'''
* [TE] Job Monitor tests and documentation done
** OK to leave document package in packages directory?

'''Items to Discuss'''
* [TE] Library wrapping: How to do code patching? [https://docs.google.com/drawings/d/1Sh3eOXot6v2y880jHKQrqXqAwr-0aoqYligg3z8G8MY/edit?usp=sharing Wrapping diagram]
** Insert code into module template (Old VTK code)
** Patch the library that is called (New VTK code)
** Somehow store code in spec and apply when executed?
*** Executed code needs at a minimum access to inputs, outputs, current class
*** Use standard input/output dict and obj reference that the code operates on?
*** Can this be done while keeping the execution abstract?

* Do new release now?

=== September 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* New release?
** [RR] wants reprounzip
** tej changes & doc
** job monitor & jobmixin fixes
** mongodb
** reprounzip
** warning: MplFigure type is int
** tabledata: add Reshape, DictoToTable & ListToTable, fix ListToTable with numpy arrays
** PythonSource can have same name for an input & output
** don't show spreadsheet at exit

=== September 2, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Limit autosaves? [https://github.com/VisTrails/VisTrails/pull/1126 #1126]

=== August 26, 2015 ===
'''Updates'''
* [TE] Added Job support to Parameter Explorations (Requested by Colin), and Mashups
** specify job ids, need to specify different ids for parameter explorations since they have the same version id
** how to deal with parameters passed in on command line
* [General] provenance: should be creating a new version when we execute workflow with changed parameters?
** currently, custom_params annotation stores this in provenance currently
** [RR] API doesn't record provenance if passing in parameters: http://git.io/vsAA5
'''Items to Discuss'''

=== August 19, 2015 ===
'''Updates'''
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [TE] Working on Job Monitor documentation

'''Items to Discuss'''
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [TE] Stop testing VisTrails 2.0?

=== August 12, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Build broken on Travis; because of IPython 4 released today? ([https://travis-ci.org/VisTrails/VisTrails/builds/75279795 build 992]; [https://github.com/VisTrails/VisTrails/issues/1123 #1123])

=== August 5, 2015 ===
'''Updates'''
* [TE] Fixes to Jobs
** Could not delete jobs
** Could not run job in group
** Job not reset when calling ModuleSuspended
** Added deleting job from context menu
* [RR] Writing documentation for everything [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

'''Items to Discuss'''

=== July 29, 2015 ===
'''Updates'''
* RR still looking into new interpreter thing
** Goal is to take out scheduling logic from Module so it can be split in multiple processes, and so that smarter strategies can be added in time
** This means some work on packages
** Spreadsheet can live in kernel process? Still some UI stuff that will take work (changing configuration, persistent archive's viewer, ...)
* [TE] Problems running examples [https://github.com/VisTrails/VisTrails/pull/1111 #1111]
** Testing of more examples requires additional packages on the test machines.
** Fixed faulty line-ending in PythonSource:s failing on Python 2.6.
** Test suite now testing SUDSWebServices (If web service is down, test suite will fail)
** preferences.py test failed reloading 'dialogs' package, switched to using 'URL'.

'''Items to Discuss'''

=== July 22, 2015 ===
'''Updates'''
* [TE] mailing lists back online
* [TE] Working on [https://github.com/VisTrails/VisTrails/issues/1107 #1107]
* [RR] Working on ReproZip package

'''Items to Discuss'''
* [RR] MongoDB package [https://github.com/VisTrails/VisTrails/pull/1106 #1106]
* [RR] Example for tej docs? [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

=== July 15, 2015 ===
'''Updates'''
* 2.2.2 released

'''Items to Discuss'''
* RR is considering executing everything in an IPython kernel (i.e. separate Python interpreter, like the one spawned for a notebook)
** It's a separate process that we can restart without restarting the app/gui
** We can isolate the execution environment (e.g. for the server)
** We can run the whole thing remotely (if your data is elsewhere, just run VisTrails locally and the pipeline elsewhere)
** Pipeline execution no longer makes the interface hang, it just makes the kernel hang (but that's fine)
** We can use notebooks as modules (probably way nicer than the PythonSource module)
** We can run multiple kernels so long as the ports carry things that are serializable
*** meaning we can put the multithreaded-interpreter without all the hacky parts it has now
*** we can run IPython kernels in all the languages IPython supports, [https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages currently 46]

=== July 8, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Buildbot github hook not working after IP address change
* [TE] No reference to VistrailsApplication ([https://github.com/VisTrails/VisTrails/issues/1103 #1103])
** [RR] Added PR [https://github.com/VisTrails/VisTrails/pull/1104 #1104]
* [TE] Reopening VT file after saving with bundled subworkflow won't offer subworkflow upgrade ([https://github.com/VisTrails/VisTrails/issues/1102 #1102])
** allow manual delete to fix right now
** fix this on top of the use-uuid branch
* [TE] Release VisTrails 2.2.1? ([https://github.com/VisTrails/VisTrails/blob/v2.2/CHANGELOG CHANGELOG])
** [https://github.com/VisTrails/VisTrails/pull/1093 output-modules-use-global-dir]
** [https://github.com/VisTrails/VisTrails/milestones/version%202.2 Current issues for 2.2]

=== July 1, 2015 ===
'''Updates'''
* [TE] PROV fixed
* [TE] Working on subworkflow issues
* [RR] Considering reworking the controller (log vs exception problem, retained upgrades causing interferences) and also the interpreter (IPython?)

'''Items to Discuss'''

=== June 24, 2015 ===
'''Updates'''

'''Items to Discuss'''
* UV-CDAT
* [TE] Can a cyclic workflow be valid? ([https://github.com/VisTrails/VisTrails/issues/1097 #1097])
** focus on disabling the ability to create cyclic pipelines because more things break than just this with a cyclic pipeline
* [RR] Relative paths ([https://github.com/VisTrails/VisTrails/pull/1057 #1057])
** This interacts with the new bundle; how do handle packing files inside the VT bundle?

=== June 17, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] current_version and reusing existing upgrades are broken ([https://github.com/VisTrails/VisTrails/issues/1095 ticket #1095])
** Could be that export to PROV is using an unflushed upgrade pipeline?
** current_version would then be correct.
** It may work to flush the actions before exporting?

=== June 10, 2015 ===
'''Updates'''
* DAT: fixed VTK issue on Linux and Mac
* Still crashes on Windows. Need help! Reminder: this works in the VisTrails spreadsheet (QCellPresenter), although no widget get changed there during a drag
** Is it a VTK bug?
** Is it simply impossible to change widgets during the drag, should we do it a different way?
** Did I miss something that is done in VisTrails but somehow not in DAT?
** Low prio, UV-CDAT doesn't run on Windows anyway

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 Updated pull request])
* Single instance code and batch mode

=== June 3, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 pr])
** Requires fixes to command line parameters, Output modules, and batch mode
** How to test this
** Updated missing/outdated flags
** Fixed view issues when generating graphs
* [TE] batch mode
** SpreadsheetOutput not enabled in batch mode. Should we check is_running_gui instead?
** Other instance setting flags from caller
** Is graphsAsPdf replacing spreadsheetDumpPdf?
** graphsAsPdf true by Default?
** Batch mode executing by default (Not needed when generating graphs)
** Re-added workflowInfo as withWorkflowInfo for writing graph and xml workflow
** [DK] batch mode should be outputting to files or stdout, shouldn't always trigger SpreadsheetMode
** execute flag, maybe make execution the default and allow a "--no-execute" if you only want to capture graphs, for example

=== May 27, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] API question
** http://lists.vistrails.org/pipermail/vistrails-users/2015-May/000357.html
* Status of DAT
** Can add VCS plot to DAT but need to work on configuration windows
** Documentation for graphics templates for UV-CDAT/vcs?
* Qt support?

=== May 20, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Reviving the DAT, integrating scripting & porting UV-CDAT!
** On [https://github.com/VisTrails/DAT GitHub] ([https://github.com/VisTrails/DAT/issues issues])
** Merging 2 years of development taking longer than expected, but getting there. The plan is to get the patches in VisTrails and never fork again, we never want to get in UV-CDAT's situation (and don't need to).
** VTK cell works fine on Linux but there was flickering on Mac & Windows before; still issues on Mac (Windows status unknown)
** Can get a VCS plot soon (but will need VTK cell fix)
** Integrate in UV-CDAT's build system (so we have cdms, VCS, ...) -> RR can do this, low priority
** How do we integrate scripting?
*** We want to be able to seamlessly make changes to a plot by changing Python code
*** Define new plots by entering Python code without writing modules/packages?
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 13, 2015 ===
'''Updates'''
* [RR] Test skipping whitelist ([https://github.com/VisTrails/VisTrails/pull/1069 #1069]) -- low priority
* [RR] Custom matplotlib modules can't be compatible with both 2.1 and 2.2 ([https://github.com/VisTrails/VisTrails/issues/1067 #1067]); should be fixed for ALPS ([https://github.com/VisTrails/VisTrails/issues/1070 #1070])

'''Items to Discuss'''
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 7, 2015 ===
'''Updates'''
* [RR] Export/import workflow to Python working!

'''Items to Discuss'''
* [Claudio] UV-CDAT
** The UV-CDAT project is the biggest user base of VisTrails
** VisTrails package management provides a lot of friction towards people plugging in their code
** Need to make it easy to integrate your random Python scripts in the system without having to deal with all the boilerplate, at least in the first step
** [RR] argues that modules are still good; UV-CDAT shouldn't move towards a purely script-based backend
** [RR] export/import with Python could reduce a lot of that friction by allowing 1) to edit workflow as Python 2) to open up boxes automatically if needed code doesn't match actual modules
** ...

=== April 29, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] <strike>Abstractions</strike> subworkflows status ([https://github.com/VisTrails/VisTrails/labels/subworkflows tickets])
* [RR] matplotlib compatibility (2.1 & 2.2), [https://github.com/VisTrails/VisTrails/issues/1067 #1067]
** RR to try and fix ALPS matplotlib modules

=== April 22, 2015 ===
'''Updates'''
* 2.2.0 has been released!
* Windows issue (via email from Ryan)
** issue with manifest file (may be a new file in VTK6?)
** Tommy has regenerated new Windows builds
* Binaries, pypi, and conda released
* [RR] Export as script
* Python sources using VTK need to switch to SetInputData (users should be aware of this)

=== April 15, 2015 ===
'''Updates'''
* Ready for 2.2.0 (apart from binary/deps issues)
** Missing some libs (scikit-learn, tej, tdparser, SQLAlchemy+connectors
** Windows: runvistrails.py is no longer used, so the PATH is wrong
** Windows: pip is broken, but it probably wouldn't work anyway because of permission issues (disable this?)
* Queries, upgrades and getPipeline() usage ([https://github.com/VisTrails/VisTrails/issues/1054 #1054])
** Getting a pipeline with getPipeline() is not safe: it might return an invalid pipeline
** This is used in many places throughout the code, like queries
** Upgrading would require going through the controller, but that creates new actions
* [TC] Avoid copying a module's output if it's used as input by exactly one downstream module ([https://github.com/VisTrails/VisTrails/issues/1060 #1060]) (useful for big numpy arrays you can update in-place)

=== April 8, 2015 ===
'''Updates'''
* [DK] Merged RR's changes for output modules (1012 and 1013)
** RR will merge remaining changes, then create v2.2 branch!

'''Items to Discuss'''
* BNL need numpy array to VTK image
** Looks like VTK has some helpers for this
** We will help if issues arise
** Will contribute back to VisTrails package
* Upgrade issue: [https://github.com/VisTrails/VisTrails/issues/1017 #1017]
** Automatic upgrades should happen between versions of provided upgrades
** Our existing upgrades work around this so it doesn't need to be 2.2.0
* Corner-case VTK modules
** No longer need VTKCell input port, so don't interfere with registry and API anymore
** Still work weirdly, people probably shouldn't use them
** But we have lots of clunky modules since we wrap the whole of VTK; some people might rely on this and know how to use them, let's keep them anyway
** Ready for 2.2.0

=== April 1, 2015 ===
'''Updates'''
* [RR] UV-CDAT: bugfixing for 2.2, long-term plans: implement scripting import/export in VisTrails, port to UV-CDAT
* Possibly, try to move to regular VisTrails to use new features

'''Items to Discuss'''
* 2.2 release: nothing much is pending anymore, release next week?
** [TE] vtkExporter classes [https://github.com/VisTrails/VisTrails/issues/1032 #1032]
** [RR] Hiding upgrades in version tree might make it (or might be 2.2.1 so we can test it out) [https://github.com/VisTrails/VisTrails/issues/949 #949]
** Output modules changes to go in
* add note to documentation about order of parameters in VTK
* add issue about exporter upgrades if not already there

=== March 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* 2.2 release
** Checklist on Github: https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist
** Review output modules
** RR has a couple more issues to fix
** Ready to go -- sign app package for OSX? [https://github.com/VisTrails/VisTrails/issues/984 #984] We need access to the Apple Membership team

=== March 18, 2015 ===
'''Updates'''
* [TE] VTK6 works

'''Items to Discuss'''
* [RR] Release v2.1.5 with backported tabledata?
** MTA example needs updated tabledata (for JoinTables)
** Google Maps package still not available
* [RR] Work torward v2.2.0?
** changes:
*** new persistence
*** API changes
*** output module changes (upgrades?), maintain cells but try to upgrade
*** not wrapping stuff
*** VTK6? yes
*** JobSubmission stuff?
*** relabeling for upgrades [https://github.com/VisTrails/VisTrails/issues/949 #949]
** makes sense, needs the tree view code to be updated, check selection
** See [https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist 2.2 checklist]
* Discussion of [https://github.com/VisTrails/VisTrails/issues/1016 #1016]
** plumbing between outputs and output modes, how to define a mode that works for many outputs without writing for each output?

=== March 11, 2015 ===
'''Updates'''
* [RR] persistent_archive done; merge? ([https://github.com/VisTrails/VisTrails/pull/755 #755])
** note about the focus events for widgets
** TE be aware of file_archive for future binaries that include persistent_archive
* [TE] [https://github.com/VisTrails/VisTrails/pull/998 New VTK package] finished

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails? (see last week; decision needed)
** RR email to JF about this
** yes; email sent to Github
* [RR] Switching order of output ports ([https://github.com/VisTrails/VisTrails/pull/1006 #1006])
** added port specs are sorted at a separate spot (Module.*_port_specs properties) than those in the registry (which are sorted in the registry), but those two lists are just combined without respect to sort keys
** need to determine whether the two lists should be merged or remain distinct
** should make sure that order of input ports and output ports makes parallel connections for things with same order
** DK suggests breaking backward compatibility here: workflows still run, can fix easily if a problem in an existing package.
* [RR] Question about output modes ([https://github.com/VisTrails/VisTrails/pull/1007 #1007]), how to integrate in API ([https://github.com/VisTrails/VisTrails/pull/24 #24])
** Should ImageFileMode be removed? ("image" is not a mode, "file" is)
** ImageOutput missing?
** Feel free to change how formats works
* [TE] Test suite segfaults on Fedora 17 virtualbox. Install newer version? (Support ended in 2013)

=== March 4, 2015 ===
'''Updates'''
* [TE] VTK wrapper
** Works on VTK 5.10
** Still need to test VTK 6
** New general wrappers for python functions and classes

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails?
** When [http://i.imgur.com/UTY2qfg.png filing a pull request] from UV-CDAT/VisTrails, VisTrails/VisTrails is selected by default
** People keep forgetting to change the default ([https://github.com/VisTrails/VisTrails/pull/956 #956] [https://github.com/VisTrails/VisTrails/pull/968 #968] [https://github.com/VisTrails/VisTrails/pull/999 #999] [https://github.com/VisTrails/VisTrails/pull/1000 #1000] [https://github.com/VisTrails/VisTrails/pull/1003 #1003] [https://github.com/VisTrails/VisTrails/pull/1004 #1004] [https://github.com/VisTrails/VisTrails/pull/1005 #1005])
** Only way to change that is to not have it marked as a fork of VisTrails/VisTrails
** Github staff [https://gist.github.com/remram44/b364c24ef1e462ce6e2f can make that change for us]; should we do it?
** Juliana: comments on this? visibility vs. convenience/annoyance for developers
* [RR] What about [https://github.com/VisTrails/VisTrails/issues/991 #991]?

=== February 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] vtkviewcell for infovis support, can we unify with VTKCell?
** need to test this
* [TE] vtk wrapping
** Mostly finished
** VTK 5.10 produce incorrect results with old wrapping
*** Old wrapper is based mostly on VTK 4
*** Most vtk_examples affected
*** [http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Replacement_of_SetInput]
*** should be able to upgrade from SetInput to SetInputData (need to drop GetOutput and replace with self ports)
*** can we change vtkInstance to just return self and not wrap things
** terminator example not working under 5.8?
* How does VTK wrapping fit into general wrapping framework?
* [RR] new persistence package

=== February 18, 2015 ===
'''Updates'''
* [RR] New VisTrails API and IPython integration ([https://github.com/VisTrails/VisTrails/pull/24 #24])

'''Items to Discuss'''
* [TE] VTK wrapping
** [https://gist.github.com/rexissimus/16b74693545b5e7c1035 Benchmarking vtk package]
*** Old: 24.7 seconds
*** New: 10.5 seconds (Except first time that adds 8 sec)
**** The parsing that calls is_abstract (that tries to instanciate all vtk classes) is now only run the first time.
**** get_items_from_sigstring takes 2 seconds, maybe we can use a lookup dict for already computed sigstrings?
** Now using a general python function wrapper
*** VTK classes are wrapped into python function that does not depend on vistrails
*** VTK functions can be executed without vistrails
*** The spec maps functions into vistrails modules, but can also describe wrapping
*** A general python function wrapper that supports
**** kwarg inputs
**** single, list, dict outputs
**** callback for progress reporting
**** temporary file generator for using FilePool
**** optional output generation
*** Creating specs:
***** Create spec by hand
***** Auto-create spec outline (TODO) and manually finish it
***** Dynamically create spec (VTK)
***** Implement documentation wrappers (Can use scikitlearn wrapper to wrap numpydoc) (TODO)
***** Classes as bad functions needs to be wrapped in new functions before they are wrapped. This is different for each package.
****** Classes is hard: Like VTK, and matplotlib. Scikit-learn does still not wrap classes
***** Spec diffing and patching could be done using code from matplotlib.
** Still needs upgrades from old VTK package
*** Is it possible to dynamically wrap functions, e.g, you see a SetFunc and just remove the 'Set' prefix. Or do you need to create a complete mapping?

=== February 11, 2015 ===
'''Updates'''
* Update from Friday's meeting
** discussed VisTrails internals
** discussed wrapping
*** xml discussion, hard to modify because tied to db code
*** TE has made it possible to add the schema-defined attributes to the intermediate representation
*** higher-level operations on the port specs
** make sure the simple case works
*** [JF] take a simple package with documentation and figure out what the base case for wrapping is

'''Items to Discuss'''
* [TE] VTK wrapping
** Dynamic loading works
** Reading XML is fast enough, but [https://gist.github.com/rexissimus/8272d3c776ccfa115d82 unserializing data is slow]
** Working on patterns for patching
** Matplotlib has many advanced patterns like argument ordering, nested arguments, alternateSpecs, output types.
*** Having all this in a general wrapper might confuse users?
** [RR] Delay module (except for identifiers) until you need it---e.g. don't deal with port specs, etc. until necessary
* Scripting Support [https://github.com/VisTrails/VisTrails/pull/950 #950]
** [RR] Issue with getting code from modules
** Design a simple solution
** [JF] Couldn't you use modules as black boxes without conversion, just to call into modules/subworkflows easily from e.g. IPython?
*** [RR] This is a job for the API, and a very separate use case. See [https://github.com/VisTrails/VisTrails/pull/24 #24]

=== February 4, 2015 ===
'''Updates'''

'''Items to Discuss'''
* Wrapping
** Format to use? Currently XML (like current matplotlib)
*** JSON and YAML have simple "to python dictionary" methods
*** But don't stream
*** YAML a lot easier for humans
** [DK] vtk-new-package also changes parameter names, creates enumerations
*** intermediate schema needs to be extensible
*** packages will want to store there specific infos for compute() method generation
*** also might have specs-altering info, like matplotlib's alternateSpec
** representation to code , registry already has schema for some aspects
** [RR] We might want to see if Module subclasses can be created lazily
*** no need to create all the classes just to register them in the registry and never actually use most of them
*** future effort
* [RR] Where should VisTrails packages live?
** tej installs as 'vistrailspkg.tej', TE installed it as 'userpackages.tej'
** Currently, standard packages are 'vistrails.packages.', user packages are 'userpackages.' and packages loaded through pkg_resources might be anything
** [RR] Use 'vistrailspkg.' everywhere?
** Long-term effort to simplify package distribution/installation (and have VisTrails get them automatically?)

=== January 28, 2015 ===
'''Updates'''
* T. Caswell to come visit on Fri 6 to discuss wrapping work

'''Items to Discuss'''
* [TE] New VTK wrapping
** Current code by DK seems a good deal faster
** Generates XML that can be patched/tweaked, generates Python code from it, VisTrails only loads generated Python code
** RR would rather have VisTrails load intermediate representation (= XML) directly, wants to make sure this is not slower
** The goal is to turn the intermediate step into something generic that would be used for every wrapped package (vtk, numpy, matplotlib, sklearn, java) instead of each having its own
** TC has its own code at [https://github.com/Nikea/VTTools/blob/master/vttools/wrap_lib.py github:VTTools] which parses numpy docstrings and generates modules, doesn't yet handle classes or persist anything
* Web crawler
** Right now, TE starts jobs for "start crawler", "stop crawler", "install classifier"
** RR would rather have the crawling be a job as far as VisTrails and tej are concerned
** The whole thing would be one pipeline: load examples, train classifier, start crawler [check for job, kill previous one, upload model, start processes], get snapshot, visualize
*** Need some support in tej and job submission system: long-running jobs, stop a job (wait for it to finish?), restart a job even though results are cached

=== January 21, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Unified wrapping method discussion [https://github.com/VisTrails/VisTrails/issues/991 #991]
** TE to work on reusable method with intermediate representation, starting with VTK
* [RR] Examples for scikit-learn: JF has an old example using Weka with parameter exploration (not currently in source tree)
** AM's examples are enough
* [AM] scikit-learn package is done, merge it in? [https://github.com/VisTrails/VisTrails/pull/955#issuecomment-70286788 #955]
** RR will merge
* [RR] What should copyright headers say? [https://github.com/VisTrails/VisTrails/pull/994#issuecomment-70173935 #994]
** Let's keep everything in there: Utah/Poly/NYU

=== January 14, 2015 ===
'''Updates'''
* [TE] Working on classifier
* [RR] Scripting integration, work in progress

'''Items to Discuss'''
* [RR] Unified wrapping method discussion ([https://github.com/VisTrails/VisTrails/issues/991 #991])
** Let's talk next week, [AM] and [DK] are not here

=== January 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* make sure that we address critical issues, questions, and pending review branches in a timely manner
* scripting support
** [RR] no issues if we want to just keep annotations in the generated code to allow the link back to a workflow
** [RR] can translate from workflow to script, working on script to workflow
** will work for parameter value changes, structural changes require changes to the annotations
** need to publish best practices here
** would be cool to do looping in scripts (easier interface than with workflows)
* notebook support (convert form notebook to workflow)
** RR will sync with FC on this
* Issue with console in built-from-scratch
** [TC] iPython rearranged some of the completion stuff in 2.2 and 2.3
** binary has old version of iPython -> 1.0.0, should we update?
* [TC] automated wrapping of numpy and scipy
** discovered a bunch of malformed documentation in numpy and scipy
** has github repo for vistrails tools
** example modules wrap a bunch of R stuff (not baked in, just how things are)
** will be pushing wrapping logic up
** port names forbidden (window and domain)
** have an import hook to get from yaml directly to VisTrails Modules
** should work for any python modules with well-formed numpy docstrings.
* [Action] should make it clear in documentation that Constant now means serializable not that the value doesn't change (e.g. List)
* [TC] might be interesting to try to build components of matplotlib and accumulate in figure (long-term project, but thinking about how this might work)
* [TE] build and build scripts
** completely automatic, buildbot
** need to set the build machines for the environment we want for the binary
** would virtualenv work here?
** [TC] anaconda can pin versions, potential path to test different configurations
** Q: upload nightly binary builds? A: makes sense, make sure they are well-labeled
* sourceforge stats: e.g. http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07
* package issues (see Remi's message)
* [TE] Scope of tej
** Support single ssh commands?
** Queue can be used as a remote machine (crawler is using queue.call*)
* SourceForge stats: http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07

== Older meetings ==
* [[Development/2014]]
* [[Development/2013]]
* [[Development/2012]]
* [[Development/2011]]
* [[Development/2010]]

Development

2016-07-13T15:01:35Z

Tommy: /* July 13, 2016 */

<div class="nonumtoc toclimit-1">
__TOC__
</div>

See also the [https://github.com/VisTrails/VisTrails/wiki/Development Github wiki]

== 2016 ==

=== July 13, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Simplified running module using API for scripting [https://gist.github.com/rexissimus/b28d83ae516a519167f5751bb8ab3739 example]
** API Module can be executed using '''compute''' method
*** Takes list of outputs to compute + inputs as keyword arguments
* Status of general cell synchronization (vistrails-users)

=== July 6, 2016 ===

'''Updates'''

* [DK] Working on bundles

'''Items to Discuss'''
* [TE] Using vistrails API in scripting [https://gist.github.com/rexissimus/034d9c4dedc3299a079e84981dedd8c7 example 1 (API with VTK)] [https://gist.github.com/rexissimus/a4a9ca6c08d4058c64967d2b35415fd5 example 2 (DownloadFile only)]
** Call module in script using vistrails API
** Can be used when no export method is defined.
* [TE] [https://github.com/VisTrails/VisTrails/commit/c76c109349769fee1280f85c22678380a2f9cd39 Server news bug] Critical?
**[RR] No, unreleased
* [DK] New bundle organization
** BundleMapping contains individual mappings from raw objects to BundleObj
** Must be separate in order to have in-memory, separate from serializer settings

=== June 29, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Export VTK as python script
** Works on Terminator (Isosurface, Volume Rendering, clipping plane, combined rendering) [https://gist.github.com/rexissimus/16caf5200802e150296f62a0c7844c5a example]
** Preludes (imports) still need improvements
** Works with vtkInteractionHandler (clipping plane)
** Resulting clipping plane is incorrect? (supposed to hide one side of the plane)
** vtkRendererOutput Uses VTKRenderWindow as output
*** Should support different output modes?
*** Does not work with multiple outputs (Next cell is displayed when current is closed)
*** Uses wrapped vtkInstance (as vvtk)
**** Create new patch system with code that can be used both in vistrails and in a python script?

=== June 22, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Fix for upgraded analogies (PR [https://github.com/VisTrails/VisTrails/pull/1177 #1177])
** Uses module location to find module remap (The best we can do right now?)
** Also fixes remapped port names for connections to existing modules
** May still fail on complex upgrades like adding a function on an upgraded module that has a different port name

* [TE] Working on exporting wrapped libraries (VTK)

=== June 15, 2016 ===

'''Updates'''
* [TE] Added depth logic to python script exporter ([https://github.com/VisTrails/VisTrails/commit/50f220e4f6abe5a7bb8689f73f456f43df2dbc12 full commit])
** Fully implements connection merging and list looping

'''Items to Discuss'''

* [TE] Making analogy work on upgraded workflows ([https://github.com/VisTrails/VisTrails/issues/1175 #1175])
** Analogy only works We need to use the non-upgraded action chain
** But pipelines need to be valid (matcher uses module portspecs)
** Tried to get upgrade remap from upgrade action, but this seems impossible
** Use module location instead?
*** Location should be identical for one-to-one module upgrades

=== June 1, 2016 ===

'''Updates'''
* VisTrails 2.2.4 announced (finally)
** 5 survey replies
** 47 downloads last week

'''Items to Discuss'''
* [TE] Export VTK as script (python-wrapper)
** to_python_script
*** needs the pipeline (or at least the connections)
**** Should not generate code for any possible VTK method (exporter detects which ports is used in the source)
**** VTK needs to know connection order
**** Adding functions directly to the script results in nicer code
** Add support for multiple input connections
** Add support for list looping

=== May 25, 2016 ===

'''Updates'''
* Mailing-list fixed
* Getting stats from the "server news" mechanism (via [https://github.com/remram44/apache-log-info parser])

'''Items to Discuss'''
* [RR] Alexis doing writeup on VisTrails, curious about interesting streaming use-cases (and potential future users)
* [TE] Union ports
** Show union ports in pipeline (DEMO)

=== May 18, 2016 ===

'''Items to Discuss'''
* [TE] mailing list still down - Julio working on it
* [TE] Improved union port
** New schema 1.0.5 adds portitem.union string attribute
** Works with pipeline view, parameter exploration view, and mashup view
** Should work well for matplotlib
** Use with VTK ports?
*** It uses [item_1,item_2] style ports usually with different tuple length.
* [TE] Remove emacs dependency from db generate [https://github.com/VisTrails/VisTrails/issues/1173 #1173]

=== May 11, 2016 ===

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]
** GUI-based solution [https://github.com/VisTrails/VisTrails/tree/union-port Branch union-port] Demo?
*** Shows single port for all ports with same sort_key
*** Select specific type when adding/showing
*** Only one type should be visible on the module at any time
*** Making tuple parameters union types is probably too complicated
*** Should work with alternate specs like matplotlib (if sort_key is defined correctly)

* [TE] Feature suggestion: Let connections connect to functions/parameters
** Show functions and parameters as ports and toggle port visibility directly for functions and parameters
** Use separate views for ports and functions (like before)
*** Allow rearranging of functions
** Pros:
*** Supports ordered connections. Create 2 functions, make them visible as ports, make connections to them.
**** We can also have, e.g., a line joining the ports on the module to indicate they are part of a list.
**** Makes List module simpler
*** Connect to parameter in tuple
*** Functions that are visible on the module can connect to an actual function, and not just to the first one it finds.
*** Can replace operation modules (in python-wrapper) in some cases for, e.g., numpy.
** Cons:
*** Interface more complicated and crowded
*** More difficult for users to grasp?
*** No immediate use case
*** Makes no union type for tuple parameters a bigger problem.

* [TE] Publish user survey?
** No response from vistrails release yet
** Not announced on vistrails-users yet.

=== May 4, 2016 ===
'''Updates'''
* VisTrails 2.2.4 released

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]

=== April 27, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Wrapping Bokeh
** New method type "operation"
*** Transforms Figure->Glyph->Output into Glyph->Figure->Output
**** Glyph sets function name and arguments as output
***** Not serializable, but should always be computed together with the subject of the operation.
**** Figure applies Glyph operation on itself
*** Useful for matplotlib?
**** matplotlib currently find actors by searching upstream?
**** But this is more difficult since matplotlib is not function-based.
** New "union" port type
*** Turns "x(float), x(list)" into "x (float, list)" and uses first set value
**** Uses only first value in tuple
**** Bokeh have many properties that support (list, string, Float)
*** Does not work with depth=1 types (e.g. Float of depth 1)
**** Turn Depth 1 types with known type into lists?

* [TE] New bugfix release
** Finalize survey

=== April 20, 2016 ===
'''Updates'''
* Merged upgrade fixes
** Now has infinite loop test
** loop test now correctly loops 5 times
*** remap_module used wrong (current) package version when creating ModuleDescriptor
* Fixed multi-step group upgrades (PR: [https://github.com/VisTrails/VisTrails/issues/1168 #1168])

'''Items to Discuss'''
* New bugfix release
** Merge usagestats
** Need to finalize survey

=== April 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Chaining upgrades done ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Replace "Upgrade" description annotation with "upgraded_from" annotation to identify which tags to hide?

* [TE] Iterating handle_invalid_pipeline ([https://github.com/VisTrails/VisTrails/pull/1165 #1165])
** Not based on [https://github.com/VisTrails/VisTrails/tree/chain-upgrades-loop chain-upgrades-loop]
** Cherry-pick test to preserve source?
** Need maxPipelineFixAttempts option?
*** The code is now smarter about recursion, so max attempts will "probably" never be reached.
** Need [https://github.com/VisTrails/VisTrails/commit/0ef0667426937eddb1d1c1e397f0657ffec039a9 debug messages]?
*** Would need to be moved into handle_invalid_pipeline

=== April 6, 2016 ===
'''Updates'''
* [TE] Query View improvements
** Done except for displaying "Version Info" and #1164
* [RR] Working on finishing new interpreter (finally!)

'''Items to Discuss'''
* [TE] Chaining upgrades ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Try latest upgrade first, then previous.
** If all fail, select latest upgrade?

=== March 30, 2016 ===
'''Updates'''

'''Items to Discuss'''

* [TE] Query View improvements
** Unified do_version_switch and get_upgrades as validate_version()
** Problems with query view using its own controller
*** Fixed module info not being displayed for query results
*** Still no version info for query results
*** Still an issue with version query view not being updated

=== March 23, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Usage reporting almost ready to go
** Need to record whether specific features are used: paramexpore, mashup, query
*** [DK] Record if LaTeX extension is used? But hard to distinguish from direct batch invocation
** How to record size of vistrail?
*** [DK] IdScope already walks over vistrail, use that
*** but total number of modules and versions doesn't give an idea of average size of individual pipelines

=== March 16, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Upgrades in Query Mode
** Now using code similar to do_version_switch
*** Uses handle_invalid_pipeline
*** Differences: Not using current_pipeline, flushes changes
*** New controller method get_pipeline optimized using cached pipelines (but not current_pipeline)
*** Integrate to avoid repeated code?
*** Use this for query mode?
* [TE] VisTrails 2.2.4 ready for release?
** tej package updated. Others?
* [JF] upgrades and the version tree
* [JF] provenance in Jupyter
* [DK] bundles: [https://github.com/VisTrails/VisTrails/pull/1092 #1092]

=== March 9, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixing search mode
** String query now matches all by default
*** This caused pipeline queries to never match
** String query can search: User/Notes/Tagname/Time/Module name
*** Should we search module names by default? (Disabled by default because it is expensive)
*** Fixed notes search
** '>' parameter queries in documentation but has been removed
** Fixed module matches for upgraded pipelines (By not upgrading pipeline)
*** Upgrades still a problem
*** Add "Upgrade all menu option?" (Or upgrade all on open when `hideUpgrades`)
*** [JF] Allow search on past tags

* [TE] Create new bugfix release
** Finish querying
** Path issue on windows

* [DK] Look into sqlalchemy and new bundle branches

=== March 2, 2016 ===
'''Updates'''
* [TE] Fixed cache bug with port specs
* [TE] VisTrails Next
** Most packages now work
** No qgis for Python 3

'''Items to Discuss'''
** Always dereference symlinks? [https://github.com/VisTrails/VisTrails/issues/1146 #1146]

=== February 23, 2016 ===
'''Updates'''
* [TE] Fixed PythonSource 100% CPU bug
* [TE] VisTrails Next
** Updated [http://opendap.co-ops.nos.noaa.gov/axis/webservices/wind/ NOAA Web Service] examples
*** Now uses REST service, tabledata, and Google Maps
*** Web Service replaced with DownloadFile

'''Items to Discuss'''
* [RR] Couple of fixes are in for API, and tej&reprounzip on the Mac binary. Also new release of tej, and working on anonymous usage reports.
** New 2.2 release soon?
* [RR] Anonymous usage reports
** Sends out info like number of modules & versions, packages used, Python & libs versions, execution time, specific features [https://github.com/VisTrails/VisTrails/pull/1154 #1154]
* [JF] Bring in noWorkflow to track variable dependencies, for the considered Jupyter integration?
* noWorkflow - provenance for python scripts
** Recent work on tracking dependencies
* Also integrates ReproZip with Jupyter
** [http://mybinder.org mybinder]
*** Use with ReproZip to automatically build Jupyter notebook interfaces
* Daves comments on Jupyter integration
** It is possible to identify cell order on the server side
** Not trivial to track order of cells on client side
* How does Galaxy workflows relate to VisTrails?
** Packaging in Galaxy is hard
** Galaxy for biomedical workflows, difficulty making it general
* Action items
** How difficult to track cell dependencies in Jupyter notebooks?
** Use noWorkflow to track cell dependencies?
** How difficult to modify mybinder to use ReproZip packages?

=== February 17, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixed Group memory usage
** Modules in groups are supposed to be freed when done executing
*** Prevented by logger that stored references to the modules (fixed, now using id(module))
*** Prevented by list iterator bug that stored list of modules on the 'self' port bug (fixed)
* [TE] VisTrails Next
** Removed deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** PythonSources will be upgraded
*** Fixes for Python < 3
*** fixes for VTK < 6
** TODOs
*** Remove RemoteQ
**** Port Hadoop to tej (Already have pbs)
*** Merge package wrapper
*** Finish SQLAlchemy branch
*** Finish new bundle branch
** [JF] Will contact Jeff and Matthias about moving to Python 3
* [JF] Query by Example is broken
* [JF] VisTrails Data Cleaning Project
** Use VisTrails to process and explore task-specific data while keeping provenance.
** Remi's Idea
*** Use VisTrails as the backend in a Jupyter notebook
*** Overcome problems with executing cells in random order
**** Interesting research topic, but little interest has yet been noted
*** Interesting to study how such a notebook would be used (Is there notebook usage data available?)
*** Impose restrictions to notebook cell boundaries
*** It will only work for functional operations
*** Can we fix, or detect, non-functional (mutating) operations?
*** Analyse code and data flow and see if it mutates data in unexpected ways?
*** Mutable operations can be created in many ways in Python
* Next meeting Tuesday 11:30

=== February 10, 2016 ===
'''Updates'''

'''Items to Discuss'''
* VisTrails Next
** Test suite passes
*** Python 3 less deterministic, module upgrade order random.
** [RR] updating packages: Reprounzip (pushed), tej, persistent_archive, ...
** All of our packages should run fine :)
** VTK thumbnail comparison works
*** Rendering bug on some systems
**** QVTKCell now inherits QGLWidget
*** Old thumbnails had wrong height due to spreadsheetwindow being too small
**** Fixed by regenerating thumbnails
*** Silenced deprecation messages when generating modules
*** Many new classes in VTK 7
** Remove deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** Will break existing PythonSources
**** Try to upgrade?
*** Old-style packages
**** Or only allow a new style, like __init__.py renamed to info.py? (merge with identifiers.py?)
***** Read info.py without importing package?
*** Fixes for Python < 3
*** Fixes for Qt < 5
*** fixes for VTK < 7
*** Remove self port?

=== February 3, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] [http://lists.vistrails.org/pipermail/vistrails-users/2016-January/000402.html Rendering a .pvd (ParaView) file?]

* VisTrails Next
** All tests but thumbnail comparison passes
** Still issues with gui and more packages needs to be tested
** PythonSource and MplSource upgraded with lib2to3
** Keep contrib packages? Update?
** [https://blog.kitware.com/vtk-7-0-0/ VTK 7 is released]
*** Supports Python 3
*** Will hopefully get into conda and others soon
*** Deprecates a bunch of modules

* [https://travis-ci.org/VisTrails/VisTrails/builds/106743348 Travis builder] for VisTrails Next
** Runs!
** Uses conda
*** Many levels of requirements
**** apt packages
**** conda packages
**** python packages in requirements.txt
**** python packages in setup.py
*** Can probably drop conda. Default builder does not have Qt5, but beta builder do!
*** But useful if we want to use conda in our own build process.
** Lots of errors I do not get locally?

* [http://goo.gl/forms/Z4HBrwaBWL User Survey]
** Have you used any alternatives to vistrails?
*** Relevant? More options?
** How often do you use any of these particular features in VisTrails?
*** Add/Remove alternatives?
** How important would you rank the following potential improvements to VisTrails?
*** Add alternatives?

=== January 27, 2016 ===
'''Updates'''
* New interpreter
** Working prototype soon
** Looping not completely done (and port combination mode: pairwise/cartesian...)
** Need to integrate with VisTrails
*** Compatibility with existing modules
*** Use log controller
*** Want to cache at multiple levels (whole stream/single element of stream)
*** Non-runtime attributes of modules (cache check, automatic conversion check, constant from/to string)

'''Items to Discuss'''
* User Survey

* ZMQ failing on windows (vistrails-users)

* [TE] [https://github.com/VisTrails/VisTrails/pull/1143 Python 3 branch]
** Testsuite almost passes
*** Failing are unicode filenames, some users guide examples, and thumbnail comparisons.
** Fixed issues
*** Signatures are now bytes (convert to string to show in widget)
*** Cannot compare different types, e.g., (None < 1)
**** PortSpec.depth and min/maxConn could be None. (Backport!)
**** cell.row could be None
*** Lots of unicode/bytes fixes to serializations
**** We have encryption implementations in the code! (keychain)
*** Lots of small fixes to package method differences
** Current issues
*** logging widget empty?
*** version tree signals messed up
*** provenance view legend icons black
*** Text do not fit in some widgets
*** VTK thumbnail comparison fails
**** VTK Cells have some faces in wrong direction?
**** Because running in VM?
** Installing on Ubuntu LTS/Latest Mint
*** Install latest matplotlib from pip
*** Install VTK 7.0.0rc2 from source
*** No QtWebEngine binary (controversial) (Must install sip/PyQt5/Qt5 from source)

=== January 20, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Backporting features from Python 3 + PyQt5 + Qt5
** Merged unicode with master ([https://github.com/VisTrails/VisTrails/tree/unicode unicode])
*** One unicode test failing
*** Problem saving to xml
** Used [http://python-future.org/ python-future] to run futurize stage 1 to update legacy (pre 2.6) code ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized unicode-futurized])
*** Updates print to functions 'from __future__ import print_function'
*** Updates exception calls to use 'as'
*** removes most usages of 'long' (mostly used unnecessarily)
**** Only needed for 32-bit support
*** Fixes relative imports (from __future__ import absolute_import)
** Fixing code that is deprecated in Qt 4.8 and removed in Qt 5 ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized-qt5 unicode-futurized-qt5])
*** Updated all signals to new-style
* If we go 2 to 3, this could break packages
** means we should schedule any package format changes for the same time
** e.g., imports should be unrelated to code path (function to load module from package identifier?) (take them out of vistrails.* [https://github.com/VisTrails/VisTrails/pull/1002 #1002])
** any structural changes (e.g. the __init__ versus init thing) (RR thinks it makes sense, though having both named "init" is unfortunate)
** putting package identifier as xml?
*** Python not so bad, plus some stuff in there is Python code (checking dependencies)
** version the APIs?
*** RR planning on versioning vistrails_module.Module, no point versioning the whole package?
* file formats on 2 to 3:
** no real translation/upgrade, but non-ascii values that work on 3 won't load in 2

=== January 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://gist.github.com/rexissimus/dfd27e466427529c385c Porting to Python 3 / PyQt5]
** Basic GUI and execution works
** Minimal work to support 2to3
** Hard to support both PyQt4 and PyQt5

=== January 6, 2016 ===
'''Updates'''
'''Items to Discuss'''
* Updating VisTrails dependencies
** Successfully built [https://gist.github.com/rexissimus/f1a1aada7de1c00a57c7 Win7-64/Python3/PyQt5/Qt5/WebEngine/VTK7]
*** VTK 7 is the first supporting Python 3 but is only in release candidate phase.
**** Next version of VTK 6 is rumored to support Python 3
**** There is a development branch of VTK 6 supporting Python 3
*** Can travis build this?
**** We can skip tests for WebEngine and VTK if needed
** Python 3 [https://python3wos.appspot.com/ showstoppers]
*** No MySQL-python (sqlalchemy supports mysql through other drivers)
*** No suds (there are active forks but we could also drop support?)
* Options for python2/3 support:
** Interpreter could be python2/python3 based on packages
** six layer works but not the easiest to maintain (e.g. in reprozip)
* Drop support for win-64
* Update copyright headers to 2016

== 2015 ==

=== December 30, 2015 ===
'''Updates'''
* Bokeh package finished
** Can output to Browser/IPython/Spreadsheet (Limited functionality in spreadsheet)
'''Items to Discuss'''
* Updating VisTrails dependencies
** Bokeh needs QWebEngine (Chromium) in Qt5 which requires PyQt5
*** Many plotting libraries only work in browsers
*** But Chromium may be a big and controversial dependency
*** Or create a browser version of the spreadsheet?
** Some users have requested Python 3
** Not backwards compatible?
** Target for VisTrails 3.0 with new interpreter?

=== December 16, 2015 ===
'''Updates'''
'''Items to Discuss'''
* Users list question
* [TE] Wrapping Bokeh
** Added bokeh property parser
*** complements numpydoc parser
*** Not all attributes are available, partially because I am using a pre-release version.
** Wrapped modules
*** bokeh.plotting finished (Backwards like matplotlib: Create plot then draw on it)
*** bokeh.charts mostly done (Missing arguments)
** QWebView mostly works (but no zooming or buttons)
*** It would be better to use external browser or QWebEngineView
** Added improvements to wrapper
*** Generalized port translations (Color/Path to native types)
*** Can use multiple docstring/property parsers simultaneously

=== December 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Looking into wrapper
** Will port TensorFlow
** Doing a pass on the wrapper code & doc
*** UX improvements
** Factorize high-level docstring parsers into core.wrapper? (sphinx, numpy, google)
** Problem with name vs module_name (fails sklearn tests because class_by_name() is broken)
** Looking into compressing specs, lazy registration of modules

=== December 2, 2015 ===
'''Updates'''
* [TE] Package wrapping
** Wrapped most of numpy/scipy using __all__
** Added class attribute and method access for classes (Can add to class or to separate inspector module)
** TODO: Document wrapping procedure

'''Items to Discuss'''

=== November 25, 2015 ===
'''Updates'''
* [RR] New interpreter is coming along
** Everything is a stream
** Task system, eventually work-stealing parallelism
** Streams no longer advance in lock-step
*** Allows for constructions like filter, join, sorted-merge
** depth>1 still to be tested, no current plan to allow this through the module interface
*** Through looping though, can do streams of streams

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapped most numpy functions (no polynomials)
** and half of scipy classes and functions
** Added functions manually from documentation (no parseable lists?)
** Focusing on data flow constructs (no property/method access for classes)
*** Using spec diff (empty for now) and dynamic parser (stores spec in .vistrails/)
** Python class/function wrapper now stable
** Add google doc parser?
*** Is there a parser available?

=== November 18, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Numpy class wrapping works
*** Basic type is List, since most types are array_likes.
*** TODO: More classes and functions
*** Some operations are in-place and some aren't, and docstring not super clear
*** [RR] It seems only methods mutate, and most have a numpy.xx function equivalent; just manually go through the methods and remove the mutating ones?
** Class wrapper is modular
*** Docstring parser and type string parser can be customized
*** Classes can have optional attribute/method ports
**** Inspectors and attribute/method modules can be created separately
** Use PythonCalc as an example
*** Can be re-implemented as a function with a parseable docstring
*** [RR] PythonCalc is just an example, and it might actually make sense to get rid of it, or do a proper math package with scalar operations (as separate modules, no combobox)
** [RR] TensorFlow to use wrapping as well
*** Very simple (only types 'tensor' & 'variable')

=== November 11, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapping numpy's classes using numpydoc (ndarray)
*** Wrapping constructor arguments, attribute getters/setters as module ports
**** Then how to access attributes afterwards?
***** Use input value port to class modules?
*** Wrap methods as modules? E.g., `ndarray.shape`.
*** Function wrapping is almost a subset of class wrapping
**** May be able to use the same parsing/execution methods
** VTK's non-getter/setter methods could be wrapped as modules
*** We could then remove extra logic in interpreter for keeping function order
** Bokeh uses autogenerated docstrings
*** We may be able to read the specification directly

* [RR] [https://github.com/VisTrails/VisTrails/pull/1138 TensorFlow package]
** Basic setup working, can execute the Mandelbrot example
** Will autogenerate the operations

=== November 4, 2015 ===
'''Updates'''
* [RR] Interpreter work requires a fix for [https://github.com/VisTrails/VisTrails/issues/1137 DB issue #1137]
* [DK] Kitware's Resonant [http://www.kitware.com/source/home/post/173]
** [https://github.com/girder/girder Girder]: data management system
** [https://github.com/Kitware/romanesco Romanesco]: execution engine, uses [http://www.celeryproject.org/ Celery] for task management
** Resonant Flow: web app for editing and executing workflows

'''Items to Discuss'''
* [TE] Added OSX Lion (10.7) VM on build machine using vagrant (seems ok with license?)
** New builds works on Lion
** Change the minimum requirement to 10.7?
* [TE] Package wrapping
* Added upgrade suggestions using 2 spec versions ([http://pastebin.com/30XUU8Gp example])
** using name edit distance to find matches
** Could use something better like port similarity for modules, and type similarity for ports
** Should write python upgrade code?
** Added spec to sklearn package
*** Can now diff spec versions and keep the spec static
*** There will be problems with downgrades and package versions

=== October 29, 2015 ===
'''Updates'''
* [TE] nightly-build-mac fixed (Needed to approve xcode license)

'''Items to Discuss'''
* [TE] matplotlib wrapper
** ported to general spec
** Diff can be used on general spec
*** Only needed minor changes
*** Fixed indexing bug that corrupted specs
*** Can now move diff tools to core/wrapper
** Add new plots?
*** New plots in mpl 1.3: eventplot
*** New plots in mpl 1.4: angle_spectrum, magnitude_spectrum, phase_spectrum', violinplot
*** No new plots in mpl 1.5 (from looking at boilerplate.py)

=== October 21, 2015 ===
'''Updates'''
* [RR] Alexis has arrived, will be working with [RR] on a more efficient interpreter

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package]
** Supporting multiple package versions
*** Check which version can be loaded [https://github.com/VisTrails/VisTrails/pull/1135 #1135]
*** We cannot show version requirements in the list of packages because old packages are loaded when importing the codepath
** Visual diff does not work well, but we can use the spec differ to see differences.
** Unifying vtk and matplotlib wrapping specs (WIP)
*** And porting matplotlibs spec differ to work on the general spec
*** Spec differ can then be used on vtk and other packages in the future
*** Will enable automatic upgrade generation
* [RR] Rework interpreter
** restore abstraction between interpreter/module code
** build looping, streaming, caching into the interpreter
** rework cache
** look into parallelism once basic functionality is there

=== October 14, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package] (adding numpydoc parser)

=== October 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/tree/fix-matplotlib-parser New matplotlib parser] (adding numpydoc parser)
** Added numpydoc attribute parser for plots.
*** TODO: Need better port spec reconciliation with call signature parser.
*** We can create a general numpydoc parser, but attribute types are unique to matplotlib.
** Needs package versioning
*** New spec will not support matplotlib < v1.4 due to changed path to axes classes.
*** Load spec version corresponding to installed matplotlib version?
*** Need version downgrades?

=== September 30, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Updating Matplotlib parser
** Matplotlib docstring parser fails on numpy docstrings
** I have [https://github.com/VisTrails/VisTrails/commit/eae8b0c16260810587e47c41cab53552cbb3cf0a added basic numpydoc parsing]
*** Only used by a few docstrings so far
*** Parsing uses many sources (class tables, signatures, ACCEPTS, method docstrings, definition parsing).
** Caswell said they were thinking about moving to traitlets, but this is not ready yet

=== September 23, 2015 ===
'''Updates'''
* [TE] VisTrails 2.2.3 released
** Also have pushed to PyPI, binstar, etc.
** Sourceforge vs. GitHub
*** should be able to host releases on GitHub
*** nightly binaries pushed to sf each night
*** old binaries?
* [TE] Re-wrapping MatPlotlib
** Keep static generation - Docstrings are brittle beween matplotlib versions
** Keep generating the executable classes - but create functions, not vistrails Modules
*** Why is there so much patching?
** Re-implemented Alternate PortSpec for InputPortSpec
*** It will now inherit specs from parent (No need to reimplement)
** Module upgrades?

'''Items to Discuss'''

=== September 16, 2015 ===
'''Updates'''
* [TE] Job Monitor tests and documentation done
** OK to leave document package in packages directory?

'''Items to Discuss'''
* [TE] Library wrapping: How to do code patching? [https://docs.google.com/drawings/d/1Sh3eOXot6v2y880jHKQrqXqAwr-0aoqYligg3z8G8MY/edit?usp=sharing Wrapping diagram]
** Insert code into module template (Old VTK code)
** Patch the library that is called (New VTK code)
** Somehow store code in spec and apply when executed?
*** Executed code needs at a minimum access to inputs, outputs, current class
*** Use standard input/output dict and obj reference that the code operates on?
*** Can this be done while keeping the execution abstract?

* Do new release now?

=== September 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* New release?
** [RR] wants reprounzip
** tej changes & doc
** job monitor & jobmixin fixes
** mongodb
** reprounzip
** warning: MplFigure type is int
** tabledata: add Reshape, DictoToTable & ListToTable, fix ListToTable with numpy arrays
** PythonSource can have same name for an input & output
** don't show spreadsheet at exit

=== September 2, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Limit autosaves? [https://github.com/VisTrails/VisTrails/pull/1126 #1126]

=== August 26, 2015 ===
'''Updates'''
* [TE] Added Job support to Parameter Explorations (Requested by Colin), and Mashups
** specify job ids, need to specify different ids for parameter explorations since they have the same version id
** how to deal with parameters passed in on command line
* [General] provenance: should be creating a new version when we execute workflow with changed parameters?
** currently, custom_params annotation stores this in provenance currently
** [RR] API doesn't record provenance if passing in parameters: http://git.io/vsAA5
'''Items to Discuss'''

=== August 19, 2015 ===
'''Updates'''
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [TE] Working on Job Monitor documentation

'''Items to Discuss'''
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [TE] Stop testing VisTrails 2.0?

=== August 12, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Build broken on Travis; because of IPython 4 released today? ([https://travis-ci.org/VisTrails/VisTrails/builds/75279795 build 992]; [https://github.com/VisTrails/VisTrails/issues/1123 #1123])

=== August 5, 2015 ===
'''Updates'''
* [TE] Fixes to Jobs
** Could not delete jobs
** Could not run job in group
** Job not reset when calling ModuleSuspended
** Added deleting job from context menu
* [RR] Writing documentation for everything [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

'''Items to Discuss'''

=== July 29, 2015 ===
'''Updates'''
* RR still looking into new interpreter thing
** Goal is to take out scheduling logic from Module so it can be split in multiple processes, and so that smarter strategies can be added in time
** This means some work on packages
** Spreadsheet can live in kernel process? Still some UI stuff that will take work (changing configuration, persistent archive's viewer, ...)
* [TE] Problems running examples [https://github.com/VisTrails/VisTrails/pull/1111 #1111]
** Testing of more examples requires additional packages on the test machines.
** Fixed faulty line-ending in PythonSource:s failing on Python 2.6.
** Test suite now testing SUDSWebServices (If web service is down, test suite will fail)
** preferences.py test failed reloading 'dialogs' package, switched to using 'URL'.

'''Items to Discuss'''

=== July 22, 2015 ===
'''Updates'''
* [TE] mailing lists back online
* [TE] Working on [https://github.com/VisTrails/VisTrails/issues/1107 #1107]
* [RR] Working on ReproZip package

'''Items to Discuss'''
* [RR] MongoDB package [https://github.com/VisTrails/VisTrails/pull/1106 #1106]
* [RR] Example for tej docs? [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

=== July 15, 2015 ===
'''Updates'''
* 2.2.2 released

'''Items to Discuss'''
* RR is considering executing everything in an IPython kernel (i.e. separate Python interpreter, like the one spawned for a notebook)
** It's a separate process that we can restart without restarting the app/gui
** We can isolate the execution environment (e.g. for the server)
** We can run the whole thing remotely (if your data is elsewhere, just run VisTrails locally and the pipeline elsewhere)
** Pipeline execution no longer makes the interface hang, it just makes the kernel hang (but that's fine)
** We can use notebooks as modules (probably way nicer than the PythonSource module)
** We can run multiple kernels so long as the ports carry things that are serializable
*** meaning we can put the multithreaded-interpreter without all the hacky parts it has now
*** we can run IPython kernels in all the languages IPython supports, [https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages currently 46]

=== July 8, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Buildbot github hook not working after IP address change
* [TE] No reference to VistrailsApplication ([https://github.com/VisTrails/VisTrails/issues/1103 #1103])
** [RR] Added PR [https://github.com/VisTrails/VisTrails/pull/1104 #1104]
* [TE] Reopening VT file after saving with bundled subworkflow won't offer subworkflow upgrade ([https://github.com/VisTrails/VisTrails/issues/1102 #1102])
** allow manual delete to fix right now
** fix this on top of the use-uuid branch
* [TE] Release VisTrails 2.2.1? ([https://github.com/VisTrails/VisTrails/blob/v2.2/CHANGELOG CHANGELOG])
** [https://github.com/VisTrails/VisTrails/pull/1093 output-modules-use-global-dir]
** [https://github.com/VisTrails/VisTrails/milestones/version%202.2 Current issues for 2.2]

=== July 1, 2015 ===
'''Updates'''
* [TE] PROV fixed
* [TE] Working on subworkflow issues
* [RR] Considering reworking the controller (log vs exception problem, retained upgrades causing interferences) and also the interpreter (IPython?)

'''Items to Discuss'''

=== June 24, 2015 ===
'''Updates'''

'''Items to Discuss'''
* UV-CDAT
* [TE] Can a cyclic workflow be valid? ([https://github.com/VisTrails/VisTrails/issues/1097 #1097])
** focus on disabling the ability to create cyclic pipelines because more things break than just this with a cyclic pipeline
* [RR] Relative paths ([https://github.com/VisTrails/VisTrails/pull/1057 #1057])
** This interacts with the new bundle; how do handle packing files inside the VT bundle?

=== June 17, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] current_version and reusing existing upgrades are broken ([https://github.com/VisTrails/VisTrails/issues/1095 ticket #1095])
** Could be that export to PROV is using an unflushed upgrade pipeline?
** current_version would then be correct.
** It may work to flush the actions before exporting?

=== June 10, 2015 ===
'''Updates'''
* DAT: fixed VTK issue on Linux and Mac
* Still crashes on Windows. Need help! Reminder: this works in the VisTrails spreadsheet (QCellPresenter), although no widget get changed there during a drag
** Is it a VTK bug?
** Is it simply impossible to change widgets during the drag, should we do it a different way?
** Did I miss something that is done in VisTrails but somehow not in DAT?
** Low prio, UV-CDAT doesn't run on Windows anyway

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 Updated pull request])
* Single instance code and batch mode

=== June 3, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 pr])
** Requires fixes to command line parameters, Output modules, and batch mode
** How to test this
** Updated missing/outdated flags
** Fixed view issues when generating graphs
* [TE] batch mode
** SpreadsheetOutput not enabled in batch mode. Should we check is_running_gui instead?
** Other instance setting flags from caller
** Is graphsAsPdf replacing spreadsheetDumpPdf?
** graphsAsPdf true by Default?
** Batch mode executing by default (Not needed when generating graphs)
** Re-added workflowInfo as withWorkflowInfo for writing graph and xml workflow
** [DK] batch mode should be outputting to files or stdout, shouldn't always trigger SpreadsheetMode
** execute flag, maybe make execution the default and allow a "--no-execute" if you only want to capture graphs, for example

=== May 27, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] API question
** http://lists.vistrails.org/pipermail/vistrails-users/2015-May/000357.html
* Status of DAT
** Can add VCS plot to DAT but need to work on configuration windows
** Documentation for graphics templates for UV-CDAT/vcs?
* Qt support?

=== May 20, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Reviving the DAT, integrating scripting & porting UV-CDAT!
** On [https://github.com/VisTrails/DAT GitHub] ([https://github.com/VisTrails/DAT/issues issues])
** Merging 2 years of development taking longer than expected, but getting there. The plan is to get the patches in VisTrails and never fork again, we never want to get in UV-CDAT's situation (and don't need to).
** VTK cell works fine on Linux but there was flickering on Mac & Windows before; still issues on Mac (Windows status unknown)
** Can get a VCS plot soon (but will need VTK cell fix)
** Integrate in UV-CDAT's build system (so we have cdms, VCS, ...) -> RR can do this, low priority
** How do we integrate scripting?
*** We want to be able to seamlessly make changes to a plot by changing Python code
*** Define new plots by entering Python code without writing modules/packages?
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 13, 2015 ===
'''Updates'''
* [RR] Test skipping whitelist ([https://github.com/VisTrails/VisTrails/pull/1069 #1069]) -- low priority
* [RR] Custom matplotlib modules can't be compatible with both 2.1 and 2.2 ([https://github.com/VisTrails/VisTrails/issues/1067 #1067]); should be fixed for ALPS ([https://github.com/VisTrails/VisTrails/issues/1070 #1070])

'''Items to Discuss'''
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 7, 2015 ===
'''Updates'''
* [RR] Export/import workflow to Python working!

'''Items to Discuss'''
* [Claudio] UV-CDAT
** The UV-CDAT project is the biggest user base of VisTrails
** VisTrails package management provides a lot of friction towards people plugging in their code
** Need to make it easy to integrate your random Python scripts in the system without having to deal with all the boilerplate, at least in the first step
** [RR] argues that modules are still good; UV-CDAT shouldn't move towards a purely script-based backend
** [RR] export/import with Python could reduce a lot of that friction by allowing 1) to edit workflow as Python 2) to open up boxes automatically if needed code doesn't match actual modules
** ...

=== April 29, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] <strike>Abstractions</strike> subworkflows status ([https://github.com/VisTrails/VisTrails/labels/subworkflows tickets])
* [RR] matplotlib compatibility (2.1 & 2.2), [https://github.com/VisTrails/VisTrails/issues/1067 #1067]
** RR to try and fix ALPS matplotlib modules

=== April 22, 2015 ===
'''Updates'''
* 2.2.0 has been released!
* Windows issue (via email from Ryan)
** issue with manifest file (may be a new file in VTK6?)
** Tommy has regenerated new Windows builds
* Binaries, pypi, and conda released
* [RR] Export as script
* Python sources using VTK need to switch to SetInputData (users should be aware of this)

=== April 15, 2015 ===
'''Updates'''
* Ready for 2.2.0 (apart from binary/deps issues)
** Missing some libs (scikit-learn, tej, tdparser, SQLAlchemy+connectors
** Windows: runvistrails.py is no longer used, so the PATH is wrong
** Windows: pip is broken, but it probably wouldn't work anyway because of permission issues (disable this?)
* Queries, upgrades and getPipeline() usage ([https://github.com/VisTrails/VisTrails/issues/1054 #1054])
** Getting a pipeline with getPipeline() is not safe: it might return an invalid pipeline
** This is used in many places throughout the code, like queries
** Upgrading would require going through the controller, but that creates new actions
* [TC] Avoid copying a module's output if it's used as input by exactly one downstream module ([https://github.com/VisTrails/VisTrails/issues/1060 #1060]) (useful for big numpy arrays you can update in-place)

=== April 8, 2015 ===
'''Updates'''
* [DK] Merged RR's changes for output modules (1012 and 1013)
** RR will merge remaining changes, then create v2.2 branch!

'''Items to Discuss'''
* BNL need numpy array to VTK image
** Looks like VTK has some helpers for this
** We will help if issues arise
** Will contribute back to VisTrails package
* Upgrade issue: [https://github.com/VisTrails/VisTrails/issues/1017 #1017]
** Automatic upgrades should happen between versions of provided upgrades
** Our existing upgrades work around this so it doesn't need to be 2.2.0
* Corner-case VTK modules
** No longer need VTKCell input port, so don't interfere with registry and API anymore
** Still work weirdly, people probably shouldn't use them
** But we have lots of clunky modules since we wrap the whole of VTK; some people might rely on this and know how to use them, let's keep them anyway
** Ready for 2.2.0

=== April 1, 2015 ===
'''Updates'''
* [RR] UV-CDAT: bugfixing for 2.2, long-term plans: implement scripting import/export in VisTrails, port to UV-CDAT
* Possibly, try to move to regular VisTrails to use new features

'''Items to Discuss'''
* 2.2 release: nothing much is pending anymore, release next week?
** [TE] vtkExporter classes [https://github.com/VisTrails/VisTrails/issues/1032 #1032]
** [RR] Hiding upgrades in version tree might make it (or might be 2.2.1 so we can test it out) [https://github.com/VisTrails/VisTrails/issues/949 #949]
** Output modules changes to go in
* add note to documentation about order of parameters in VTK
* add issue about exporter upgrades if not already there

=== March 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* 2.2 release
** Checklist on Github: https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist
** Review output modules
** RR has a couple more issues to fix
** Ready to go -- sign app package for OSX? [https://github.com/VisTrails/VisTrails/issues/984 #984] We need access to the Apple Membership team

=== March 18, 2015 ===
'''Updates'''
* [TE] VTK6 works

'''Items to Discuss'''
* [RR] Release v2.1.5 with backported tabledata?
** MTA example needs updated tabledata (for JoinTables)
** Google Maps package still not available
* [RR] Work torward v2.2.0?
** changes:
*** new persistence
*** API changes
*** output module changes (upgrades?), maintain cells but try to upgrade
*** not wrapping stuff
*** VTK6? yes
*** JobSubmission stuff?
*** relabeling for upgrades [https://github.com/VisTrails/VisTrails/issues/949 #949]
** makes sense, needs the tree view code to be updated, check selection
** See [https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist 2.2 checklist]
* Discussion of [https://github.com/VisTrails/VisTrails/issues/1016 #1016]
** plumbing between outputs and output modes, how to define a mode that works for many outputs without writing for each output?

=== March 11, 2015 ===
'''Updates'''
* [RR] persistent_archive done; merge? ([https://github.com/VisTrails/VisTrails/pull/755 #755])
** note about the focus events for widgets
** TE be aware of file_archive for future binaries that include persistent_archive
* [TE] [https://github.com/VisTrails/VisTrails/pull/998 New VTK package] finished

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails? (see last week; decision needed)
** RR email to JF about this
** yes; email sent to Github
* [RR] Switching order of output ports ([https://github.com/VisTrails/VisTrails/pull/1006 #1006])
** added port specs are sorted at a separate spot (Module.*_port_specs properties) than those in the registry (which are sorted in the registry), but those two lists are just combined without respect to sort keys
** need to determine whether the two lists should be merged or remain distinct
** should make sure that order of input ports and output ports makes parallel connections for things with same order
** DK suggests breaking backward compatibility here: workflows still run, can fix easily if a problem in an existing package.
* [RR] Question about output modes ([https://github.com/VisTrails/VisTrails/pull/1007 #1007]), how to integrate in API ([https://github.com/VisTrails/VisTrails/pull/24 #24])
** Should ImageFileMode be removed? ("image" is not a mode, "file" is)
** ImageOutput missing?
** Feel free to change how formats works
* [TE] Test suite segfaults on Fedora 17 virtualbox. Install newer version? (Support ended in 2013)

=== March 4, 2015 ===
'''Updates'''
* [TE] VTK wrapper
** Works on VTK 5.10
** Still need to test VTK 6
** New general wrappers for python functions and classes

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails?
** When [http://i.imgur.com/UTY2qfg.png filing a pull request] from UV-CDAT/VisTrails, VisTrails/VisTrails is selected by default
** People keep forgetting to change the default ([https://github.com/VisTrails/VisTrails/pull/956 #956] [https://github.com/VisTrails/VisTrails/pull/968 #968] [https://github.com/VisTrails/VisTrails/pull/999 #999] [https://github.com/VisTrails/VisTrails/pull/1000 #1000] [https://github.com/VisTrails/VisTrails/pull/1003 #1003] [https://github.com/VisTrails/VisTrails/pull/1004 #1004] [https://github.com/VisTrails/VisTrails/pull/1005 #1005])
** Only way to change that is to not have it marked as a fork of VisTrails/VisTrails
** Github staff [https://gist.github.com/remram44/b364c24ef1e462ce6e2f can make that change for us]; should we do it?
** Juliana: comments on this? visibility vs. convenience/annoyance for developers
* [RR] What about [https://github.com/VisTrails/VisTrails/issues/991 #991]?

=== February 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] vtkviewcell for infovis support, can we unify with VTKCell?
** need to test this
* [TE] vtk wrapping
** Mostly finished
** VTK 5.10 produce incorrect results with old wrapping
*** Old wrapper is based mostly on VTK 4
*** Most vtk_examples affected
*** [http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Replacement_of_SetInput]
*** should be able to upgrade from SetInput to SetInputData (need to drop GetOutput and replace with self ports)
*** can we change vtkInstance to just return self and not wrap things
** terminator example not working under 5.8?
* How does VTK wrapping fit into general wrapping framework?
* [RR] new persistence package

=== February 18, 2015 ===
'''Updates'''
* [RR] New VisTrails API and IPython integration ([https://github.com/VisTrails/VisTrails/pull/24 #24])

'''Items to Discuss'''
* [TE] VTK wrapping
** [https://gist.github.com/rexissimus/16b74693545b5e7c1035 Benchmarking vtk package]
*** Old: 24.7 seconds
*** New: 10.5 seconds (Except first time that adds 8 sec)
**** The parsing that calls is_abstract (that tries to instanciate all vtk classes) is now only run the first time.
**** get_items_from_sigstring takes 2 seconds, maybe we can use a lookup dict for already computed sigstrings?
** Now using a general python function wrapper
*** VTK classes are wrapped into python function that does not depend on vistrails
*** VTK functions can be executed without vistrails
*** The spec maps functions into vistrails modules, but can also describe wrapping
*** A general python function wrapper that supports
**** kwarg inputs
**** single, list, dict outputs
**** callback for progress reporting
**** temporary file generator for using FilePool
**** optional output generation
*** Creating specs:
***** Create spec by hand
***** Auto-create spec outline (TODO) and manually finish it
***** Dynamically create spec (VTK)
***** Implement documentation wrappers (Can use scikitlearn wrapper to wrap numpydoc) (TODO)
***** Classes as bad functions needs to be wrapped in new functions before they are wrapped. This is different for each package.
****** Classes is hard: Like VTK, and matplotlib. Scikit-learn does still not wrap classes
***** Spec diffing and patching could be done using code from matplotlib.
** Still needs upgrades from old VTK package
*** Is it possible to dynamically wrap functions, e.g, you see a SetFunc and just remove the 'Set' prefix. Or do you need to create a complete mapping?

=== February 11, 2015 ===
'''Updates'''
* Update from Friday's meeting
** discussed VisTrails internals
** discussed wrapping
*** xml discussion, hard to modify because tied to db code
*** TE has made it possible to add the schema-defined attributes to the intermediate representation
*** higher-level operations on the port specs
** make sure the simple case works
*** [JF] take a simple package with documentation and figure out what the base case for wrapping is

'''Items to Discuss'''
* [TE] VTK wrapping
** Dynamic loading works
** Reading XML is fast enough, but [https://gist.github.com/rexissimus/8272d3c776ccfa115d82 unserializing data is slow]
** Working on patterns for patching
** Matplotlib has many advanced patterns like argument ordering, nested arguments, alternateSpecs, output types.
*** Having all this in a general wrapper might confuse users?
** [RR] Delay module (except for identifiers) until you need it---e.g. don't deal with port specs, etc. until necessary
* Scripting Support [https://github.com/VisTrails/VisTrails/pull/950 #950]
** [RR] Issue with getting code from modules
** Design a simple solution
** [JF] Couldn't you use modules as black boxes without conversion, just to call into modules/subworkflows easily from e.g. IPython?
*** [RR] This is a job for the API, and a very separate use case. See [https://github.com/VisTrails/VisTrails/pull/24 #24]

=== February 4, 2015 ===
'''Updates'''

'''Items to Discuss'''
* Wrapping
** Format to use? Currently XML (like current matplotlib)
*** JSON and YAML have simple "to python dictionary" methods
*** But don't stream
*** YAML a lot easier for humans
** [DK] vtk-new-package also changes parameter names, creates enumerations
*** intermediate schema needs to be extensible
*** packages will want to store there specific infos for compute() method generation
*** also might have specs-altering info, like matplotlib's alternateSpec
** representation to code , registry already has schema for some aspects
** [RR] We might want to see if Module subclasses can be created lazily
*** no need to create all the classes just to register them in the registry and never actually use most of them
*** future effort
* [RR] Where should VisTrails packages live?
** tej installs as 'vistrailspkg.tej', TE installed it as 'userpackages.tej'
** Currently, standard packages are 'vistrails.packages.', user packages are 'userpackages.' and packages loaded through pkg_resources might be anything
** [RR] Use 'vistrailspkg.' everywhere?
** Long-term effort to simplify package distribution/installation (and have VisTrails get them automatically?)

=== January 28, 2015 ===
'''Updates'''
* T. Caswell to come visit on Fri 6 to discuss wrapping work

'''Items to Discuss'''
* [TE] New VTK wrapping
** Current code by DK seems a good deal faster
** Generates XML that can be patched/tweaked, generates Python code from it, VisTrails only loads generated Python code
** RR would rather have VisTrails load intermediate representation (= XML) directly, wants to make sure this is not slower
** The goal is to turn the intermediate step into something generic that would be used for every wrapped package (vtk, numpy, matplotlib, sklearn, java) instead of each having its own
** TC has its own code at [https://github.com/Nikea/VTTools/blob/master/vttools/wrap_lib.py github:VTTools] which parses numpy docstrings and generates modules, doesn't yet handle classes or persist anything
* Web crawler
** Right now, TE starts jobs for "start crawler", "stop crawler", "install classifier"
** RR would rather have the crawling be a job as far as VisTrails and tej are concerned
** The whole thing would be one pipeline: load examples, train classifier, start crawler [check for job, kill previous one, upload model, start processes], get snapshot, visualize
*** Need some support in tej and job submission system: long-running jobs, stop a job (wait for it to finish?), restart a job even though results are cached

=== January 21, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Unified wrapping method discussion [https://github.com/VisTrails/VisTrails/issues/991 #991]
** TE to work on reusable method with intermediate representation, starting with VTK
* [RR] Examples for scikit-learn: JF has an old example using Weka with parameter exploration (not currently in source tree)
** AM's examples are enough
* [AM] scikit-learn package is done, merge it in? [https://github.com/VisTrails/VisTrails/pull/955#issuecomment-70286788 #955]
** RR will merge
* [RR] What should copyright headers say? [https://github.com/VisTrails/VisTrails/pull/994#issuecomment-70173935 #994]
** Let's keep everything in there: Utah/Poly/NYU

=== January 14, 2015 ===
'''Updates'''
* [TE] Working on classifier
* [RR] Scripting integration, work in progress

'''Items to Discuss'''
* [RR] Unified wrapping method discussion ([https://github.com/VisTrails/VisTrails/issues/991 #991])
** Let's talk next week, [AM] and [DK] are not here

=== January 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* make sure that we address critical issues, questions, and pending review branches in a timely manner
* scripting support
** [RR] no issues if we want to just keep annotations in the generated code to allow the link back to a workflow
** [RR] can translate from workflow to script, working on script to workflow
** will work for parameter value changes, structural changes require changes to the annotations
** need to publish best practices here
** would be cool to do looping in scripts (easier interface than with workflows)
* notebook support (convert form notebook to workflow)
** RR will sync with FC on this
* Issue with console in built-from-scratch
** [TC] iPython rearranged some of the completion stuff in 2.2 and 2.3
** binary has old version of iPython -> 1.0.0, should we update?
* [TC] automated wrapping of numpy and scipy
** discovered a bunch of malformed documentation in numpy and scipy
** has github repo for vistrails tools
** example modules wrap a bunch of R stuff (not baked in, just how things are)
** will be pushing wrapping logic up
** port names forbidden (window and domain)
** have an import hook to get from yaml directly to VisTrails Modules
** should work for any python modules with well-formed numpy docstrings.
* [Action] should make it clear in documentation that Constant now means serializable not that the value doesn't change (e.g. List)
* [TC] might be interesting to try to build components of matplotlib and accumulate in figure (long-term project, but thinking about how this might work)
* [TE] build and build scripts
** completely automatic, buildbot
** need to set the build machines for the environment we want for the binary
** would virtualenv work here?
** [TC] anaconda can pin versions, potential path to test different configurations
** Q: upload nightly binary builds? A: makes sense, make sure they are well-labeled
* sourceforge stats: e.g. http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07
* package issues (see Remi's message)
* [TE] Scope of tej
** Support single ssh commands?
** Queue can be used as a remote machine (crawler is using queue.call*)
* SourceForge stats: http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07

== Older meetings ==
* [[Development/2014]]
* [[Development/2013]]
* [[Development/2012]]
* [[Development/2011]]
* [[Development/2010]]

Development

2016-07-13T15:00:19Z

Tommy: /* July 13, 2016 */

<div class="nonumtoc toclimit-1">
__TOC__
</div>

See also the [https://github.com/VisTrails/VisTrails/wiki/Development Github wiki]

== 2016 ==

=== July 13, 2016 ===

'''Updates'''

'''Items to Discuss'''
*[TE] Simplified running module using API for scripting [https://gist.github.com/rexissimus/b28d83ae516a519167f5751bb8ab3739 example]
** API Module can be executed using '''compute''' method
*** Takes list of outputs to compute + inputs as keyword arguments

=== July 6, 2016 ===

'''Updates'''

* [DK] Working on bundles

'''Items to Discuss'''
* [TE] Using vistrails API in scripting [https://gist.github.com/rexissimus/034d9c4dedc3299a079e84981dedd8c7 example 1 (API with VTK)] [https://gist.github.com/rexissimus/a4a9ca6c08d4058c64967d2b35415fd5 example 2 (DownloadFile only)]
** Call module in script using vistrails API
** Can be used when no export method is defined.
* [TE] [https://github.com/VisTrails/VisTrails/commit/c76c109349769fee1280f85c22678380a2f9cd39 Server news bug] Critical?
**[RR] No, unreleased
* [DK] New bundle organization
** BundleMapping contains individual mappings from raw objects to BundleObj
** Must be separate in order to have in-memory, separate from serializer settings

=== June 29, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Export VTK as python script
** Works on Terminator (Isosurface, Volume Rendering, clipping plane, combined rendering) [https://gist.github.com/rexissimus/16caf5200802e150296f62a0c7844c5a example]
** Preludes (imports) still need improvements
** Works with vtkInteractionHandler (clipping plane)
** Resulting clipping plane is incorrect? (supposed to hide one side of the plane)
** vtkRendererOutput Uses VTKRenderWindow as output
*** Should support different output modes?
*** Does not work with multiple outputs (Next cell is displayed when current is closed)
*** Uses wrapped vtkInstance (as vvtk)
**** Create new patch system with code that can be used both in vistrails and in a python script?

=== June 22, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Fix for upgraded analogies (PR [https://github.com/VisTrails/VisTrails/pull/1177 #1177])
** Uses module location to find module remap (The best we can do right now?)
** Also fixes remapped port names for connections to existing modules
** May still fail on complex upgrades like adding a function on an upgraded module that has a different port name

* [TE] Working on exporting wrapped libraries (VTK)

=== June 15, 2016 ===

'''Updates'''
* [TE] Added depth logic to python script exporter ([https://github.com/VisTrails/VisTrails/commit/50f220e4f6abe5a7bb8689f73f456f43df2dbc12 full commit])
** Fully implements connection merging and list looping

'''Items to Discuss'''

* [TE] Making analogy work on upgraded workflows ([https://github.com/VisTrails/VisTrails/issues/1175 #1175])
** Analogy only works We need to use the non-upgraded action chain
** But pipelines need to be valid (matcher uses module portspecs)
** Tried to get upgrade remap from upgrade action, but this seems impossible
** Use module location instead?
*** Location should be identical for one-to-one module upgrades

=== June 1, 2016 ===

'''Updates'''
* VisTrails 2.2.4 announced (finally)
** 5 survey replies
** 47 downloads last week

'''Items to Discuss'''
* [TE] Export VTK as script (python-wrapper)
** to_python_script
*** needs the pipeline (or at least the connections)
**** Should not generate code for any possible VTK method (exporter detects which ports is used in the source)
**** VTK needs to know connection order
**** Adding functions directly to the script results in nicer code
** Add support for multiple input connections
** Add support for list looping

=== May 25, 2016 ===

'''Updates'''
* Mailing-list fixed
* Getting stats from the "server news" mechanism (via [https://github.com/remram44/apache-log-info parser])

'''Items to Discuss'''
* [RR] Alexis doing writeup on VisTrails, curious about interesting streaming use-cases (and potential future users)
* [TE] Union ports
** Show union ports in pipeline (DEMO)

=== May 18, 2016 ===

'''Items to Discuss'''
* [TE] mailing list still down - Julio working on it
* [TE] Improved union port
** New schema 1.0.5 adds portitem.union string attribute
** Works with pipeline view, parameter exploration view, and mashup view
** Should work well for matplotlib
** Use with VTK ports?
*** It uses [item_1,item_2] style ports usually with different tuple length.
* [TE] Remove emacs dependency from db generate [https://github.com/VisTrails/VisTrails/issues/1173 #1173]

=== May 11, 2016 ===

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]
** GUI-based solution [https://github.com/VisTrails/VisTrails/tree/union-port Branch union-port] Demo?
*** Shows single port for all ports with same sort_key
*** Select specific type when adding/showing
*** Only one type should be visible on the module at any time
*** Making tuple parameters union types is probably too complicated
*** Should work with alternate specs like matplotlib (if sort_key is defined correctly)

* [TE] Feature suggestion: Let connections connect to functions/parameters
** Show functions and parameters as ports and toggle port visibility directly for functions and parameters
** Use separate views for ports and functions (like before)
*** Allow rearranging of functions
** Pros:
*** Supports ordered connections. Create 2 functions, make them visible as ports, make connections to them.
**** We can also have, e.g., a line joining the ports on the module to indicate they are part of a list.
**** Makes List module simpler
*** Connect to parameter in tuple
*** Functions that are visible on the module can connect to an actual function, and not just to the first one it finds.
*** Can replace operation modules (in python-wrapper) in some cases for, e.g., numpy.
** Cons:
*** Interface more complicated and crowded
*** More difficult for users to grasp?
*** No immediate use case
*** Makes no union type for tuple parameters a bigger problem.

* [TE] Publish user survey?
** No response from vistrails release yet
** Not announced on vistrails-users yet.

=== May 4, 2016 ===
'''Updates'''
* VisTrails 2.2.4 released

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]

=== April 27, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Wrapping Bokeh
** New method type "operation"
*** Transforms Figure->Glyph->Output into Glyph->Figure->Output
**** Glyph sets function name and arguments as output
***** Not serializable, but should always be computed together with the subject of the operation.
**** Figure applies Glyph operation on itself
*** Useful for matplotlib?
**** matplotlib currently find actors by searching upstream?
**** But this is more difficult since matplotlib is not function-based.
** New "union" port type
*** Turns "x(float), x(list)" into "x (float, list)" and uses first set value
**** Uses only first value in tuple
**** Bokeh have many properties that support (list, string, Float)
*** Does not work with depth=1 types (e.g. Float of depth 1)
**** Turn Depth 1 types with known type into lists?

* [TE] New bugfix release
** Finalize survey

=== April 20, 2016 ===
'''Updates'''
* Merged upgrade fixes
** Now has infinite loop test
** loop test now correctly loops 5 times
*** remap_module used wrong (current) package version when creating ModuleDescriptor
* Fixed multi-step group upgrades (PR: [https://github.com/VisTrails/VisTrails/issues/1168 #1168])

'''Items to Discuss'''
* New bugfix release
** Merge usagestats
** Need to finalize survey

=== April 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Chaining upgrades done ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Replace "Upgrade" description annotation with "upgraded_from" annotation to identify which tags to hide?

* [TE] Iterating handle_invalid_pipeline ([https://github.com/VisTrails/VisTrails/pull/1165 #1165])
** Not based on [https://github.com/VisTrails/VisTrails/tree/chain-upgrades-loop chain-upgrades-loop]
** Cherry-pick test to preserve source?
** Need maxPipelineFixAttempts option?
*** The code is now smarter about recursion, so max attempts will "probably" never be reached.
** Need [https://github.com/VisTrails/VisTrails/commit/0ef0667426937eddb1d1c1e397f0657ffec039a9 debug messages]?
*** Would need to be moved into handle_invalid_pipeline

=== April 6, 2016 ===
'''Updates'''
* [TE] Query View improvements
** Done except for displaying "Version Info" and #1164
* [RR] Working on finishing new interpreter (finally!)

'''Items to Discuss'''
* [TE] Chaining upgrades ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Try latest upgrade first, then previous.
** If all fail, select latest upgrade?

=== March 30, 2016 ===
'''Updates'''

'''Items to Discuss'''

* [TE] Query View improvements
** Unified do_version_switch and get_upgrades as validate_version()
** Problems with query view using its own controller
*** Fixed module info not being displayed for query results
*** Still no version info for query results
*** Still an issue with version query view not being updated

=== March 23, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Usage reporting almost ready to go
** Need to record whether specific features are used: paramexpore, mashup, query
*** [DK] Record if LaTeX extension is used? But hard to distinguish from direct batch invocation
** How to record size of vistrail?
*** [DK] IdScope already walks over vistrail, use that
*** but total number of modules and versions doesn't give an idea of average size of individual pipelines

=== March 16, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Upgrades in Query Mode
** Now using code similar to do_version_switch
*** Uses handle_invalid_pipeline
*** Differences: Not using current_pipeline, flushes changes
*** New controller method get_pipeline optimized using cached pipelines (but not current_pipeline)
*** Integrate to avoid repeated code?
*** Use this for query mode?
* [TE] VisTrails 2.2.4 ready for release?
** tej package updated. Others?
* [JF] upgrades and the version tree
* [JF] provenance in Jupyter
* [DK] bundles: [https://github.com/VisTrails/VisTrails/pull/1092 #1092]

=== March 9, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixing search mode
** String query now matches all by default
*** This caused pipeline queries to never match
** String query can search: User/Notes/Tagname/Time/Module name
*** Should we search module names by default? (Disabled by default because it is expensive)
*** Fixed notes search
** '>' parameter queries in documentation but has been removed
** Fixed module matches for upgraded pipelines (By not upgrading pipeline)
*** Upgrades still a problem
*** Add "Upgrade all menu option?" (Or upgrade all on open when `hideUpgrades`)
*** [JF] Allow search on past tags

* [TE] Create new bugfix release
** Finish querying
** Path issue on windows

* [DK] Look into sqlalchemy and new bundle branches

=== March 2, 2016 ===
'''Updates'''
* [TE] Fixed cache bug with port specs
* [TE] VisTrails Next
** Most packages now work
** No qgis for Python 3

'''Items to Discuss'''
** Always dereference symlinks? [https://github.com/VisTrails/VisTrails/issues/1146 #1146]

=== February 23, 2016 ===
'''Updates'''
* [TE] Fixed PythonSource 100% CPU bug
* [TE] VisTrails Next
** Updated [http://opendap.co-ops.nos.noaa.gov/axis/webservices/wind/ NOAA Web Service] examples
*** Now uses REST service, tabledata, and Google Maps
*** Web Service replaced with DownloadFile

'''Items to Discuss'''
* [RR] Couple of fixes are in for API, and tej&reprounzip on the Mac binary. Also new release of tej, and working on anonymous usage reports.
** New 2.2 release soon?
* [RR] Anonymous usage reports
** Sends out info like number of modules & versions, packages used, Python & libs versions, execution time, specific features [https://github.com/VisTrails/VisTrails/pull/1154 #1154]
* [JF] Bring in noWorkflow to track variable dependencies, for the considered Jupyter integration?
* noWorkflow - provenance for python scripts
** Recent work on tracking dependencies
* Also integrates ReproZip with Jupyter
** [http://mybinder.org mybinder]
*** Use with ReproZip to automatically build Jupyter notebook interfaces
* Daves comments on Jupyter integration
** It is possible to identify cell order on the server side
** Not trivial to track order of cells on client side
* How does Galaxy workflows relate to VisTrails?
** Packaging in Galaxy is hard
** Galaxy for biomedical workflows, difficulty making it general
* Action items
** How difficult to track cell dependencies in Jupyter notebooks?
** Use noWorkflow to track cell dependencies?
** How difficult to modify mybinder to use ReproZip packages?

=== February 17, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixed Group memory usage
** Modules in groups are supposed to be freed when done executing
*** Prevented by logger that stored references to the modules (fixed, now using id(module))
*** Prevented by list iterator bug that stored list of modules on the 'self' port bug (fixed)
* [TE] VisTrails Next
** Removed deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** PythonSources will be upgraded
*** Fixes for Python < 3
*** fixes for VTK < 6
** TODOs
*** Remove RemoteQ
**** Port Hadoop to tej (Already have pbs)
*** Merge package wrapper
*** Finish SQLAlchemy branch
*** Finish new bundle branch
** [JF] Will contact Jeff and Matthias about moving to Python 3
* [JF] Query by Example is broken
* [JF] VisTrails Data Cleaning Project
** Use VisTrails to process and explore task-specific data while keeping provenance.
** Remi's Idea
*** Use VisTrails as the backend in a Jupyter notebook
*** Overcome problems with executing cells in random order
**** Interesting research topic, but little interest has yet been noted
*** Interesting to study how such a notebook would be used (Is there notebook usage data available?)
*** Impose restrictions to notebook cell boundaries
*** It will only work for functional operations
*** Can we fix, or detect, non-functional (mutating) operations?
*** Analyse code and data flow and see if it mutates data in unexpected ways?
*** Mutable operations can be created in many ways in Python
* Next meeting Tuesday 11:30

=== February 10, 2016 ===
'''Updates'''

'''Items to Discuss'''
* VisTrails Next
** Test suite passes
*** Python 3 less deterministic, module upgrade order random.
** [RR] updating packages: Reprounzip (pushed), tej, persistent_archive, ...
** All of our packages should run fine :)
** VTK thumbnail comparison works
*** Rendering bug on some systems
**** QVTKCell now inherits QGLWidget
*** Old thumbnails had wrong height due to spreadsheetwindow being too small
**** Fixed by regenerating thumbnails
*** Silenced deprecation messages when generating modules
*** Many new classes in VTK 7
** Remove deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** Will break existing PythonSources
**** Try to upgrade?
*** Old-style packages
**** Or only allow a new style, like __init__.py renamed to info.py? (merge with identifiers.py?)
***** Read info.py without importing package?
*** Fixes for Python < 3
*** Fixes for Qt < 5
*** fixes for VTK < 7
*** Remove self port?

=== February 3, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] [http://lists.vistrails.org/pipermail/vistrails-users/2016-January/000402.html Rendering a .pvd (ParaView) file?]

* VisTrails Next
** All tests but thumbnail comparison passes
** Still issues with gui and more packages needs to be tested
** PythonSource and MplSource upgraded with lib2to3
** Keep contrib packages? Update?
** [https://blog.kitware.com/vtk-7-0-0/ VTK 7 is released]
*** Supports Python 3
*** Will hopefully get into conda and others soon
*** Deprecates a bunch of modules

* [https://travis-ci.org/VisTrails/VisTrails/builds/106743348 Travis builder] for VisTrails Next
** Runs!
** Uses conda
*** Many levels of requirements
**** apt packages
**** conda packages
**** python packages in requirements.txt
**** python packages in setup.py
*** Can probably drop conda. Default builder does not have Qt5, but beta builder do!
*** But useful if we want to use conda in our own build process.
** Lots of errors I do not get locally?

* [http://goo.gl/forms/Z4HBrwaBWL User Survey]
** Have you used any alternatives to vistrails?
*** Relevant? More options?
** How often do you use any of these particular features in VisTrails?
*** Add/Remove alternatives?
** How important would you rank the following potential improvements to VisTrails?
*** Add alternatives?

=== January 27, 2016 ===
'''Updates'''
* New interpreter
** Working prototype soon
** Looping not completely done (and port combination mode: pairwise/cartesian...)
** Need to integrate with VisTrails
*** Compatibility with existing modules
*** Use log controller
*** Want to cache at multiple levels (whole stream/single element of stream)
*** Non-runtime attributes of modules (cache check, automatic conversion check, constant from/to string)

'''Items to Discuss'''
* User Survey

* ZMQ failing on windows (vistrails-users)

* [TE] [https://github.com/VisTrails/VisTrails/pull/1143 Python 3 branch]
** Testsuite almost passes
*** Failing are unicode filenames, some users guide examples, and thumbnail comparisons.
** Fixed issues
*** Signatures are now bytes (convert to string to show in widget)
*** Cannot compare different types, e.g., (None < 1)
**** PortSpec.depth and min/maxConn could be None. (Backport!)
**** cell.row could be None
*** Lots of unicode/bytes fixes to serializations
**** We have encryption implementations in the code! (keychain)
*** Lots of small fixes to package method differences
** Current issues
*** logging widget empty?
*** version tree signals messed up
*** provenance view legend icons black
*** Text do not fit in some widgets
*** VTK thumbnail comparison fails
**** VTK Cells have some faces in wrong direction?
**** Because running in VM?
** Installing on Ubuntu LTS/Latest Mint
*** Install latest matplotlib from pip
*** Install VTK 7.0.0rc2 from source
*** No QtWebEngine binary (controversial) (Must install sip/PyQt5/Qt5 from source)

=== January 20, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Backporting features from Python 3 + PyQt5 + Qt5
** Merged unicode with master ([https://github.com/VisTrails/VisTrails/tree/unicode unicode])
*** One unicode test failing
*** Problem saving to xml
** Used [http://python-future.org/ python-future] to run futurize stage 1 to update legacy (pre 2.6) code ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized unicode-futurized])
*** Updates print to functions 'from __future__ import print_function'
*** Updates exception calls to use 'as'
*** removes most usages of 'long' (mostly used unnecessarily)
**** Only needed for 32-bit support
*** Fixes relative imports (from __future__ import absolute_import)
** Fixing code that is deprecated in Qt 4.8 and removed in Qt 5 ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized-qt5 unicode-futurized-qt5])
*** Updated all signals to new-style
* If we go 2 to 3, this could break packages
** means we should schedule any package format changes for the same time
** e.g., imports should be unrelated to code path (function to load module from package identifier?) (take them out of vistrails.* [https://github.com/VisTrails/VisTrails/pull/1002 #1002])
** any structural changes (e.g. the __init__ versus init thing) (RR thinks it makes sense, though having both named "init" is unfortunate)
** putting package identifier as xml?
*** Python not so bad, plus some stuff in there is Python code (checking dependencies)
** version the APIs?
*** RR planning on versioning vistrails_module.Module, no point versioning the whole package?
* file formats on 2 to 3:
** no real translation/upgrade, but non-ascii values that work on 3 won't load in 2

=== January 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://gist.github.com/rexissimus/dfd27e466427529c385c Porting to Python 3 / PyQt5]
** Basic GUI and execution works
** Minimal work to support 2to3
** Hard to support both PyQt4 and PyQt5

=== January 6, 2016 ===
'''Updates'''
'''Items to Discuss'''
* Updating VisTrails dependencies
** Successfully built [https://gist.github.com/rexissimus/f1a1aada7de1c00a57c7 Win7-64/Python3/PyQt5/Qt5/WebEngine/VTK7]
*** VTK 7 is the first supporting Python 3 but is only in release candidate phase.
**** Next version of VTK 6 is rumored to support Python 3
**** There is a development branch of VTK 6 supporting Python 3
*** Can travis build this?
**** We can skip tests for WebEngine and VTK if needed
** Python 3 [https://python3wos.appspot.com/ showstoppers]
*** No MySQL-python (sqlalchemy supports mysql through other drivers)
*** No suds (there are active forks but we could also drop support?)
* Options for python2/3 support:
** Interpreter could be python2/python3 based on packages
** six layer works but not the easiest to maintain (e.g. in reprozip)
* Drop support for win-64
* Update copyright headers to 2016

== 2015 ==

=== December 30, 2015 ===
'''Updates'''
* Bokeh package finished
** Can output to Browser/IPython/Spreadsheet (Limited functionality in spreadsheet)
'''Items to Discuss'''
* Updating VisTrails dependencies
** Bokeh needs QWebEngine (Chromium) in Qt5 which requires PyQt5
*** Many plotting libraries only work in browsers
*** But Chromium may be a big and controversial dependency
*** Or create a browser version of the spreadsheet?
** Some users have requested Python 3
** Not backwards compatible?
** Target for VisTrails 3.0 with new interpreter?

=== December 16, 2015 ===
'''Updates'''
'''Items to Discuss'''
* Users list question
* [TE] Wrapping Bokeh
** Added bokeh property parser
*** complements numpydoc parser
*** Not all attributes are available, partially because I am using a pre-release version.
** Wrapped modules
*** bokeh.plotting finished (Backwards like matplotlib: Create plot then draw on it)
*** bokeh.charts mostly done (Missing arguments)
** QWebView mostly works (but no zooming or buttons)
*** It would be better to use external browser or QWebEngineView
** Added improvements to wrapper
*** Generalized port translations (Color/Path to native types)
*** Can use multiple docstring/property parsers simultaneously

=== December 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Looking into wrapper
** Will port TensorFlow
** Doing a pass on the wrapper code & doc
*** UX improvements
** Factorize high-level docstring parsers into core.wrapper? (sphinx, numpy, google)
** Problem with name vs module_name (fails sklearn tests because class_by_name() is broken)
** Looking into compressing specs, lazy registration of modules

=== December 2, 2015 ===
'''Updates'''
* [TE] Package wrapping
** Wrapped most of numpy/scipy using __all__
** Added class attribute and method access for classes (Can add to class or to separate inspector module)
** TODO: Document wrapping procedure

'''Items to Discuss'''

=== November 25, 2015 ===
'''Updates'''
* [RR] New interpreter is coming along
** Everything is a stream
** Task system, eventually work-stealing parallelism
** Streams no longer advance in lock-step
*** Allows for constructions like filter, join, sorted-merge
** depth>1 still to be tested, no current plan to allow this through the module interface
*** Through looping though, can do streams of streams

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapped most numpy functions (no polynomials)
** and half of scipy classes and functions
** Added functions manually from documentation (no parseable lists?)
** Focusing on data flow constructs (no property/method access for classes)
*** Using spec diff (empty for now) and dynamic parser (stores spec in .vistrails/)
** Python class/function wrapper now stable
** Add google doc parser?
*** Is there a parser available?

=== November 18, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Numpy class wrapping works
*** Basic type is List, since most types are array_likes.
*** TODO: More classes and functions
*** Some operations are in-place and some aren't, and docstring not super clear
*** [RR] It seems only methods mutate, and most have a numpy.xx function equivalent; just manually go through the methods and remove the mutating ones?
** Class wrapper is modular
*** Docstring parser and type string parser can be customized
*** Classes can have optional attribute/method ports
**** Inspectors and attribute/method modules can be created separately
** Use PythonCalc as an example
*** Can be re-implemented as a function with a parseable docstring
*** [RR] PythonCalc is just an example, and it might actually make sense to get rid of it, or do a proper math package with scalar operations (as separate modules, no combobox)
** [RR] TensorFlow to use wrapping as well
*** Very simple (only types 'tensor' & 'variable')

=== November 11, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapping numpy's classes using numpydoc (ndarray)
*** Wrapping constructor arguments, attribute getters/setters as module ports
**** Then how to access attributes afterwards?
***** Use input value port to class modules?
*** Wrap methods as modules? E.g., `ndarray.shape`.
*** Function wrapping is almost a subset of class wrapping
**** May be able to use the same parsing/execution methods
** VTK's non-getter/setter methods could be wrapped as modules
*** We could then remove extra logic in interpreter for keeping function order
** Bokeh uses autogenerated docstrings
*** We may be able to read the specification directly

* [RR] [https://github.com/VisTrails/VisTrails/pull/1138 TensorFlow package]
** Basic setup working, can execute the Mandelbrot example
** Will autogenerate the operations

=== November 4, 2015 ===
'''Updates'''
* [RR] Interpreter work requires a fix for [https://github.com/VisTrails/VisTrails/issues/1137 DB issue #1137]
* [DK] Kitware's Resonant [http://www.kitware.com/source/home/post/173]
** [https://github.com/girder/girder Girder]: data management system
** [https://github.com/Kitware/romanesco Romanesco]: execution engine, uses [http://www.celeryproject.org/ Celery] for task management
** Resonant Flow: web app for editing and executing workflows

'''Items to Discuss'''
* [TE] Added OSX Lion (10.7) VM on build machine using vagrant (seems ok with license?)
** New builds works on Lion
** Change the minimum requirement to 10.7?
* [TE] Package wrapping
* Added upgrade suggestions using 2 spec versions ([http://pastebin.com/30XUU8Gp example])
** using name edit distance to find matches
** Could use something better like port similarity for modules, and type similarity for ports
** Should write python upgrade code?
** Added spec to sklearn package
*** Can now diff spec versions and keep the spec static
*** There will be problems with downgrades and package versions

=== October 29, 2015 ===
'''Updates'''
* [TE] nightly-build-mac fixed (Needed to approve xcode license)

'''Items to Discuss'''
* [TE] matplotlib wrapper
** ported to general spec
** Diff can be used on general spec
*** Only needed minor changes
*** Fixed indexing bug that corrupted specs
*** Can now move diff tools to core/wrapper
** Add new plots?
*** New plots in mpl 1.3: eventplot
*** New plots in mpl 1.4: angle_spectrum, magnitude_spectrum, phase_spectrum', violinplot
*** No new plots in mpl 1.5 (from looking at boilerplate.py)

=== October 21, 2015 ===
'''Updates'''
* [RR] Alexis has arrived, will be working with [RR] on a more efficient interpreter

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package]
** Supporting multiple package versions
*** Check which version can be loaded [https://github.com/VisTrails/VisTrails/pull/1135 #1135]
*** We cannot show version requirements in the list of packages because old packages are loaded when importing the codepath
** Visual diff does not work well, but we can use the spec differ to see differences.
** Unifying vtk and matplotlib wrapping specs (WIP)
*** And porting matplotlibs spec differ to work on the general spec
*** Spec differ can then be used on vtk and other packages in the future
*** Will enable automatic upgrade generation
* [RR] Rework interpreter
** restore abstraction between interpreter/module code
** build looping, streaming, caching into the interpreter
** rework cache
** look into parallelism once basic functionality is there

=== October 14, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package] (adding numpydoc parser)

=== October 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/tree/fix-matplotlib-parser New matplotlib parser] (adding numpydoc parser)
** Added numpydoc attribute parser for plots.
*** TODO: Need better port spec reconciliation with call signature parser.
*** We can create a general numpydoc parser, but attribute types are unique to matplotlib.
** Needs package versioning
*** New spec will not support matplotlib < v1.4 due to changed path to axes classes.
*** Load spec version corresponding to installed matplotlib version?
*** Need version downgrades?

=== September 30, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Updating Matplotlib parser
** Matplotlib docstring parser fails on numpy docstrings
** I have [https://github.com/VisTrails/VisTrails/commit/eae8b0c16260810587e47c41cab53552cbb3cf0a added basic numpydoc parsing]
*** Only used by a few docstrings so far
*** Parsing uses many sources (class tables, signatures, ACCEPTS, method docstrings, definition parsing).
** Caswell said they were thinking about moving to traitlets, but this is not ready yet

=== September 23, 2015 ===
'''Updates'''
* [TE] VisTrails 2.2.3 released
** Also have pushed to PyPI, binstar, etc.
** Sourceforge vs. GitHub
*** should be able to host releases on GitHub
*** nightly binaries pushed to sf each night
*** old binaries?
* [TE] Re-wrapping MatPlotlib
** Keep static generation - Docstrings are brittle beween matplotlib versions
** Keep generating the executable classes - but create functions, not vistrails Modules
*** Why is there so much patching?
** Re-implemented Alternate PortSpec for InputPortSpec
*** It will now inherit specs from parent (No need to reimplement)
** Module upgrades?

'''Items to Discuss'''

=== September 16, 2015 ===
'''Updates'''
* [TE] Job Monitor tests and documentation done
** OK to leave document package in packages directory?

'''Items to Discuss'''
* [TE] Library wrapping: How to do code patching? [https://docs.google.com/drawings/d/1Sh3eOXot6v2y880jHKQrqXqAwr-0aoqYligg3z8G8MY/edit?usp=sharing Wrapping diagram]
** Insert code into module template (Old VTK code)
** Patch the library that is called (New VTK code)
** Somehow store code in spec and apply when executed?
*** Executed code needs at a minimum access to inputs, outputs, current class
*** Use standard input/output dict and obj reference that the code operates on?
*** Can this be done while keeping the execution abstract?

* Do new release now?

=== September 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* New release?
** [RR] wants reprounzip
** tej changes & doc
** job monitor & jobmixin fixes
** mongodb
** reprounzip
** warning: MplFigure type is int
** tabledata: add Reshape, DictoToTable & ListToTable, fix ListToTable with numpy arrays
** PythonSource can have same name for an input & output
** don't show spreadsheet at exit

=== September 2, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Limit autosaves? [https://github.com/VisTrails/VisTrails/pull/1126 #1126]

=== August 26, 2015 ===
'''Updates'''
* [TE] Added Job support to Parameter Explorations (Requested by Colin), and Mashups
** specify job ids, need to specify different ids for parameter explorations since they have the same version id
** how to deal with parameters passed in on command line
* [General] provenance: should be creating a new version when we execute workflow with changed parameters?
** currently, custom_params annotation stores this in provenance currently
** [RR] API doesn't record provenance if passing in parameters: http://git.io/vsAA5
'''Items to Discuss'''

=== August 19, 2015 ===
'''Updates'''
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [TE] Working on Job Monitor documentation

'''Items to Discuss'''
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [TE] Stop testing VisTrails 2.0?

=== August 12, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Build broken on Travis; because of IPython 4 released today? ([https://travis-ci.org/VisTrails/VisTrails/builds/75279795 build 992]; [https://github.com/VisTrails/VisTrails/issues/1123 #1123])

=== August 5, 2015 ===
'''Updates'''
* [TE] Fixes to Jobs
** Could not delete jobs
** Could not run job in group
** Job not reset when calling ModuleSuspended
** Added deleting job from context menu
* [RR] Writing documentation for everything [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

'''Items to Discuss'''

=== July 29, 2015 ===
'''Updates'''
* RR still looking into new interpreter thing
** Goal is to take out scheduling logic from Module so it can be split in multiple processes, and so that smarter strategies can be added in time
** This means some work on packages
** Spreadsheet can live in kernel process? Still some UI stuff that will take work (changing configuration, persistent archive's viewer, ...)
* [TE] Problems running examples [https://github.com/VisTrails/VisTrails/pull/1111 #1111]
** Testing of more examples requires additional packages on the test machines.
** Fixed faulty line-ending in PythonSource:s failing on Python 2.6.
** Test suite now testing SUDSWebServices (If web service is down, test suite will fail)
** preferences.py test failed reloading 'dialogs' package, switched to using 'URL'.

'''Items to Discuss'''

=== July 22, 2015 ===
'''Updates'''
* [TE] mailing lists back online
* [TE] Working on [https://github.com/VisTrails/VisTrails/issues/1107 #1107]
* [RR] Working on ReproZip package

'''Items to Discuss'''
* [RR] MongoDB package [https://github.com/VisTrails/VisTrails/pull/1106 #1106]
* [RR] Example for tej docs? [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

=== July 15, 2015 ===
'''Updates'''
* 2.2.2 released

'''Items to Discuss'''
* RR is considering executing everything in an IPython kernel (i.e. separate Python interpreter, like the one spawned for a notebook)
** It's a separate process that we can restart without restarting the app/gui
** We can isolate the execution environment (e.g. for the server)
** We can run the whole thing remotely (if your data is elsewhere, just run VisTrails locally and the pipeline elsewhere)
** Pipeline execution no longer makes the interface hang, it just makes the kernel hang (but that's fine)
** We can use notebooks as modules (probably way nicer than the PythonSource module)
** We can run multiple kernels so long as the ports carry things that are serializable
*** meaning we can put the multithreaded-interpreter without all the hacky parts it has now
*** we can run IPython kernels in all the languages IPython supports, [https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages currently 46]

=== July 8, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Buildbot github hook not working after IP address change
* [TE] No reference to VistrailsApplication ([https://github.com/VisTrails/VisTrails/issues/1103 #1103])
** [RR] Added PR [https://github.com/VisTrails/VisTrails/pull/1104 #1104]
* [TE] Reopening VT file after saving with bundled subworkflow won't offer subworkflow upgrade ([https://github.com/VisTrails/VisTrails/issues/1102 #1102])
** allow manual delete to fix right now
** fix this on top of the use-uuid branch
* [TE] Release VisTrails 2.2.1? ([https://github.com/VisTrails/VisTrails/blob/v2.2/CHANGELOG CHANGELOG])
** [https://github.com/VisTrails/VisTrails/pull/1093 output-modules-use-global-dir]
** [https://github.com/VisTrails/VisTrails/milestones/version%202.2 Current issues for 2.2]

=== July 1, 2015 ===
'''Updates'''
* [TE] PROV fixed
* [TE] Working on subworkflow issues
* [RR] Considering reworking the controller (log vs exception problem, retained upgrades causing interferences) and also the interpreter (IPython?)

'''Items to Discuss'''

=== June 24, 2015 ===
'''Updates'''

'''Items to Discuss'''
* UV-CDAT
* [TE] Can a cyclic workflow be valid? ([https://github.com/VisTrails/VisTrails/issues/1097 #1097])
** focus on disabling the ability to create cyclic pipelines because more things break than just this with a cyclic pipeline
* [RR] Relative paths ([https://github.com/VisTrails/VisTrails/pull/1057 #1057])
** This interacts with the new bundle; how do handle packing files inside the VT bundle?

=== June 17, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] current_version and reusing existing upgrades are broken ([https://github.com/VisTrails/VisTrails/issues/1095 ticket #1095])
** Could be that export to PROV is using an unflushed upgrade pipeline?
** current_version would then be correct.
** It may work to flush the actions before exporting?

=== June 10, 2015 ===
'''Updates'''
* DAT: fixed VTK issue on Linux and Mac
* Still crashes on Windows. Need help! Reminder: this works in the VisTrails spreadsheet (QCellPresenter), although no widget get changed there during a drag
** Is it a VTK bug?
** Is it simply impossible to change widgets during the drag, should we do it a different way?
** Did I miss something that is done in VisTrails but somehow not in DAT?
** Low prio, UV-CDAT doesn't run on Windows anyway

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 Updated pull request])
* Single instance code and batch mode

=== June 3, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 pr])
** Requires fixes to command line parameters, Output modules, and batch mode
** How to test this
** Updated missing/outdated flags
** Fixed view issues when generating graphs
* [TE] batch mode
** SpreadsheetOutput not enabled in batch mode. Should we check is_running_gui instead?
** Other instance setting flags from caller
** Is graphsAsPdf replacing spreadsheetDumpPdf?
** graphsAsPdf true by Default?
** Batch mode executing by default (Not needed when generating graphs)
** Re-added workflowInfo as withWorkflowInfo for writing graph and xml workflow
** [DK] batch mode should be outputting to files or stdout, shouldn't always trigger SpreadsheetMode
** execute flag, maybe make execution the default and allow a "--no-execute" if you only want to capture graphs, for example

=== May 27, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] API question
** http://lists.vistrails.org/pipermail/vistrails-users/2015-May/000357.html
* Status of DAT
** Can add VCS plot to DAT but need to work on configuration windows
** Documentation for graphics templates for UV-CDAT/vcs?
* Qt support?

=== May 20, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Reviving the DAT, integrating scripting & porting UV-CDAT!
** On [https://github.com/VisTrails/DAT GitHub] ([https://github.com/VisTrails/DAT/issues issues])
** Merging 2 years of development taking longer than expected, but getting there. The plan is to get the patches in VisTrails and never fork again, we never want to get in UV-CDAT's situation (and don't need to).
** VTK cell works fine on Linux but there was flickering on Mac & Windows before; still issues on Mac (Windows status unknown)
** Can get a VCS plot soon (but will need VTK cell fix)
** Integrate in UV-CDAT's build system (so we have cdms, VCS, ...) -> RR can do this, low priority
** How do we integrate scripting?
*** We want to be able to seamlessly make changes to a plot by changing Python code
*** Define new plots by entering Python code without writing modules/packages?
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 13, 2015 ===
'''Updates'''
* [RR] Test skipping whitelist ([https://github.com/VisTrails/VisTrails/pull/1069 #1069]) -- low priority
* [RR] Custom matplotlib modules can't be compatible with both 2.1 and 2.2 ([https://github.com/VisTrails/VisTrails/issues/1067 #1067]); should be fixed for ALPS ([https://github.com/VisTrails/VisTrails/issues/1070 #1070])

'''Items to Discuss'''
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 7, 2015 ===
'''Updates'''
* [RR] Export/import workflow to Python working!

'''Items to Discuss'''
* [Claudio] UV-CDAT
** The UV-CDAT project is the biggest user base of VisTrails
** VisTrails package management provides a lot of friction towards people plugging in their code
** Need to make it easy to integrate your random Python scripts in the system without having to deal with all the boilerplate, at least in the first step
** [RR] argues that modules are still good; UV-CDAT shouldn't move towards a purely script-based backend
** [RR] export/import with Python could reduce a lot of that friction by allowing 1) to edit workflow as Python 2) to open up boxes automatically if needed code doesn't match actual modules
** ...

=== April 29, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] <strike>Abstractions</strike> subworkflows status ([https://github.com/VisTrails/VisTrails/labels/subworkflows tickets])
* [RR] matplotlib compatibility (2.1 & 2.2), [https://github.com/VisTrails/VisTrails/issues/1067 #1067]
** RR to try and fix ALPS matplotlib modules

=== April 22, 2015 ===
'''Updates'''
* 2.2.0 has been released!
* Windows issue (via email from Ryan)
** issue with manifest file (may be a new file in VTK6?)
** Tommy has regenerated new Windows builds
* Binaries, pypi, and conda released
* [RR] Export as script
* Python sources using VTK need to switch to SetInputData (users should be aware of this)

=== April 15, 2015 ===
'''Updates'''
* Ready for 2.2.0 (apart from binary/deps issues)
** Missing some libs (scikit-learn, tej, tdparser, SQLAlchemy+connectors
** Windows: runvistrails.py is no longer used, so the PATH is wrong
** Windows: pip is broken, but it probably wouldn't work anyway because of permission issues (disable this?)
* Queries, upgrades and getPipeline() usage ([https://github.com/VisTrails/VisTrails/issues/1054 #1054])
** Getting a pipeline with getPipeline() is not safe: it might return an invalid pipeline
** This is used in many places throughout the code, like queries
** Upgrading would require going through the controller, but that creates new actions
* [TC] Avoid copying a module's output if it's used as input by exactly one downstream module ([https://github.com/VisTrails/VisTrails/issues/1060 #1060]) (useful for big numpy arrays you can update in-place)

=== April 8, 2015 ===
'''Updates'''
* [DK] Merged RR's changes for output modules (1012 and 1013)
** RR will merge remaining changes, then create v2.2 branch!

'''Items to Discuss'''
* BNL need numpy array to VTK image
** Looks like VTK has some helpers for this
** We will help if issues arise
** Will contribute back to VisTrails package
* Upgrade issue: [https://github.com/VisTrails/VisTrails/issues/1017 #1017]
** Automatic upgrades should happen between versions of provided upgrades
** Our existing upgrades work around this so it doesn't need to be 2.2.0
* Corner-case VTK modules
** No longer need VTKCell input port, so don't interfere with registry and API anymore
** Still work weirdly, people probably shouldn't use them
** But we have lots of clunky modules since we wrap the whole of VTK; some people might rely on this and know how to use them, let's keep them anyway
** Ready for 2.2.0

=== April 1, 2015 ===
'''Updates'''
* [RR] UV-CDAT: bugfixing for 2.2, long-term plans: implement scripting import/export in VisTrails, port to UV-CDAT
* Possibly, try to move to regular VisTrails to use new features

'''Items to Discuss'''
* 2.2 release: nothing much is pending anymore, release next week?
** [TE] vtkExporter classes [https://github.com/VisTrails/VisTrails/issues/1032 #1032]
** [RR] Hiding upgrades in version tree might make it (or might be 2.2.1 so we can test it out) [https://github.com/VisTrails/VisTrails/issues/949 #949]
** Output modules changes to go in
* add note to documentation about order of parameters in VTK
* add issue about exporter upgrades if not already there

=== March 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* 2.2 release
** Checklist on Github: https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist
** Review output modules
** RR has a couple more issues to fix
** Ready to go -- sign app package for OSX? [https://github.com/VisTrails/VisTrails/issues/984 #984] We need access to the Apple Membership team

=== March 18, 2015 ===
'''Updates'''
* [TE] VTK6 works

'''Items to Discuss'''
* [RR] Release v2.1.5 with backported tabledata?
** MTA example needs updated tabledata (for JoinTables)
** Google Maps package still not available
* [RR] Work torward v2.2.0?
** changes:
*** new persistence
*** API changes
*** output module changes (upgrades?), maintain cells but try to upgrade
*** not wrapping stuff
*** VTK6? yes
*** JobSubmission stuff?
*** relabeling for upgrades [https://github.com/VisTrails/VisTrails/issues/949 #949]
** makes sense, needs the tree view code to be updated, check selection
** See [https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist 2.2 checklist]
* Discussion of [https://github.com/VisTrails/VisTrails/issues/1016 #1016]
** plumbing between outputs and output modes, how to define a mode that works for many outputs without writing for each output?

=== March 11, 2015 ===
'''Updates'''
* [RR] persistent_archive done; merge? ([https://github.com/VisTrails/VisTrails/pull/755 #755])
** note about the focus events for widgets
** TE be aware of file_archive for future binaries that include persistent_archive
* [TE] [https://github.com/VisTrails/VisTrails/pull/998 New VTK package] finished

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails? (see last week; decision needed)
** RR email to JF about this
** yes; email sent to Github
* [RR] Switching order of output ports ([https://github.com/VisTrails/VisTrails/pull/1006 #1006])
** added port specs are sorted at a separate spot (Module.*_port_specs properties) than those in the registry (which are sorted in the registry), but those two lists are just combined without respect to sort keys
** need to determine whether the two lists should be merged or remain distinct
** should make sure that order of input ports and output ports makes parallel connections for things with same order
** DK suggests breaking backward compatibility here: workflows still run, can fix easily if a problem in an existing package.
* [RR] Question about output modes ([https://github.com/VisTrails/VisTrails/pull/1007 #1007]), how to integrate in API ([https://github.com/VisTrails/VisTrails/pull/24 #24])
** Should ImageFileMode be removed? ("image" is not a mode, "file" is)
** ImageOutput missing?
** Feel free to change how formats works
* [TE] Test suite segfaults on Fedora 17 virtualbox. Install newer version? (Support ended in 2013)

=== March 4, 2015 ===
'''Updates'''
* [TE] VTK wrapper
** Works on VTK 5.10
** Still need to test VTK 6
** New general wrappers for python functions and classes

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails?
** When [http://i.imgur.com/UTY2qfg.png filing a pull request] from UV-CDAT/VisTrails, VisTrails/VisTrails is selected by default
** People keep forgetting to change the default ([https://github.com/VisTrails/VisTrails/pull/956 #956] [https://github.com/VisTrails/VisTrails/pull/968 #968] [https://github.com/VisTrails/VisTrails/pull/999 #999] [https://github.com/VisTrails/VisTrails/pull/1000 #1000] [https://github.com/VisTrails/VisTrails/pull/1003 #1003] [https://github.com/VisTrails/VisTrails/pull/1004 #1004] [https://github.com/VisTrails/VisTrails/pull/1005 #1005])
** Only way to change that is to not have it marked as a fork of VisTrails/VisTrails
** Github staff [https://gist.github.com/remram44/b364c24ef1e462ce6e2f can make that change for us]; should we do it?
** Juliana: comments on this? visibility vs. convenience/annoyance for developers
* [RR] What about [https://github.com/VisTrails/VisTrails/issues/991 #991]?

=== February 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] vtkviewcell for infovis support, can we unify with VTKCell?
** need to test this
* [TE] vtk wrapping
** Mostly finished
** VTK 5.10 produce incorrect results with old wrapping
*** Old wrapper is based mostly on VTK 4
*** Most vtk_examples affected
*** [http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Replacement_of_SetInput]
*** should be able to upgrade from SetInput to SetInputData (need to drop GetOutput and replace with self ports)
*** can we change vtkInstance to just return self and not wrap things
** terminator example not working under 5.8?
* How does VTK wrapping fit into general wrapping framework?
* [RR] new persistence package

=== February 18, 2015 ===
'''Updates'''
* [RR] New VisTrails API and IPython integration ([https://github.com/VisTrails/VisTrails/pull/24 #24])

'''Items to Discuss'''
* [TE] VTK wrapping
** [https://gist.github.com/rexissimus/16b74693545b5e7c1035 Benchmarking vtk package]
*** Old: 24.7 seconds
*** New: 10.5 seconds (Except first time that adds 8 sec)
**** The parsing that calls is_abstract (that tries to instanciate all vtk classes) is now only run the first time.
**** get_items_from_sigstring takes 2 seconds, maybe we can use a lookup dict for already computed sigstrings?
** Now using a general python function wrapper
*** VTK classes are wrapped into python function that does not depend on vistrails
*** VTK functions can be executed without vistrails
*** The spec maps functions into vistrails modules, but can also describe wrapping
*** A general python function wrapper that supports
**** kwarg inputs
**** single, list, dict outputs
**** callback for progress reporting
**** temporary file generator for using FilePool
**** optional output generation
*** Creating specs:
***** Create spec by hand
***** Auto-create spec outline (TODO) and manually finish it
***** Dynamically create spec (VTK)
***** Implement documentation wrappers (Can use scikitlearn wrapper to wrap numpydoc) (TODO)
***** Classes as bad functions needs to be wrapped in new functions before they are wrapped. This is different for each package.
****** Classes is hard: Like VTK, and matplotlib. Scikit-learn does still not wrap classes
***** Spec diffing and patching could be done using code from matplotlib.
** Still needs upgrades from old VTK package
*** Is it possible to dynamically wrap functions, e.g, you see a SetFunc and just remove the 'Set' prefix. Or do you need to create a complete mapping?

=== February 11, 2015 ===
'''Updates'''
* Update from Friday's meeting
** discussed VisTrails internals
** discussed wrapping
*** xml discussion, hard to modify because tied to db code
*** TE has made it possible to add the schema-defined attributes to the intermediate representation
*** higher-level operations on the port specs
** make sure the simple case works
*** [JF] take a simple package with documentation and figure out what the base case for wrapping is

'''Items to Discuss'''
* [TE] VTK wrapping
** Dynamic loading works
** Reading XML is fast enough, but [https://gist.github.com/rexissimus/8272d3c776ccfa115d82 unserializing data is slow]
** Working on patterns for patching
** Matplotlib has many advanced patterns like argument ordering, nested arguments, alternateSpecs, output types.
*** Having all this in a general wrapper might confuse users?
** [RR] Delay module (except for identifiers) until you need it---e.g. don't deal with port specs, etc. until necessary
* Scripting Support [https://github.com/VisTrails/VisTrails/pull/950 #950]
** [RR] Issue with getting code from modules
** Design a simple solution
** [JF] Couldn't you use modules as black boxes without conversion, just to call into modules/subworkflows easily from e.g. IPython?
*** [RR] This is a job for the API, and a very separate use case. See [https://github.com/VisTrails/VisTrails/pull/24 #24]

=== February 4, 2015 ===
'''Updates'''

'''Items to Discuss'''
* Wrapping
** Format to use? Currently XML (like current matplotlib)
*** JSON and YAML have simple "to python dictionary" methods
*** But don't stream
*** YAML a lot easier for humans
** [DK] vtk-new-package also changes parameter names, creates enumerations
*** intermediate schema needs to be extensible
*** packages will want to store there specific infos for compute() method generation
*** also might have specs-altering info, like matplotlib's alternateSpec
** representation to code , registry already has schema for some aspects
** [RR] We might want to see if Module subclasses can be created lazily
*** no need to create all the classes just to register them in the registry and never actually use most of them
*** future effort
* [RR] Where should VisTrails packages live?
** tej installs as 'vistrailspkg.tej', TE installed it as 'userpackages.tej'
** Currently, standard packages are 'vistrails.packages.', user packages are 'userpackages.' and packages loaded through pkg_resources might be anything
** [RR] Use 'vistrailspkg.' everywhere?
** Long-term effort to simplify package distribution/installation (and have VisTrails get them automatically?)

=== January 28, 2015 ===
'''Updates'''
* T. Caswell to come visit on Fri 6 to discuss wrapping work

'''Items to Discuss'''
* [TE] New VTK wrapping
** Current code by DK seems a good deal faster
** Generates XML that can be patched/tweaked, generates Python code from it, VisTrails only loads generated Python code
** RR would rather have VisTrails load intermediate representation (= XML) directly, wants to make sure this is not slower
** The goal is to turn the intermediate step into something generic that would be used for every wrapped package (vtk, numpy, matplotlib, sklearn, java) instead of each having its own
** TC has its own code at [https://github.com/Nikea/VTTools/blob/master/vttools/wrap_lib.py github:VTTools] which parses numpy docstrings and generates modules, doesn't yet handle classes or persist anything
* Web crawler
** Right now, TE starts jobs for "start crawler", "stop crawler", "install classifier"
** RR would rather have the crawling be a job as far as VisTrails and tej are concerned
** The whole thing would be one pipeline: load examples, train classifier, start crawler [check for job, kill previous one, upload model, start processes], get snapshot, visualize
*** Need some support in tej and job submission system: long-running jobs, stop a job (wait for it to finish?), restart a job even though results are cached

=== January 21, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Unified wrapping method discussion [https://github.com/VisTrails/VisTrails/issues/991 #991]
** TE to work on reusable method with intermediate representation, starting with VTK
* [RR] Examples for scikit-learn: JF has an old example using Weka with parameter exploration (not currently in source tree)
** AM's examples are enough
* [AM] scikit-learn package is done, merge it in? [https://github.com/VisTrails/VisTrails/pull/955#issuecomment-70286788 #955]
** RR will merge
* [RR] What should copyright headers say? [https://github.com/VisTrails/VisTrails/pull/994#issuecomment-70173935 #994]
** Let's keep everything in there: Utah/Poly/NYU

=== January 14, 2015 ===
'''Updates'''
* [TE] Working on classifier
* [RR] Scripting integration, work in progress

'''Items to Discuss'''
* [RR] Unified wrapping method discussion ([https://github.com/VisTrails/VisTrails/issues/991 #991])
** Let's talk next week, [AM] and [DK] are not here

=== January 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* make sure that we address critical issues, questions, and pending review branches in a timely manner
* scripting support
** [RR] no issues if we want to just keep annotations in the generated code to allow the link back to a workflow
** [RR] can translate from workflow to script, working on script to workflow
** will work for parameter value changes, structural changes require changes to the annotations
** need to publish best practices here
** would be cool to do looping in scripts (easier interface than with workflows)
* notebook support (convert form notebook to workflow)
** RR will sync with FC on this
* Issue with console in built-from-scratch
** [TC] iPython rearranged some of the completion stuff in 2.2 and 2.3
** binary has old version of iPython -> 1.0.0, should we update?
* [TC] automated wrapping of numpy and scipy
** discovered a bunch of malformed documentation in numpy and scipy
** has github repo for vistrails tools
** example modules wrap a bunch of R stuff (not baked in, just how things are)
** will be pushing wrapping logic up
** port names forbidden (window and domain)
** have an import hook to get from yaml directly to VisTrails Modules
** should work for any python modules with well-formed numpy docstrings.
* [Action] should make it clear in documentation that Constant now means serializable not that the value doesn't change (e.g. List)
* [TC] might be interesting to try to build components of matplotlib and accumulate in figure (long-term project, but thinking about how this might work)
* [TE] build and build scripts
** completely automatic, buildbot
** need to set the build machines for the environment we want for the binary
** would virtualenv work here?
** [TC] anaconda can pin versions, potential path to test different configurations
** Q: upload nightly binary builds? A: makes sense, make sure they are well-labeled
* sourceforge stats: e.g. http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07
* package issues (see Remi's message)
* [TE] Scope of tej
** Support single ssh commands?
** Queue can be used as a remote machine (crawler is using queue.call*)
* SourceForge stats: http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07

== Older meetings ==
* [[Development/2014]]
* [[Development/2013]]
* [[Development/2012]]
* [[Development/2011]]
* [[Development/2010]]

Development

2016-07-13T14:56:43Z

Tommy: /* 2016 */

<div class="nonumtoc toclimit-1">
__TOC__
</div>

See also the [https://github.com/VisTrails/VisTrails/wiki/Development Github wiki]

== 2016 ==

=== July 13, 2016 ===

'''Updates'''

'''Items to Discuss'''
*[TE] Simplified running module using API for scripting [https://gist.github.com/rexissimus/b28d83ae516a519167f5751bb8ab3739 example]

=== July 6, 2016 ===

'''Updates'''

* [DK] Working on bundles

'''Items to Discuss'''
* [TE] Using vistrails API in scripting [https://gist.github.com/rexissimus/034d9c4dedc3299a079e84981dedd8c7 example 1 (API with VTK)] [https://gist.github.com/rexissimus/a4a9ca6c08d4058c64967d2b35415fd5 example 2 (DownloadFile only)]
** Call module in script using vistrails API
** Can be used when no export method is defined.
* [TE] [https://github.com/VisTrails/VisTrails/commit/c76c109349769fee1280f85c22678380a2f9cd39 Server news bug] Critical?
**[RR] No, unreleased
* [DK] New bundle organization
** BundleMapping contains individual mappings from raw objects to BundleObj
** Must be separate in order to have in-memory, separate from serializer settings

=== June 29, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Export VTK as python script
** Works on Terminator (Isosurface, Volume Rendering, clipping plane, combined rendering) [https://gist.github.com/rexissimus/16caf5200802e150296f62a0c7844c5a example]
** Preludes (imports) still need improvements
** Works with vtkInteractionHandler (clipping plane)
** Resulting clipping plane is incorrect? (supposed to hide one side of the plane)
** vtkRendererOutput Uses VTKRenderWindow as output
*** Should support different output modes?
*** Does not work with multiple outputs (Next cell is displayed when current is closed)
*** Uses wrapped vtkInstance (as vvtk)
**** Create new patch system with code that can be used both in vistrails and in a python script?

=== June 22, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Fix for upgraded analogies (PR [https://github.com/VisTrails/VisTrails/pull/1177 #1177])
** Uses module location to find module remap (The best we can do right now?)
** Also fixes remapped port names for connections to existing modules
** May still fail on complex upgrades like adding a function on an upgraded module that has a different port name

* [TE] Working on exporting wrapped libraries (VTK)

=== June 15, 2016 ===

'''Updates'''
* [TE] Added depth logic to python script exporter ([https://github.com/VisTrails/VisTrails/commit/50f220e4f6abe5a7bb8689f73f456f43df2dbc12 full commit])
** Fully implements connection merging and list looping

'''Items to Discuss'''

* [TE] Making analogy work on upgraded workflows ([https://github.com/VisTrails/VisTrails/issues/1175 #1175])
** Analogy only works We need to use the non-upgraded action chain
** But pipelines need to be valid (matcher uses module portspecs)
** Tried to get upgrade remap from upgrade action, but this seems impossible
** Use module location instead?
*** Location should be identical for one-to-one module upgrades

=== June 1, 2016 ===

'''Updates'''
* VisTrails 2.2.4 announced (finally)
** 5 survey replies
** 47 downloads last week

'''Items to Discuss'''
* [TE] Export VTK as script (python-wrapper)
** to_python_script
*** needs the pipeline (or at least the connections)
**** Should not generate code for any possible VTK method (exporter detects which ports is used in the source)
**** VTK needs to know connection order
**** Adding functions directly to the script results in nicer code
** Add support for multiple input connections
** Add support for list looping

=== May 25, 2016 ===

'''Updates'''
* Mailing-list fixed
* Getting stats from the "server news" mechanism (via [https://github.com/remram44/apache-log-info parser])

'''Items to Discuss'''
* [RR] Alexis doing writeup on VisTrails, curious about interesting streaming use-cases (and potential future users)
* [TE] Union ports
** Show union ports in pipeline (DEMO)

=== May 18, 2016 ===

'''Items to Discuss'''
* [TE] mailing list still down - Julio working on it
* [TE] Improved union port
** New schema 1.0.5 adds portitem.union string attribute
** Works with pipeline view, parameter exploration view, and mashup view
** Should work well for matplotlib
** Use with VTK ports?
*** It uses [item_1,item_2] style ports usually with different tuple length.
* [TE] Remove emacs dependency from db generate [https://github.com/VisTrails/VisTrails/issues/1173 #1173]

=== May 11, 2016 ===

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]
** GUI-based solution [https://github.com/VisTrails/VisTrails/tree/union-port Branch union-port] Demo?
*** Shows single port for all ports with same sort_key
*** Select specific type when adding/showing
*** Only one type should be visible on the module at any time
*** Making tuple parameters union types is probably too complicated
*** Should work with alternate specs like matplotlib (if sort_key is defined correctly)

* [TE] Feature suggestion: Let connections connect to functions/parameters
** Show functions and parameters as ports and toggle port visibility directly for functions and parameters
** Use separate views for ports and functions (like before)
*** Allow rearranging of functions
** Pros:
*** Supports ordered connections. Create 2 functions, make them visible as ports, make connections to them.
**** We can also have, e.g., a line joining the ports on the module to indicate they are part of a list.
**** Makes List module simpler
*** Connect to parameter in tuple
*** Functions that are visible on the module can connect to an actual function, and not just to the first one it finds.
*** Can replace operation modules (in python-wrapper) in some cases for, e.g., numpy.
** Cons:
*** Interface more complicated and crowded
*** More difficult for users to grasp?
*** No immediate use case
*** Makes no union type for tuple parameters a bigger problem.

* [TE] Publish user survey?
** No response from vistrails release yet
** Not announced on vistrails-users yet.

=== May 4, 2016 ===
'''Updates'''
* VisTrails 2.2.4 released

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]

=== April 27, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Wrapping Bokeh
** New method type "operation"
*** Transforms Figure->Glyph->Output into Glyph->Figure->Output
**** Glyph sets function name and arguments as output
***** Not serializable, but should always be computed together with the subject of the operation.
**** Figure applies Glyph operation on itself
*** Useful for matplotlib?
**** matplotlib currently find actors by searching upstream?
**** But this is more difficult since matplotlib is not function-based.
** New "union" port type
*** Turns "x(float), x(list)" into "x (float, list)" and uses first set value
**** Uses only first value in tuple
**** Bokeh have many properties that support (list, string, Float)
*** Does not work with depth=1 types (e.g. Float of depth 1)
**** Turn Depth 1 types with known type into lists?

* [TE] New bugfix release
** Finalize survey

=== April 20, 2016 ===
'''Updates'''
* Merged upgrade fixes
** Now has infinite loop test
** loop test now correctly loops 5 times
*** remap_module used wrong (current) package version when creating ModuleDescriptor
* Fixed multi-step group upgrades (PR: [https://github.com/VisTrails/VisTrails/issues/1168 #1168])

'''Items to Discuss'''
* New bugfix release
** Merge usagestats
** Need to finalize survey

=== April 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Chaining upgrades done ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Replace "Upgrade" description annotation with "upgraded_from" annotation to identify which tags to hide?

* [TE] Iterating handle_invalid_pipeline ([https://github.com/VisTrails/VisTrails/pull/1165 #1165])
** Not based on [https://github.com/VisTrails/VisTrails/tree/chain-upgrades-loop chain-upgrades-loop]
** Cherry-pick test to preserve source?
** Need maxPipelineFixAttempts option?
*** The code is now smarter about recursion, so max attempts will "probably" never be reached.
** Need [https://github.com/VisTrails/VisTrails/commit/0ef0667426937eddb1d1c1e397f0657ffec039a9 debug messages]?
*** Would need to be moved into handle_invalid_pipeline

=== April 6, 2016 ===
'''Updates'''
* [TE] Query View improvements
** Done except for displaying "Version Info" and #1164
* [RR] Working on finishing new interpreter (finally!)

'''Items to Discuss'''
* [TE] Chaining upgrades ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Try latest upgrade first, then previous.
** If all fail, select latest upgrade?

=== March 30, 2016 ===
'''Updates'''

'''Items to Discuss'''

* [TE] Query View improvements
** Unified do_version_switch and get_upgrades as validate_version()
** Problems with query view using its own controller
*** Fixed module info not being displayed for query results
*** Still no version info for query results
*** Still an issue with version query view not being updated

=== March 23, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Usage reporting almost ready to go
** Need to record whether specific features are used: paramexpore, mashup, query
*** [DK] Record if LaTeX extension is used? But hard to distinguish from direct batch invocation
** How to record size of vistrail?
*** [DK] IdScope already walks over vistrail, use that
*** but total number of modules and versions doesn't give an idea of average size of individual pipelines

=== March 16, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Upgrades in Query Mode
** Now using code similar to do_version_switch
*** Uses handle_invalid_pipeline
*** Differences: Not using current_pipeline, flushes changes
*** New controller method get_pipeline optimized using cached pipelines (but not current_pipeline)
*** Integrate to avoid repeated code?
*** Use this for query mode?
* [TE] VisTrails 2.2.4 ready for release?
** tej package updated. Others?
* [JF] upgrades and the version tree
* [JF] provenance in Jupyter
* [DK] bundles: [https://github.com/VisTrails/VisTrails/pull/1092 #1092]

=== March 9, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixing search mode
** String query now matches all by default
*** This caused pipeline queries to never match
** String query can search: User/Notes/Tagname/Time/Module name
*** Should we search module names by default? (Disabled by default because it is expensive)
*** Fixed notes search
** '>' parameter queries in documentation but has been removed
** Fixed module matches for upgraded pipelines (By not upgrading pipeline)
*** Upgrades still a problem
*** Add "Upgrade all menu option?" (Or upgrade all on open when `hideUpgrades`)
*** [JF] Allow search on past tags

* [TE] Create new bugfix release
** Finish querying
** Path issue on windows

* [DK] Look into sqlalchemy and new bundle branches

=== March 2, 2016 ===
'''Updates'''
* [TE] Fixed cache bug with port specs
* [TE] VisTrails Next
** Most packages now work
** No qgis for Python 3

'''Items to Discuss'''
** Always dereference symlinks? [https://github.com/VisTrails/VisTrails/issues/1146 #1146]

=== February 23, 2016 ===
'''Updates'''
* [TE] Fixed PythonSource 100% CPU bug
* [TE] VisTrails Next
** Updated [http://opendap.co-ops.nos.noaa.gov/axis/webservices/wind/ NOAA Web Service] examples
*** Now uses REST service, tabledata, and Google Maps
*** Web Service replaced with DownloadFile

'''Items to Discuss'''
* [RR] Couple of fixes are in for API, and tej&reprounzip on the Mac binary. Also new release of tej, and working on anonymous usage reports.
** New 2.2 release soon?
* [RR] Anonymous usage reports
** Sends out info like number of modules & versions, packages used, Python & libs versions, execution time, specific features [https://github.com/VisTrails/VisTrails/pull/1154 #1154]
* [JF] Bring in noWorkflow to track variable dependencies, for the considered Jupyter integration?
* noWorkflow - provenance for python scripts
** Recent work on tracking dependencies
* Also integrates ReproZip with Jupyter
** [http://mybinder.org mybinder]
*** Use with ReproZip to automatically build Jupyter notebook interfaces
* Daves comments on Jupyter integration
** It is possible to identify cell order on the server side
** Not trivial to track order of cells on client side
* How does Galaxy workflows relate to VisTrails?
** Packaging in Galaxy is hard
** Galaxy for biomedical workflows, difficulty making it general
* Action items
** How difficult to track cell dependencies in Jupyter notebooks?
** Use noWorkflow to track cell dependencies?
** How difficult to modify mybinder to use ReproZip packages?

=== February 17, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixed Group memory usage
** Modules in groups are supposed to be freed when done executing
*** Prevented by logger that stored references to the modules (fixed, now using id(module))
*** Prevented by list iterator bug that stored list of modules on the 'self' port bug (fixed)
* [TE] VisTrails Next
** Removed deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** PythonSources will be upgraded
*** Fixes for Python < 3
*** fixes for VTK < 6
** TODOs
*** Remove RemoteQ
**** Port Hadoop to tej (Already have pbs)
*** Merge package wrapper
*** Finish SQLAlchemy branch
*** Finish new bundle branch
** [JF] Will contact Jeff and Matthias about moving to Python 3
* [JF] Query by Example is broken
* [JF] VisTrails Data Cleaning Project
** Use VisTrails to process and explore task-specific data while keeping provenance.
** Remi's Idea
*** Use VisTrails as the backend in a Jupyter notebook
*** Overcome problems with executing cells in random order
**** Interesting research topic, but little interest has yet been noted
*** Interesting to study how such a notebook would be used (Is there notebook usage data available?)
*** Impose restrictions to notebook cell boundaries
*** It will only work for functional operations
*** Can we fix, or detect, non-functional (mutating) operations?
*** Analyse code and data flow and see if it mutates data in unexpected ways?
*** Mutable operations can be created in many ways in Python
* Next meeting Tuesday 11:30

=== February 10, 2016 ===
'''Updates'''

'''Items to Discuss'''
* VisTrails Next
** Test suite passes
*** Python 3 less deterministic, module upgrade order random.
** [RR] updating packages: Reprounzip (pushed), tej, persistent_archive, ...
** All of our packages should run fine :)
** VTK thumbnail comparison works
*** Rendering bug on some systems
**** QVTKCell now inherits QGLWidget
*** Old thumbnails had wrong height due to spreadsheetwindow being too small
**** Fixed by regenerating thumbnails
*** Silenced deprecation messages when generating modules
*** Many new classes in VTK 7
** Remove deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** Will break existing PythonSources
**** Try to upgrade?
*** Old-style packages
**** Or only allow a new style, like __init__.py renamed to info.py? (merge with identifiers.py?)
***** Read info.py without importing package?
*** Fixes for Python < 3
*** Fixes for Qt < 5
*** fixes for VTK < 7
*** Remove self port?

=== February 3, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] [http://lists.vistrails.org/pipermail/vistrails-users/2016-January/000402.html Rendering a .pvd (ParaView) file?]

* VisTrails Next
** All tests but thumbnail comparison passes
** Still issues with gui and more packages needs to be tested
** PythonSource and MplSource upgraded with lib2to3
** Keep contrib packages? Update?
** [https://blog.kitware.com/vtk-7-0-0/ VTK 7 is released]
*** Supports Python 3
*** Will hopefully get into conda and others soon
*** Deprecates a bunch of modules

* [https://travis-ci.org/VisTrails/VisTrails/builds/106743348 Travis builder] for VisTrails Next
** Runs!
** Uses conda
*** Many levels of requirements
**** apt packages
**** conda packages
**** python packages in requirements.txt
**** python packages in setup.py
*** Can probably drop conda. Default builder does not have Qt5, but beta builder do!
*** But useful if we want to use conda in our own build process.
** Lots of errors I do not get locally?

* [http://goo.gl/forms/Z4HBrwaBWL User Survey]
** Have you used any alternatives to vistrails?
*** Relevant? More options?
** How often do you use any of these particular features in VisTrails?
*** Add/Remove alternatives?
** How important would you rank the following potential improvements to VisTrails?
*** Add alternatives?

=== January 27, 2016 ===
'''Updates'''
* New interpreter
** Working prototype soon
** Looping not completely done (and port combination mode: pairwise/cartesian...)
** Need to integrate with VisTrails
*** Compatibility with existing modules
*** Use log controller
*** Want to cache at multiple levels (whole stream/single element of stream)
*** Non-runtime attributes of modules (cache check, automatic conversion check, constant from/to string)

'''Items to Discuss'''
* User Survey

* ZMQ failing on windows (vistrails-users)

* [TE] [https://github.com/VisTrails/VisTrails/pull/1143 Python 3 branch]
** Testsuite almost passes
*** Failing are unicode filenames, some users guide examples, and thumbnail comparisons.
** Fixed issues
*** Signatures are now bytes (convert to string to show in widget)
*** Cannot compare different types, e.g., (None < 1)
**** PortSpec.depth and min/maxConn could be None. (Backport!)
**** cell.row could be None
*** Lots of unicode/bytes fixes to serializations
**** We have encryption implementations in the code! (keychain)
*** Lots of small fixes to package method differences
** Current issues
*** logging widget empty?
*** version tree signals messed up
*** provenance view legend icons black
*** Text do not fit in some widgets
*** VTK thumbnail comparison fails
**** VTK Cells have some faces in wrong direction?
**** Because running in VM?
** Installing on Ubuntu LTS/Latest Mint
*** Install latest matplotlib from pip
*** Install VTK 7.0.0rc2 from source
*** No QtWebEngine binary (controversial) (Must install sip/PyQt5/Qt5 from source)

=== January 20, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Backporting features from Python 3 + PyQt5 + Qt5
** Merged unicode with master ([https://github.com/VisTrails/VisTrails/tree/unicode unicode])
*** One unicode test failing
*** Problem saving to xml
** Used [http://python-future.org/ python-future] to run futurize stage 1 to update legacy (pre 2.6) code ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized unicode-futurized])
*** Updates print to functions 'from __future__ import print_function'
*** Updates exception calls to use 'as'
*** removes most usages of 'long' (mostly used unnecessarily)
**** Only needed for 32-bit support
*** Fixes relative imports (from __future__ import absolute_import)
** Fixing code that is deprecated in Qt 4.8 and removed in Qt 5 ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized-qt5 unicode-futurized-qt5])
*** Updated all signals to new-style
* If we go 2 to 3, this could break packages
** means we should schedule any package format changes for the same time
** e.g., imports should be unrelated to code path (function to load module from package identifier?) (take them out of vistrails.* [https://github.com/VisTrails/VisTrails/pull/1002 #1002])
** any structural changes (e.g. the __init__ versus init thing) (RR thinks it makes sense, though having both named "init" is unfortunate)
** putting package identifier as xml?
*** Python not so bad, plus some stuff in there is Python code (checking dependencies)
** version the APIs?
*** RR planning on versioning vistrails_module.Module, no point versioning the whole package?
* file formats on 2 to 3:
** no real translation/upgrade, but non-ascii values that work on 3 won't load in 2

=== January 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://gist.github.com/rexissimus/dfd27e466427529c385c Porting to Python 3 / PyQt5]
** Basic GUI and execution works
** Minimal work to support 2to3
** Hard to support both PyQt4 and PyQt5

=== January 6, 2016 ===
'''Updates'''
'''Items to Discuss'''
* Updating VisTrails dependencies
** Successfully built [https://gist.github.com/rexissimus/f1a1aada7de1c00a57c7 Win7-64/Python3/PyQt5/Qt5/WebEngine/VTK7]
*** VTK 7 is the first supporting Python 3 but is only in release candidate phase.
**** Next version of VTK 6 is rumored to support Python 3
**** There is a development branch of VTK 6 supporting Python 3
*** Can travis build this?
**** We can skip tests for WebEngine and VTK if needed
** Python 3 [https://python3wos.appspot.com/ showstoppers]
*** No MySQL-python (sqlalchemy supports mysql through other drivers)
*** No suds (there are active forks but we could also drop support?)
* Options for python2/3 support:
** Interpreter could be python2/python3 based on packages
** six layer works but not the easiest to maintain (e.g. in reprozip)
* Drop support for win-64
* Update copyright headers to 2016

== 2015 ==

=== December 30, 2015 ===
'''Updates'''
* Bokeh package finished
** Can output to Browser/IPython/Spreadsheet (Limited functionality in spreadsheet)
'''Items to Discuss'''
* Updating VisTrails dependencies
** Bokeh needs QWebEngine (Chromium) in Qt5 which requires PyQt5
*** Many plotting libraries only work in browsers
*** But Chromium may be a big and controversial dependency
*** Or create a browser version of the spreadsheet?
** Some users have requested Python 3
** Not backwards compatible?
** Target for VisTrails 3.0 with new interpreter?

=== December 16, 2015 ===
'''Updates'''
'''Items to Discuss'''
* Users list question
* [TE] Wrapping Bokeh
** Added bokeh property parser
*** complements numpydoc parser
*** Not all attributes are available, partially because I am using a pre-release version.
** Wrapped modules
*** bokeh.plotting finished (Backwards like matplotlib: Create plot then draw on it)
*** bokeh.charts mostly done (Missing arguments)
** QWebView mostly works (but no zooming or buttons)
*** It would be better to use external browser or QWebEngineView
** Added improvements to wrapper
*** Generalized port translations (Color/Path to native types)
*** Can use multiple docstring/property parsers simultaneously

=== December 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Looking into wrapper
** Will port TensorFlow
** Doing a pass on the wrapper code & doc
*** UX improvements
** Factorize high-level docstring parsers into core.wrapper? (sphinx, numpy, google)
** Problem with name vs module_name (fails sklearn tests because class_by_name() is broken)
** Looking into compressing specs, lazy registration of modules

=== December 2, 2015 ===
'''Updates'''
* [TE] Package wrapping
** Wrapped most of numpy/scipy using __all__
** Added class attribute and method access for classes (Can add to class or to separate inspector module)
** TODO: Document wrapping procedure

'''Items to Discuss'''

=== November 25, 2015 ===
'''Updates'''
* [RR] New interpreter is coming along
** Everything is a stream
** Task system, eventually work-stealing parallelism
** Streams no longer advance in lock-step
*** Allows for constructions like filter, join, sorted-merge
** depth>1 still to be tested, no current plan to allow this through the module interface
*** Through looping though, can do streams of streams

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapped most numpy functions (no polynomials)
** and half of scipy classes and functions
** Added functions manually from documentation (no parseable lists?)
** Focusing on data flow constructs (no property/method access for classes)
*** Using spec diff (empty for now) and dynamic parser (stores spec in .vistrails/)
** Python class/function wrapper now stable
** Add google doc parser?
*** Is there a parser available?

=== November 18, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Numpy class wrapping works
*** Basic type is List, since most types are array_likes.
*** TODO: More classes and functions
*** Some operations are in-place and some aren't, and docstring not super clear
*** [RR] It seems only methods mutate, and most have a numpy.xx function equivalent; just manually go through the methods and remove the mutating ones?
** Class wrapper is modular
*** Docstring parser and type string parser can be customized
*** Classes can have optional attribute/method ports
**** Inspectors and attribute/method modules can be created separately
** Use PythonCalc as an example
*** Can be re-implemented as a function with a parseable docstring
*** [RR] PythonCalc is just an example, and it might actually make sense to get rid of it, or do a proper math package with scalar operations (as separate modules, no combobox)
** [RR] TensorFlow to use wrapping as well
*** Very simple (only types 'tensor' & 'variable')

=== November 11, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapping numpy's classes using numpydoc (ndarray)
*** Wrapping constructor arguments, attribute getters/setters as module ports
**** Then how to access attributes afterwards?
***** Use input value port to class modules?
*** Wrap methods as modules? E.g., `ndarray.shape`.
*** Function wrapping is almost a subset of class wrapping
**** May be able to use the same parsing/execution methods
** VTK's non-getter/setter methods could be wrapped as modules
*** We could then remove extra logic in interpreter for keeping function order
** Bokeh uses autogenerated docstrings
*** We may be able to read the specification directly

* [RR] [https://github.com/VisTrails/VisTrails/pull/1138 TensorFlow package]
** Basic setup working, can execute the Mandelbrot example
** Will autogenerate the operations

=== November 4, 2015 ===
'''Updates'''
* [RR] Interpreter work requires a fix for [https://github.com/VisTrails/VisTrails/issues/1137 DB issue #1137]
* [DK] Kitware's Resonant [http://www.kitware.com/source/home/post/173]
** [https://github.com/girder/girder Girder]: data management system
** [https://github.com/Kitware/romanesco Romanesco]: execution engine, uses [http://www.celeryproject.org/ Celery] for task management
** Resonant Flow: web app for editing and executing workflows

'''Items to Discuss'''
* [TE] Added OSX Lion (10.7) VM on build machine using vagrant (seems ok with license?)
** New builds works on Lion
** Change the minimum requirement to 10.7?
* [TE] Package wrapping
* Added upgrade suggestions using 2 spec versions ([http://pastebin.com/30XUU8Gp example])
** using name edit distance to find matches
** Could use something better like port similarity for modules, and type similarity for ports
** Should write python upgrade code?
** Added spec to sklearn package
*** Can now diff spec versions and keep the spec static
*** There will be problems with downgrades and package versions

=== October 29, 2015 ===
'''Updates'''
* [TE] nightly-build-mac fixed (Needed to approve xcode license)

'''Items to Discuss'''
* [TE] matplotlib wrapper
** ported to general spec
** Diff can be used on general spec
*** Only needed minor changes
*** Fixed indexing bug that corrupted specs
*** Can now move diff tools to core/wrapper
** Add new plots?
*** New plots in mpl 1.3: eventplot
*** New plots in mpl 1.4: angle_spectrum, magnitude_spectrum, phase_spectrum', violinplot
*** No new plots in mpl 1.5 (from looking at boilerplate.py)

=== October 21, 2015 ===
'''Updates'''
* [RR] Alexis has arrived, will be working with [RR] on a more efficient interpreter

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package]
** Supporting multiple package versions
*** Check which version can be loaded [https://github.com/VisTrails/VisTrails/pull/1135 #1135]
*** We cannot show version requirements in the list of packages because old packages are loaded when importing the codepath
** Visual diff does not work well, but we can use the spec differ to see differences.
** Unifying vtk and matplotlib wrapping specs (WIP)
*** And porting matplotlibs spec differ to work on the general spec
*** Spec differ can then be used on vtk and other packages in the future
*** Will enable automatic upgrade generation
* [RR] Rework interpreter
** restore abstraction between interpreter/module code
** build looping, streaming, caching into the interpreter
** rework cache
** look into parallelism once basic functionality is there

=== October 14, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package] (adding numpydoc parser)

=== October 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/tree/fix-matplotlib-parser New matplotlib parser] (adding numpydoc parser)
** Added numpydoc attribute parser for plots.
*** TODO: Need better port spec reconciliation with call signature parser.
*** We can create a general numpydoc parser, but attribute types are unique to matplotlib.
** Needs package versioning
*** New spec will not support matplotlib < v1.4 due to changed path to axes classes.
*** Load spec version corresponding to installed matplotlib version?
*** Need version downgrades?

=== September 30, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Updating Matplotlib parser
** Matplotlib docstring parser fails on numpy docstrings
** I have [https://github.com/VisTrails/VisTrails/commit/eae8b0c16260810587e47c41cab53552cbb3cf0a added basic numpydoc parsing]
*** Only used by a few docstrings so far
*** Parsing uses many sources (class tables, signatures, ACCEPTS, method docstrings, definition parsing).
** Caswell said they were thinking about moving to traitlets, but this is not ready yet

=== September 23, 2015 ===
'''Updates'''
* [TE] VisTrails 2.2.3 released
** Also have pushed to PyPI, binstar, etc.
** Sourceforge vs. GitHub
*** should be able to host releases on GitHub
*** nightly binaries pushed to sf each night
*** old binaries?
* [TE] Re-wrapping MatPlotlib
** Keep static generation - Docstrings are brittle beween matplotlib versions
** Keep generating the executable classes - but create functions, not vistrails Modules
*** Why is there so much patching?
** Re-implemented Alternate PortSpec for InputPortSpec
*** It will now inherit specs from parent (No need to reimplement)
** Module upgrades?

'''Items to Discuss'''

=== September 16, 2015 ===
'''Updates'''
* [TE] Job Monitor tests and documentation done
** OK to leave document package in packages directory?

'''Items to Discuss'''
* [TE] Library wrapping: How to do code patching? [https://docs.google.com/drawings/d/1Sh3eOXot6v2y880jHKQrqXqAwr-0aoqYligg3z8G8MY/edit?usp=sharing Wrapping diagram]
** Insert code into module template (Old VTK code)
** Patch the library that is called (New VTK code)
** Somehow store code in spec and apply when executed?
*** Executed code needs at a minimum access to inputs, outputs, current class
*** Use standard input/output dict and obj reference that the code operates on?
*** Can this be done while keeping the execution abstract?

* Do new release now?

=== September 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* New release?
** [RR] wants reprounzip
** tej changes & doc
** job monitor & jobmixin fixes
** mongodb
** reprounzip
** warning: MplFigure type is int
** tabledata: add Reshape, DictoToTable & ListToTable, fix ListToTable with numpy arrays
** PythonSource can have same name for an input & output
** don't show spreadsheet at exit

=== September 2, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Limit autosaves? [https://github.com/VisTrails/VisTrails/pull/1126 #1126]

=== August 26, 2015 ===
'''Updates'''
* [TE] Added Job support to Parameter Explorations (Requested by Colin), and Mashups
** specify job ids, need to specify different ids for parameter explorations since they have the same version id
** how to deal with parameters passed in on command line
* [General] provenance: should be creating a new version when we execute workflow with changed parameters?
** currently, custom_params annotation stores this in provenance currently
** [RR] API doesn't record provenance if passing in parameters: http://git.io/vsAA5
'''Items to Discuss'''

=== August 19, 2015 ===
'''Updates'''
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [TE] Working on Job Monitor documentation

'''Items to Discuss'''
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [TE] Stop testing VisTrails 2.0?

=== August 12, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Build broken on Travis; because of IPython 4 released today? ([https://travis-ci.org/VisTrails/VisTrails/builds/75279795 build 992]; [https://github.com/VisTrails/VisTrails/issues/1123 #1123])

=== August 5, 2015 ===
'''Updates'''
* [TE] Fixes to Jobs
** Could not delete jobs
** Could not run job in group
** Job not reset when calling ModuleSuspended
** Added deleting job from context menu
* [RR] Writing documentation for everything [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

'''Items to Discuss'''

=== July 29, 2015 ===
'''Updates'''
* RR still looking into new interpreter thing
** Goal is to take out scheduling logic from Module so it can be split in multiple processes, and so that smarter strategies can be added in time
** This means some work on packages
** Spreadsheet can live in kernel process? Still some UI stuff that will take work (changing configuration, persistent archive's viewer, ...)
* [TE] Problems running examples [https://github.com/VisTrails/VisTrails/pull/1111 #1111]
** Testing of more examples requires additional packages on the test machines.
** Fixed faulty line-ending in PythonSource:s failing on Python 2.6.
** Test suite now testing SUDSWebServices (If web service is down, test suite will fail)
** preferences.py test failed reloading 'dialogs' package, switched to using 'URL'.

'''Items to Discuss'''

=== July 22, 2015 ===
'''Updates'''
* [TE] mailing lists back online
* [TE] Working on [https://github.com/VisTrails/VisTrails/issues/1107 #1107]
* [RR] Working on ReproZip package

'''Items to Discuss'''
* [RR] MongoDB package [https://github.com/VisTrails/VisTrails/pull/1106 #1106]
* [RR] Example for tej docs? [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

=== July 15, 2015 ===
'''Updates'''
* 2.2.2 released

'''Items to Discuss'''
* RR is considering executing everything in an IPython kernel (i.e. separate Python interpreter, like the one spawned for a notebook)
** It's a separate process that we can restart without restarting the app/gui
** We can isolate the execution environment (e.g. for the server)
** We can run the whole thing remotely (if your data is elsewhere, just run VisTrails locally and the pipeline elsewhere)
** Pipeline execution no longer makes the interface hang, it just makes the kernel hang (but that's fine)
** We can use notebooks as modules (probably way nicer than the PythonSource module)
** We can run multiple kernels so long as the ports carry things that are serializable
*** meaning we can put the multithreaded-interpreter without all the hacky parts it has now
*** we can run IPython kernels in all the languages IPython supports, [https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages currently 46]

=== July 8, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Buildbot github hook not working after IP address change
* [TE] No reference to VistrailsApplication ([https://github.com/VisTrails/VisTrails/issues/1103 #1103])
** [RR] Added PR [https://github.com/VisTrails/VisTrails/pull/1104 #1104]
* [TE] Reopening VT file after saving with bundled subworkflow won't offer subworkflow upgrade ([https://github.com/VisTrails/VisTrails/issues/1102 #1102])
** allow manual delete to fix right now
** fix this on top of the use-uuid branch
* [TE] Release VisTrails 2.2.1? ([https://github.com/VisTrails/VisTrails/blob/v2.2/CHANGELOG CHANGELOG])
** [https://github.com/VisTrails/VisTrails/pull/1093 output-modules-use-global-dir]
** [https://github.com/VisTrails/VisTrails/milestones/version%202.2 Current issues for 2.2]

=== July 1, 2015 ===
'''Updates'''
* [TE] PROV fixed
* [TE] Working on subworkflow issues
* [RR] Considering reworking the controller (log vs exception problem, retained upgrades causing interferences) and also the interpreter (IPython?)

'''Items to Discuss'''

=== June 24, 2015 ===
'''Updates'''

'''Items to Discuss'''
* UV-CDAT
* [TE] Can a cyclic workflow be valid? ([https://github.com/VisTrails/VisTrails/issues/1097 #1097])
** focus on disabling the ability to create cyclic pipelines because more things break than just this with a cyclic pipeline
* [RR] Relative paths ([https://github.com/VisTrails/VisTrails/pull/1057 #1057])
** This interacts with the new bundle; how do handle packing files inside the VT bundle?

=== June 17, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] current_version and reusing existing upgrades are broken ([https://github.com/VisTrails/VisTrails/issues/1095 ticket #1095])
** Could be that export to PROV is using an unflushed upgrade pipeline?
** current_version would then be correct.
** It may work to flush the actions before exporting?

=== June 10, 2015 ===
'''Updates'''
* DAT: fixed VTK issue on Linux and Mac
* Still crashes on Windows. Need help! Reminder: this works in the VisTrails spreadsheet (QCellPresenter), although no widget get changed there during a drag
** Is it a VTK bug?
** Is it simply impossible to change widgets during the drag, should we do it a different way?
** Did I miss something that is done in VisTrails but somehow not in DAT?
** Low prio, UV-CDAT doesn't run on Windows anyway

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 Updated pull request])
* Single instance code and batch mode

=== June 3, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 pr])
** Requires fixes to command line parameters, Output modules, and batch mode
** How to test this
** Updated missing/outdated flags
** Fixed view issues when generating graphs
* [TE] batch mode
** SpreadsheetOutput not enabled in batch mode. Should we check is_running_gui instead?
** Other instance setting flags from caller
** Is graphsAsPdf replacing spreadsheetDumpPdf?
** graphsAsPdf true by Default?
** Batch mode executing by default (Not needed when generating graphs)
** Re-added workflowInfo as withWorkflowInfo for writing graph and xml workflow
** [DK] batch mode should be outputting to files or stdout, shouldn't always trigger SpreadsheetMode
** execute flag, maybe make execution the default and allow a "--no-execute" if you only want to capture graphs, for example

=== May 27, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] API question
** http://lists.vistrails.org/pipermail/vistrails-users/2015-May/000357.html
* Status of DAT
** Can add VCS plot to DAT but need to work on configuration windows
** Documentation for graphics templates for UV-CDAT/vcs?
* Qt support?

=== May 20, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Reviving the DAT, integrating scripting & porting UV-CDAT!
** On [https://github.com/VisTrails/DAT GitHub] ([https://github.com/VisTrails/DAT/issues issues])
** Merging 2 years of development taking longer than expected, but getting there. The plan is to get the patches in VisTrails and never fork again, we never want to get in UV-CDAT's situation (and don't need to).
** VTK cell works fine on Linux but there was flickering on Mac & Windows before; still issues on Mac (Windows status unknown)
** Can get a VCS plot soon (but will need VTK cell fix)
** Integrate in UV-CDAT's build system (so we have cdms, VCS, ...) -> RR can do this, low priority
** How do we integrate scripting?
*** We want to be able to seamlessly make changes to a plot by changing Python code
*** Define new plots by entering Python code without writing modules/packages?
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 13, 2015 ===
'''Updates'''
* [RR] Test skipping whitelist ([https://github.com/VisTrails/VisTrails/pull/1069 #1069]) -- low priority
* [RR] Custom matplotlib modules can't be compatible with both 2.1 and 2.2 ([https://github.com/VisTrails/VisTrails/issues/1067 #1067]); should be fixed for ALPS ([https://github.com/VisTrails/VisTrails/issues/1070 #1070])

'''Items to Discuss'''
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 7, 2015 ===
'''Updates'''
* [RR] Export/import workflow to Python working!

'''Items to Discuss'''
* [Claudio] UV-CDAT
** The UV-CDAT project is the biggest user base of VisTrails
** VisTrails package management provides a lot of friction towards people plugging in their code
** Need to make it easy to integrate your random Python scripts in the system without having to deal with all the boilerplate, at least in the first step
** [RR] argues that modules are still good; UV-CDAT shouldn't move towards a purely script-based backend
** [RR] export/import with Python could reduce a lot of that friction by allowing 1) to edit workflow as Python 2) to open up boxes automatically if needed code doesn't match actual modules
** ...

=== April 29, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] <strike>Abstractions</strike> subworkflows status ([https://github.com/VisTrails/VisTrails/labels/subworkflows tickets])
* [RR] matplotlib compatibility (2.1 & 2.2), [https://github.com/VisTrails/VisTrails/issues/1067 #1067]
** RR to try and fix ALPS matplotlib modules

=== April 22, 2015 ===
'''Updates'''
* 2.2.0 has been released!
* Windows issue (via email from Ryan)
** issue with manifest file (may be a new file in VTK6?)
** Tommy has regenerated new Windows builds
* Binaries, pypi, and conda released
* [RR] Export as script
* Python sources using VTK need to switch to SetInputData (users should be aware of this)

=== April 15, 2015 ===
'''Updates'''
* Ready for 2.2.0 (apart from binary/deps issues)
** Missing some libs (scikit-learn, tej, tdparser, SQLAlchemy+connectors
** Windows: runvistrails.py is no longer used, so the PATH is wrong
** Windows: pip is broken, but it probably wouldn't work anyway because of permission issues (disable this?)
* Queries, upgrades and getPipeline() usage ([https://github.com/VisTrails/VisTrails/issues/1054 #1054])
** Getting a pipeline with getPipeline() is not safe: it might return an invalid pipeline
** This is used in many places throughout the code, like queries
** Upgrading would require going through the controller, but that creates new actions
* [TC] Avoid copying a module's output if it's used as input by exactly one downstream module ([https://github.com/VisTrails/VisTrails/issues/1060 #1060]) (useful for big numpy arrays you can update in-place)

=== April 8, 2015 ===
'''Updates'''
* [DK] Merged RR's changes for output modules (1012 and 1013)
** RR will merge remaining changes, then create v2.2 branch!

'''Items to Discuss'''
* BNL need numpy array to VTK image
** Looks like VTK has some helpers for this
** We will help if issues arise
** Will contribute back to VisTrails package
* Upgrade issue: [https://github.com/VisTrails/VisTrails/issues/1017 #1017]
** Automatic upgrades should happen between versions of provided upgrades
** Our existing upgrades work around this so it doesn't need to be 2.2.0
* Corner-case VTK modules
** No longer need VTKCell input port, so don't interfere with registry and API anymore
** Still work weirdly, people probably shouldn't use them
** But we have lots of clunky modules since we wrap the whole of VTK; some people might rely on this and know how to use them, let's keep them anyway
** Ready for 2.2.0

=== April 1, 2015 ===
'''Updates'''
* [RR] UV-CDAT: bugfixing for 2.2, long-term plans: implement scripting import/export in VisTrails, port to UV-CDAT
* Possibly, try to move to regular VisTrails to use new features

'''Items to Discuss'''
* 2.2 release: nothing much is pending anymore, release next week?
** [TE] vtkExporter classes [https://github.com/VisTrails/VisTrails/issues/1032 #1032]
** [RR] Hiding upgrades in version tree might make it (or might be 2.2.1 so we can test it out) [https://github.com/VisTrails/VisTrails/issues/949 #949]
** Output modules changes to go in
* add note to documentation about order of parameters in VTK
* add issue about exporter upgrades if not already there

=== March 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* 2.2 release
** Checklist on Github: https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist
** Review output modules
** RR has a couple more issues to fix
** Ready to go -- sign app package for OSX? [https://github.com/VisTrails/VisTrails/issues/984 #984] We need access to the Apple Membership team

=== March 18, 2015 ===
'''Updates'''
* [TE] VTK6 works

'''Items to Discuss'''
* [RR] Release v2.1.5 with backported tabledata?
** MTA example needs updated tabledata (for JoinTables)
** Google Maps package still not available
* [RR] Work torward v2.2.0?
** changes:
*** new persistence
*** API changes
*** output module changes (upgrades?), maintain cells but try to upgrade
*** not wrapping stuff
*** VTK6? yes
*** JobSubmission stuff?
*** relabeling for upgrades [https://github.com/VisTrails/VisTrails/issues/949 #949]
** makes sense, needs the tree view code to be updated, check selection
** See [https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist 2.2 checklist]
* Discussion of [https://github.com/VisTrails/VisTrails/issues/1016 #1016]
** plumbing between outputs and output modes, how to define a mode that works for many outputs without writing for each output?

=== March 11, 2015 ===
'''Updates'''
* [RR] persistent_archive done; merge? ([https://github.com/VisTrails/VisTrails/pull/755 #755])
** note about the focus events for widgets
** TE be aware of file_archive for future binaries that include persistent_archive
* [TE] [https://github.com/VisTrails/VisTrails/pull/998 New VTK package] finished

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails? (see last week; decision needed)
** RR email to JF about this
** yes; email sent to Github
* [RR] Switching order of output ports ([https://github.com/VisTrails/VisTrails/pull/1006 #1006])
** added port specs are sorted at a separate spot (Module.*_port_specs properties) than those in the registry (which are sorted in the registry), but those two lists are just combined without respect to sort keys
** need to determine whether the two lists should be merged or remain distinct
** should make sure that order of input ports and output ports makes parallel connections for things with same order
** DK suggests breaking backward compatibility here: workflows still run, can fix easily if a problem in an existing package.
* [RR] Question about output modes ([https://github.com/VisTrails/VisTrails/pull/1007 #1007]), how to integrate in API ([https://github.com/VisTrails/VisTrails/pull/24 #24])
** Should ImageFileMode be removed? ("image" is not a mode, "file" is)
** ImageOutput missing?
** Feel free to change how formats works
* [TE] Test suite segfaults on Fedora 17 virtualbox. Install newer version? (Support ended in 2013)

=== March 4, 2015 ===
'''Updates'''
* [TE] VTK wrapper
** Works on VTK 5.10
** Still need to test VTK 6
** New general wrappers for python functions and classes

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails?
** When [http://i.imgur.com/UTY2qfg.png filing a pull request] from UV-CDAT/VisTrails, VisTrails/VisTrails is selected by default
** People keep forgetting to change the default ([https://github.com/VisTrails/VisTrails/pull/956 #956] [https://github.com/VisTrails/VisTrails/pull/968 #968] [https://github.com/VisTrails/VisTrails/pull/999 #999] [https://github.com/VisTrails/VisTrails/pull/1000 #1000] [https://github.com/VisTrails/VisTrails/pull/1003 #1003] [https://github.com/VisTrails/VisTrails/pull/1004 #1004] [https://github.com/VisTrails/VisTrails/pull/1005 #1005])
** Only way to change that is to not have it marked as a fork of VisTrails/VisTrails
** Github staff [https://gist.github.com/remram44/b364c24ef1e462ce6e2f can make that change for us]; should we do it?
** Juliana: comments on this? visibility vs. convenience/annoyance for developers
* [RR] What about [https://github.com/VisTrails/VisTrails/issues/991 #991]?

=== February 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] vtkviewcell for infovis support, can we unify with VTKCell?
** need to test this
* [TE] vtk wrapping
** Mostly finished
** VTK 5.10 produce incorrect results with old wrapping
*** Old wrapper is based mostly on VTK 4
*** Most vtk_examples affected
*** [http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Replacement_of_SetInput]
*** should be able to upgrade from SetInput to SetInputData (need to drop GetOutput and replace with self ports)
*** can we change vtkInstance to just return self and not wrap things
** terminator example not working under 5.8?
* How does VTK wrapping fit into general wrapping framework?
* [RR] new persistence package

=== February 18, 2015 ===
'''Updates'''
* [RR] New VisTrails API and IPython integration ([https://github.com/VisTrails/VisTrails/pull/24 #24])

'''Items to Discuss'''
* [TE] VTK wrapping
** [https://gist.github.com/rexissimus/16b74693545b5e7c1035 Benchmarking vtk package]
*** Old: 24.7 seconds
*** New: 10.5 seconds (Except first time that adds 8 sec)
**** The parsing that calls is_abstract (that tries to instanciate all vtk classes) is now only run the first time.
**** get_items_from_sigstring takes 2 seconds, maybe we can use a lookup dict for already computed sigstrings?
** Now using a general python function wrapper
*** VTK classes are wrapped into python function that does not depend on vistrails
*** VTK functions can be executed without vistrails
*** The spec maps functions into vistrails modules, but can also describe wrapping
*** A general python function wrapper that supports
**** kwarg inputs
**** single, list, dict outputs
**** callback for progress reporting
**** temporary file generator for using FilePool
**** optional output generation
*** Creating specs:
***** Create spec by hand
***** Auto-create spec outline (TODO) and manually finish it
***** Dynamically create spec (VTK)
***** Implement documentation wrappers (Can use scikitlearn wrapper to wrap numpydoc) (TODO)
***** Classes as bad functions needs to be wrapped in new functions before they are wrapped. This is different for each package.
****** Classes is hard: Like VTK, and matplotlib. Scikit-learn does still not wrap classes
***** Spec diffing and patching could be done using code from matplotlib.
** Still needs upgrades from old VTK package
*** Is it possible to dynamically wrap functions, e.g, you see a SetFunc and just remove the 'Set' prefix. Or do you need to create a complete mapping?

=== February 11, 2015 ===
'''Updates'''
* Update from Friday's meeting
** discussed VisTrails internals
** discussed wrapping
*** xml discussion, hard to modify because tied to db code
*** TE has made it possible to add the schema-defined attributes to the intermediate representation
*** higher-level operations on the port specs
** make sure the simple case works
*** [JF] take a simple package with documentation and figure out what the base case for wrapping is

'''Items to Discuss'''
* [TE] VTK wrapping
** Dynamic loading works
** Reading XML is fast enough, but [https://gist.github.com/rexissimus/8272d3c776ccfa115d82 unserializing data is slow]
** Working on patterns for patching
** Matplotlib has many advanced patterns like argument ordering, nested arguments, alternateSpecs, output types.
*** Having all this in a general wrapper might confuse users?
** [RR] Delay module (except for identifiers) until you need it---e.g. don't deal with port specs, etc. until necessary
* Scripting Support [https://github.com/VisTrails/VisTrails/pull/950 #950]
** [RR] Issue with getting code from modules
** Design a simple solution
** [JF] Couldn't you use modules as black boxes without conversion, just to call into modules/subworkflows easily from e.g. IPython?
*** [RR] This is a job for the API, and a very separate use case. See [https://github.com/VisTrails/VisTrails/pull/24 #24]

=== February 4, 2015 ===
'''Updates'''

'''Items to Discuss'''
* Wrapping
** Format to use? Currently XML (like current matplotlib)
*** JSON and YAML have simple "to python dictionary" methods
*** But don't stream
*** YAML a lot easier for humans
** [DK] vtk-new-package also changes parameter names, creates enumerations
*** intermediate schema needs to be extensible
*** packages will want to store there specific infos for compute() method generation
*** also might have specs-altering info, like matplotlib's alternateSpec
** representation to code , registry already has schema for some aspects
** [RR] We might want to see if Module subclasses can be created lazily
*** no need to create all the classes just to register them in the registry and never actually use most of them
*** future effort
* [RR] Where should VisTrails packages live?
** tej installs as 'vistrailspkg.tej', TE installed it as 'userpackages.tej'
** Currently, standard packages are 'vistrails.packages.', user packages are 'userpackages.' and packages loaded through pkg_resources might be anything
** [RR] Use 'vistrailspkg.' everywhere?
** Long-term effort to simplify package distribution/installation (and have VisTrails get them automatically?)

=== January 28, 2015 ===
'''Updates'''
* T. Caswell to come visit on Fri 6 to discuss wrapping work

'''Items to Discuss'''
* [TE] New VTK wrapping
** Current code by DK seems a good deal faster
** Generates XML that can be patched/tweaked, generates Python code from it, VisTrails only loads generated Python code
** RR would rather have VisTrails load intermediate representation (= XML) directly, wants to make sure this is not slower
** The goal is to turn the intermediate step into something generic that would be used for every wrapped package (vtk, numpy, matplotlib, sklearn, java) instead of each having its own
** TC has its own code at [https://github.com/Nikea/VTTools/blob/master/vttools/wrap_lib.py github:VTTools] which parses numpy docstrings and generates modules, doesn't yet handle classes or persist anything
* Web crawler
** Right now, TE starts jobs for "start crawler", "stop crawler", "install classifier"
** RR would rather have the crawling be a job as far as VisTrails and tej are concerned
** The whole thing would be one pipeline: load examples, train classifier, start crawler [check for job, kill previous one, upload model, start processes], get snapshot, visualize
*** Need some support in tej and job submission system: long-running jobs, stop a job (wait for it to finish?), restart a job even though results are cached

=== January 21, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Unified wrapping method discussion [https://github.com/VisTrails/VisTrails/issues/991 #991]
** TE to work on reusable method with intermediate representation, starting with VTK
* [RR] Examples for scikit-learn: JF has an old example using Weka with parameter exploration (not currently in source tree)
** AM's examples are enough
* [AM] scikit-learn package is done, merge it in? [https://github.com/VisTrails/VisTrails/pull/955#issuecomment-70286788 #955]
** RR will merge
* [RR] What should copyright headers say? [https://github.com/VisTrails/VisTrails/pull/994#issuecomment-70173935 #994]
** Let's keep everything in there: Utah/Poly/NYU

=== January 14, 2015 ===
'''Updates'''
* [TE] Working on classifier
* [RR] Scripting integration, work in progress

'''Items to Discuss'''
* [RR] Unified wrapping method discussion ([https://github.com/VisTrails/VisTrails/issues/991 #991])
** Let's talk next week, [AM] and [DK] are not here

=== January 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* make sure that we address critical issues, questions, and pending review branches in a timely manner
* scripting support
** [RR] no issues if we want to just keep annotations in the generated code to allow the link back to a workflow
** [RR] can translate from workflow to script, working on script to workflow
** will work for parameter value changes, structural changes require changes to the annotations
** need to publish best practices here
** would be cool to do looping in scripts (easier interface than with workflows)
* notebook support (convert form notebook to workflow)
** RR will sync with FC on this
* Issue with console in built-from-scratch
** [TC] iPython rearranged some of the completion stuff in 2.2 and 2.3
** binary has old version of iPython -> 1.0.0, should we update?
* [TC] automated wrapping of numpy and scipy
** discovered a bunch of malformed documentation in numpy and scipy
** has github repo for vistrails tools
** example modules wrap a bunch of R stuff (not baked in, just how things are)
** will be pushing wrapping logic up
** port names forbidden (window and domain)
** have an import hook to get from yaml directly to VisTrails Modules
** should work for any python modules with well-formed numpy docstrings.
* [Action] should make it clear in documentation that Constant now means serializable not that the value doesn't change (e.g. List)
* [TC] might be interesting to try to build components of matplotlib and accumulate in figure (long-term project, but thinking about how this might work)
* [TE] build and build scripts
** completely automatic, buildbot
** need to set the build machines for the environment we want for the binary
** would virtualenv work here?
** [TC] anaconda can pin versions, potential path to test different configurations
** Q: upload nightly binary builds? A: makes sense, make sure they are well-labeled
* sourceforge stats: e.g. http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07
* package issues (see Remi's message)
* [TE] Scope of tej
** Support single ssh commands?
** Queue can be used as a remote machine (crawler is using queue.call*)
* SourceForge stats: http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07

== Older meetings ==
* [[Development/2014]]
* [[Development/2013]]
* [[Development/2012]]
* [[Development/2011]]
* [[Development/2010]]

Development

2016-07-06T15:03:01Z

Tommy: /* 2016 */

<div class="nonumtoc toclimit-1">
__TOC__
</div>

See also the [https://github.com/VisTrails/VisTrails/wiki/Development Github wiki]

== 2016 ==

=== July 6, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Using vistrails API in scripting [https://gist.github.com/rexissimus/034d9c4dedc3299a079e84981dedd8c7 example 1 (API with VTK)] [https://gist.github.com/rexissimus/a4a9ca6c08d4058c64967d2b35415fd5 example 2 (DownloadFile only)]
** Call module in script using vistrails API
** Can be used when no export method is defined.
* [TE] [https://github.com/VisTrails/VisTrails/commit/c76c109349769fee1280f85c22678380a2f9cd39 Server news bug] Critical?

=== June 29, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Export VTK as python script
** Works on Terminator (Isosurface, Volume Rendering, clipping plane, combined rendering) [https://gist.github.com/rexissimus/16caf5200802e150296f62a0c7844c5a example]
** Preludes (imports) still need improvements
** Works with vtkInteractionHandler (clipping plane)
** Resulting clipping plane is incorrect? (supposed to hide one side of the plane)
** vtkRendererOutput Uses VTKRenderWindow as output
*** Should support different output modes?
*** Does not work with multiple outputs (Next cell is displayed when current is closed)
*** Uses wrapped vtkInstance (as vvtk)
**** Create new patch system with code that can be used both in vistrails and in a python script?

=== June 22, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Fix for upgraded analogies (PR [https://github.com/VisTrails/VisTrails/pull/1177 #1177])
** Uses module location to find module remap (The best we can do right now?)
** Also fixes remapped port names for connections to existing modules
** May still fail on complex upgrades like adding a function on an upgraded module that has a different port name

* [TE] Working on exporting wrapped libraries (VTK)

=== June 15, 2016 ===

'''Updates'''
* [TE] Added depth logic to python script exporter ([https://github.com/VisTrails/VisTrails/commit/50f220e4f6abe5a7bb8689f73f456f43df2dbc12 full commit])
** Fully implements connection merging and list looping

'''Items to Discuss'''

* [TE] Making analogy work on upgraded workflows ([https://github.com/VisTrails/VisTrails/issues/1175 #1175])
** Analogy only works We need to use the non-upgraded action chain
** But pipelines need to be valid (matcher uses module portspecs)
** Tried to get upgrade remap from upgrade action, but this seems impossible
** Use module location instead?
*** Location should be identical for one-to-one module upgrades

=== June 1, 2016 ===

'''Updates'''
* VisTrails 2.2.4 announced (finally)
** 5 survey replies
** 47 downloads last week

'''Items to Discuss'''
* [TE] Export VTK as script (python-wrapper)
** to_python_script
*** needs the pipeline (or at least the connections)
**** Should not generate code for any possible VTK method (exporter detects which ports is used in the source)
**** VTK needs to know connection order
**** Adding functions directly to the script results in nicer code
** Add support for multiple input connections
** Add support for list looping

=== May 25, 2016 ===

'''Updates'''
* Mailing-list fixed
* Getting stats from the "server news" mechanism (via [https://github.com/remram44/apache-log-info parser])

'''Items to Discuss'''
* [RR] Alexis doing writeup on VisTrails, curious about interesting streaming use-cases (and potential future users)
* [TE] Union ports
** Show union ports in pipeline (DEMO)

=== May 18, 2016 ===

'''Items to Discuss'''
* [TE] mailing list still down - Julio working on it
* [TE] Improved union port
** New schema 1.0.5 adds portitem.union string attribute
** Works with pipeline view, parameter exploration view, and mashup view
** Should work well for matplotlib
** Use with VTK ports?
*** It uses [item_1,item_2] style ports usually with different tuple length.
* [TE] Remove emacs dependency from db generate [https://github.com/VisTrails/VisTrails/issues/1173 #1173]

=== May 11, 2016 ===

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]
** GUI-based solution [https://github.com/VisTrails/VisTrails/tree/union-port Branch union-port] Demo?
*** Shows single port for all ports with same sort_key
*** Select specific type when adding/showing
*** Only one type should be visible on the module at any time
*** Making tuple parameters union types is probably too complicated
*** Should work with alternate specs like matplotlib (if sort_key is defined correctly)

* [TE] Feature suggestion: Let connections connect to functions/parameters
** Show functions and parameters as ports and toggle port visibility directly for functions and parameters
** Use separate views for ports and functions (like before)
*** Allow rearranging of functions
** Pros:
*** Supports ordered connections. Create 2 functions, make them visible as ports, make connections to them.
**** We can also have, e.g., a line joining the ports on the module to indicate they are part of a list.
**** Makes List module simpler
*** Connect to parameter in tuple
*** Functions that are visible on the module can connect to an actual function, and not just to the first one it finds.
*** Can replace operation modules (in python-wrapper) in some cases for, e.g., numpy.
** Cons:
*** Interface more complicated and crowded
*** More difficult for users to grasp?
*** No immediate use case
*** Makes no union type for tuple parameters a bigger problem.

* [TE] Publish user survey?
** No response from vistrails release yet
** Not announced on vistrails-users yet.

=== May 4, 2016 ===
'''Updates'''
* VisTrails 2.2.4 released

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]

=== April 27, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Wrapping Bokeh
** New method type "operation"
*** Transforms Figure->Glyph->Output into Glyph->Figure->Output
**** Glyph sets function name and arguments as output
***** Not serializable, but should always be computed together with the subject of the operation.
**** Figure applies Glyph operation on itself
*** Useful for matplotlib?
**** matplotlib currently find actors by searching upstream?
**** But this is more difficult since matplotlib is not function-based.
** New "union" port type
*** Turns "x(float), x(list)" into "x (float, list)" and uses first set value
**** Uses only first value in tuple
**** Bokeh have many properties that support (list, string, Float)
*** Does not work with depth=1 types (e.g. Float of depth 1)
**** Turn Depth 1 types with known type into lists?

* [TE] New bugfix release
** Finalize survey

=== April 20, 2016 ===
'''Updates'''
* Merged upgrade fixes
** Now has infinite loop test
** loop test now correctly loops 5 times
*** remap_module used wrong (current) package version when creating ModuleDescriptor
* Fixed multi-step group upgrades (PR: [https://github.com/VisTrails/VisTrails/issues/1168 #1168])

'''Items to Discuss'''
* New bugfix release
** Merge usagestats
** Need to finalize survey

=== April 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Chaining upgrades done ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Replace "Upgrade" description annotation with "upgraded_from" annotation to identify which tags to hide?

* [TE] Iterating handle_invalid_pipeline ([https://github.com/VisTrails/VisTrails/pull/1165 #1165])
** Not based on [https://github.com/VisTrails/VisTrails/tree/chain-upgrades-loop chain-upgrades-loop]
** Cherry-pick test to preserve source?
** Need maxPipelineFixAttempts option?
*** The code is now smarter about recursion, so max attempts will "probably" never be reached.
** Need [https://github.com/VisTrails/VisTrails/commit/0ef0667426937eddb1d1c1e397f0657ffec039a9 debug messages]?
*** Would need to be moved into handle_invalid_pipeline

=== April 6, 2016 ===
'''Updates'''
* [TE] Query View improvements
** Done except for displaying "Version Info" and #1164
* [RR] Working on finishing new interpreter (finally!)

'''Items to Discuss'''
* [TE] Chaining upgrades ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Try latest upgrade first, then previous.
** If all fail, select latest upgrade?

=== March 30, 2016 ===
'''Updates'''

'''Items to Discuss'''

* [TE] Query View improvements
** Unified do_version_switch and get_upgrades as validate_version()
** Problems with query view using its own controller
*** Fixed module info not being displayed for query results
*** Still no version info for query results
*** Still an issue with version query view not being updated

=== March 23, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Usage reporting almost ready to go
** Need to record whether specific features are used: paramexpore, mashup, query
*** [DK] Record if LaTeX extension is used? But hard to distinguish from direct batch invocation
** How to record size of vistrail?
*** [DK] IdScope already walks over vistrail, use that
*** but total number of modules and versions doesn't give an idea of average size of individual pipelines

=== March 16, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Upgrades in Query Mode
** Now using code similar to do_version_switch
*** Uses handle_invalid_pipeline
*** Differences: Not using current_pipeline, flushes changes
*** New controller method get_pipeline optimized using cached pipelines (but not current_pipeline)
*** Integrate to avoid repeated code?
*** Use this for query mode?
* [TE] VisTrails 2.2.4 ready for release?
** tej package updated. Others?
* [JF] upgrades and the version tree
* [JF] provenance in Jupyter
* [DK] bundles: [https://github.com/VisTrails/VisTrails/pull/1092 #1092]

=== March 9, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixing search mode
** String query now matches all by default
*** This caused pipeline queries to never match
** String query can search: User/Notes/Tagname/Time/Module name
*** Should we search module names by default? (Disabled by default because it is expensive)
*** Fixed notes search
** '>' parameter queries in documentation but has been removed
** Fixed module matches for upgraded pipelines (By not upgrading pipeline)
*** Upgrades still a problem
*** Add "Upgrade all menu option?" (Or upgrade all on open when `hideUpgrades`)
*** [JF] Allow search on past tags

* [TE] Create new bugfix release
** Finish querying
** Path issue on windows

* [DK] Look into sqlalchemy and new bundle branches

=== March 2, 2016 ===
'''Updates'''
* [TE] Fixed cache bug with port specs
* [TE] VisTrails Next
** Most packages now work
** No qgis for Python 3

'''Items to Discuss'''
** Always dereference symlinks? [https://github.com/VisTrails/VisTrails/issues/1146 #1146]

=== February 23, 2016 ===
'''Updates'''
* [TE] Fixed PythonSource 100% CPU bug
* [TE] VisTrails Next
** Updated [http://opendap.co-ops.nos.noaa.gov/axis/webservices/wind/ NOAA Web Service] examples
*** Now uses REST service, tabledata, and Google Maps
*** Web Service replaced with DownloadFile

'''Items to Discuss'''
* [RR] Couple of fixes are in for API, and tej&reprounzip on the Mac binary. Also new release of tej, and working on anonymous usage reports.
** New 2.2 release soon?
* [RR] Anonymous usage reports
** Sends out info like number of modules & versions, packages used, Python & libs versions, execution time, specific features [https://github.com/VisTrails/VisTrails/pull/1154 #1154]
* [JF] Bring in noWorkflow to track variable dependencies, for the considered Jupyter integration?
* noWorkflow - provenance for python scripts
** Recent work on tracking dependencies
* Also integrates ReproZip with Jupyter
** [http://mybinder.org mybinder]
*** Use with ReproZip to automatically build Jupyter notebook interfaces
* Daves comments on Jupyter integration
** It is possible to identify cell order on the server side
** Not trivial to track order of cells on client side
* How does Galaxy workflows relate to VisTrails?
** Packaging in Galaxy is hard
** Galaxy for biomedical workflows, difficulty making it general
* Action items
** How difficult to track cell dependencies in Jupyter notebooks?
** Use noWorkflow to track cell dependencies?
** How difficult to modify mybinder to use ReproZip packages?

=== February 17, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixed Group memory usage
** Modules in groups are supposed to be freed when done executing
*** Prevented by logger that stored references to the modules (fixed, now using id(module))
*** Prevented by list iterator bug that stored list of modules on the 'self' port bug (fixed)
* [TE] VisTrails Next
** Removed deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** PythonSources will be upgraded
*** Fixes for Python < 3
*** fixes for VTK < 6
** TODOs
*** Remove RemoteQ
**** Port Hadoop to tej (Already have pbs)
*** Merge package wrapper
*** Finish SQLAlchemy branch
*** Finish new bundle branch
** [JF] Will contact Jeff and Matthias about moving to Python 3
* [JF] Query by Example is broken
* [JF] VisTrails Data Cleaning Project
** Use VisTrails to process and explore task-specific data while keeping provenance.
** Remi's Idea
*** Use VisTrails as the backend in a Jupyter notebook
*** Overcome problems with executing cells in random order
**** Interesting research topic, but little interest has yet been noted
*** Interesting to study how such a notebook would be used (Is there notebook usage data available?)
*** Impose restrictions to notebook cell boundaries
*** It will only work for functional operations
*** Can we fix, or detect, non-functional (mutating) operations?
*** Analyse code and data flow and see if it mutates data in unexpected ways?
*** Mutable operations can be created in many ways in Python
* Next meeting Tuesday 11:30

=== February 10, 2016 ===
'''Updates'''

'''Items to Discuss'''
* VisTrails Next
** Test suite passes
*** Python 3 less deterministic, module upgrade order random.
** [RR] updating packages: Reprounzip (pushed), tej, persistent_archive, ...
** All of our packages should run fine :)
** VTK thumbnail comparison works
*** Rendering bug on some systems
**** QVTKCell now inherits QGLWidget
*** Old thumbnails had wrong height due to spreadsheetwindow being too small
**** Fixed by regenerating thumbnails
*** Silenced deprecation messages when generating modules
*** Many new classes in VTK 7
** Remove deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** Will break existing PythonSources
**** Try to upgrade?
*** Old-style packages
**** Or only allow a new style, like __init__.py renamed to info.py? (merge with identifiers.py?)
***** Read info.py without importing package?
*** Fixes for Python < 3
*** Fixes for Qt < 5
*** fixes for VTK < 7
*** Remove self port?

=== February 3, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] [http://lists.vistrails.org/pipermail/vistrails-users/2016-January/000402.html Rendering a .pvd (ParaView) file?]

* VisTrails Next
** All tests but thumbnail comparison passes
** Still issues with gui and more packages needs to be tested
** PythonSource and MplSource upgraded with lib2to3
** Keep contrib packages? Update?
** [https://blog.kitware.com/vtk-7-0-0/ VTK 7 is released]
*** Supports Python 3
*** Will hopefully get into conda and others soon
*** Deprecates a bunch of modules

* [https://travis-ci.org/VisTrails/VisTrails/builds/106743348 Travis builder] for VisTrails Next
** Runs!
** Uses conda
*** Many levels of requirements
**** apt packages
**** conda packages
**** python packages in requirements.txt
**** python packages in setup.py
*** Can probably drop conda. Default builder does not have Qt5, but beta builder do!
*** But useful if we want to use conda in our own build process.
** Lots of errors I do not get locally?

* [http://goo.gl/forms/Z4HBrwaBWL User Survey]
** Have you used any alternatives to vistrails?
*** Relevant? More options?
** How often do you use any of these particular features in VisTrails?
*** Add/Remove alternatives?
** How important would you rank the following potential improvements to VisTrails?
*** Add alternatives?

=== January 27, 2016 ===
'''Updates'''
* New interpreter
** Working prototype soon
** Looping not completely done (and port combination mode: pairwise/cartesian...)
** Need to integrate with VisTrails
*** Compatibility with existing modules
*** Use log controller
*** Want to cache at multiple levels (whole stream/single element of stream)
*** Non-runtime attributes of modules (cache check, automatic conversion check, constant from/to string)

'''Items to Discuss'''
* User Survey

* ZMQ failing on windows (vistrails-users)

* [TE] [https://github.com/VisTrails/VisTrails/pull/1143 Python 3 branch]
** Testsuite almost passes
*** Failing are unicode filenames, some users guide examples, and thumbnail comparisons.
** Fixed issues
*** Signatures are now bytes (convert to string to show in widget)
*** Cannot compare different types, e.g., (None < 1)
**** PortSpec.depth and min/maxConn could be None. (Backport!)
**** cell.row could be None
*** Lots of unicode/bytes fixes to serializations
**** We have encryption implementations in the code! (keychain)
*** Lots of small fixes to package method differences
** Current issues
*** logging widget empty?
*** version tree signals messed up
*** provenance view legend icons black
*** Text do not fit in some widgets
*** VTK thumbnail comparison fails
**** VTK Cells have some faces in wrong direction?
**** Because running in VM?
** Installing on Ubuntu LTS/Latest Mint
*** Install latest matplotlib from pip
*** Install VTK 7.0.0rc2 from source
*** No QtWebEngine binary (controversial) (Must install sip/PyQt5/Qt5 from source)

=== January 20, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Backporting features from Python 3 + PyQt5 + Qt5
** Merged unicode with master ([https://github.com/VisTrails/VisTrails/tree/unicode unicode])
*** One unicode test failing
*** Problem saving to xml
** Used [http://python-future.org/ python-future] to run futurize stage 1 to update legacy (pre 2.6) code ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized unicode-futurized])
*** Updates print to functions 'from __future__ import print_function'
*** Updates exception calls to use 'as'
*** removes most usages of 'long' (mostly used unnecessarily)
**** Only needed for 32-bit support
*** Fixes relative imports (from __future__ import absolute_import)
** Fixing code that is deprecated in Qt 4.8 and removed in Qt 5 ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized-qt5 unicode-futurized-qt5])
*** Updated all signals to new-style
* If we go 2 to 3, this could break packages
** means we should schedule any package format changes for the same time
** e.g., imports should be unrelated to code path (function to load module from package identifier?) (take them out of vistrails.* [https://github.com/VisTrails/VisTrails/pull/1002 #1002])
** any structural changes (e.g. the __init__ versus init thing) (RR thinks it makes sense, though having both named "init" is unfortunate)
** putting package identifier as xml?
*** Python not so bad, plus some stuff in there is Python code (checking dependencies)
** version the APIs?
*** RR planning on versioning vistrails_module.Module, no point versioning the whole package?
* file formats on 2 to 3:
** no real translation/upgrade, but non-ascii values that work on 3 won't load in 2

=== January 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://gist.github.com/rexissimus/dfd27e466427529c385c Porting to Python 3 / PyQt5]
** Basic GUI and execution works
** Minimal work to support 2to3
** Hard to support both PyQt4 and PyQt5

=== January 6, 2016 ===
'''Updates'''
'''Items to Discuss'''
* Updating VisTrails dependencies
** Successfully built [https://gist.github.com/rexissimus/f1a1aada7de1c00a57c7 Win7-64/Python3/PyQt5/Qt5/WebEngine/VTK7]
*** VTK 7 is the first supporting Python 3 but is only in release candidate phase.
**** Next version of VTK 6 is rumored to support Python 3
**** There is a development branch of VTK 6 supporting Python 3
*** Can travis build this?
**** We can skip tests for WebEngine and VTK if needed
** Python 3 [https://python3wos.appspot.com/ showstoppers]
*** No MySQL-python (sqlalchemy supports mysql through other drivers)
*** No suds (there are active forks but we could also drop support?)
* Options for python2/3 support:
** Interpreter could be python2/python3 based on packages
** six layer works but not the easiest to maintain (e.g. in reprozip)
* Drop support for win-64
* Update copyright headers to 2016

== 2015 ==

=== December 30, 2015 ===
'''Updates'''
* Bokeh package finished
** Can output to Browser/IPython/Spreadsheet (Limited functionality in spreadsheet)
'''Items to Discuss'''
* Updating VisTrails dependencies
** Bokeh needs QWebEngine (Chromium) in Qt5 which requires PyQt5
*** Many plotting libraries only work in browsers
*** But Chromium may be a big and controversial dependency
*** Or create a browser version of the spreadsheet?
** Some users have requested Python 3
** Not backwards compatible?
** Target for VisTrails 3.0 with new interpreter?

=== December 16, 2015 ===
'''Updates'''
'''Items to Discuss'''
* Users list question
* [TE] Wrapping Bokeh
** Added bokeh property parser
*** complements numpydoc parser
*** Not all attributes are available, partially because I am using a pre-release version.
** Wrapped modules
*** bokeh.plotting finished (Backwards like matplotlib: Create plot then draw on it)
*** bokeh.charts mostly done (Missing arguments)
** QWebView mostly works (but no zooming or buttons)
*** It would be better to use external browser or QWebEngineView
** Added improvements to wrapper
*** Generalized port translations (Color/Path to native types)
*** Can use multiple docstring/property parsers simultaneously

=== December 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Looking into wrapper
** Will port TensorFlow
** Doing a pass on the wrapper code & doc
*** UX improvements
** Factorize high-level docstring parsers into core.wrapper? (sphinx, numpy, google)
** Problem with name vs module_name (fails sklearn tests because class_by_name() is broken)
** Looking into compressing specs, lazy registration of modules

=== December 2, 2015 ===
'''Updates'''
* [TE] Package wrapping
** Wrapped most of numpy/scipy using __all__
** Added class attribute and method access for classes (Can add to class or to separate inspector module)
** TODO: Document wrapping procedure

'''Items to Discuss'''

=== November 25, 2015 ===
'''Updates'''
* [RR] New interpreter is coming along
** Everything is a stream
** Task system, eventually work-stealing parallelism
** Streams no longer advance in lock-step
*** Allows for constructions like filter, join, sorted-merge
** depth>1 still to be tested, no current plan to allow this through the module interface
*** Through looping though, can do streams of streams

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapped most numpy functions (no polynomials)
** and half of scipy classes and functions
** Added functions manually from documentation (no parseable lists?)
** Focusing on data flow constructs (no property/method access for classes)
*** Using spec diff (empty for now) and dynamic parser (stores spec in .vistrails/)
** Python class/function wrapper now stable
** Add google doc parser?
*** Is there a parser available?

=== November 18, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Numpy class wrapping works
*** Basic type is List, since most types are array_likes.
*** TODO: More classes and functions
*** Some operations are in-place and some aren't, and docstring not super clear
*** [RR] It seems only methods mutate, and most have a numpy.xx function equivalent; just manually go through the methods and remove the mutating ones?
** Class wrapper is modular
*** Docstring parser and type string parser can be customized
*** Classes can have optional attribute/method ports
**** Inspectors and attribute/method modules can be created separately
** Use PythonCalc as an example
*** Can be re-implemented as a function with a parseable docstring
*** [RR] PythonCalc is just an example, and it might actually make sense to get rid of it, or do a proper math package with scalar operations (as separate modules, no combobox)
** [RR] TensorFlow to use wrapping as well
*** Very simple (only types 'tensor' & 'variable')

=== November 11, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapping numpy's classes using numpydoc (ndarray)
*** Wrapping constructor arguments, attribute getters/setters as module ports
**** Then how to access attributes afterwards?
***** Use input value port to class modules?
*** Wrap methods as modules? E.g., `ndarray.shape`.
*** Function wrapping is almost a subset of class wrapping
**** May be able to use the same parsing/execution methods
** VTK's non-getter/setter methods could be wrapped as modules
*** We could then remove extra logic in interpreter for keeping function order
** Bokeh uses autogenerated docstrings
*** We may be able to read the specification directly

* [RR] [https://github.com/VisTrails/VisTrails/pull/1138 TensorFlow package]
** Basic setup working, can execute the Mandelbrot example
** Will autogenerate the operations

=== November 4, 2015 ===
'''Updates'''
* [RR] Interpreter work requires a fix for [https://github.com/VisTrails/VisTrails/issues/1137 DB issue #1137]
* [DK] Kitware's Resonant [http://www.kitware.com/source/home/post/173]
** [https://github.com/girder/girder Girder]: data management system
** [https://github.com/Kitware/romanesco Romanesco]: execution engine, uses [http://www.celeryproject.org/ Celery] for task management
** Resonant Flow: web app for editing and executing workflows

'''Items to Discuss'''
* [TE] Added OSX Lion (10.7) VM on build machine using vagrant (seems ok with license?)
** New builds works on Lion
** Change the minimum requirement to 10.7?
* [TE] Package wrapping
* Added upgrade suggestions using 2 spec versions ([http://pastebin.com/30XUU8Gp example])
** using name edit distance to find matches
** Could use something better like port similarity for modules, and type similarity for ports
** Should write python upgrade code?
** Added spec to sklearn package
*** Can now diff spec versions and keep the spec static
*** There will be problems with downgrades and package versions

=== October 29, 2015 ===
'''Updates'''
* [TE] nightly-build-mac fixed (Needed to approve xcode license)

'''Items to Discuss'''
* [TE] matplotlib wrapper
** ported to general spec
** Diff can be used on general spec
*** Only needed minor changes
*** Fixed indexing bug that corrupted specs
*** Can now move diff tools to core/wrapper
** Add new plots?
*** New plots in mpl 1.3: eventplot
*** New plots in mpl 1.4: angle_spectrum, magnitude_spectrum, phase_spectrum', violinplot
*** No new plots in mpl 1.5 (from looking at boilerplate.py)

=== October 21, 2015 ===
'''Updates'''
* [RR] Alexis has arrived, will be working with [RR] on a more efficient interpreter

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package]
** Supporting multiple package versions
*** Check which version can be loaded [https://github.com/VisTrails/VisTrails/pull/1135 #1135]
*** We cannot show version requirements in the list of packages because old packages are loaded when importing the codepath
** Visual diff does not work well, but we can use the spec differ to see differences.
** Unifying vtk and matplotlib wrapping specs (WIP)
*** And porting matplotlibs spec differ to work on the general spec
*** Spec differ can then be used on vtk and other packages in the future
*** Will enable automatic upgrade generation
* [RR] Rework interpreter
** restore abstraction between interpreter/module code
** build looping, streaming, caching into the interpreter
** rework cache
** look into parallelism once basic functionality is there

=== October 14, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package] (adding numpydoc parser)

=== October 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/tree/fix-matplotlib-parser New matplotlib parser] (adding numpydoc parser)
** Added numpydoc attribute parser for plots.
*** TODO: Need better port spec reconciliation with call signature parser.
*** We can create a general numpydoc parser, but attribute types are unique to matplotlib.
** Needs package versioning
*** New spec will not support matplotlib < v1.4 due to changed path to axes classes.
*** Load spec version corresponding to installed matplotlib version?
*** Need version downgrades?

=== September 30, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Updating Matplotlib parser
** Matplotlib docstring parser fails on numpy docstrings
** I have [https://github.com/VisTrails/VisTrails/commit/eae8b0c16260810587e47c41cab53552cbb3cf0a added basic numpydoc parsing]
*** Only used by a few docstrings so far
*** Parsing uses many sources (class tables, signatures, ACCEPTS, method docstrings, definition parsing).
** Caswell said they were thinking about moving to traitlets, but this is not ready yet

=== September 23, 2015 ===
'''Updates'''
* [TE] VisTrails 2.2.3 released
** Also have pushed to PyPI, binstar, etc.
** Sourceforge vs. GitHub
*** should be able to host releases on GitHub
*** nightly binaries pushed to sf each night
*** old binaries?
* [TE] Re-wrapping MatPlotlib
** Keep static generation - Docstrings are brittle beween matplotlib versions
** Keep generating the executable classes - but create functions, not vistrails Modules
*** Why is there so much patching?
** Re-implemented Alternate PortSpec for InputPortSpec
*** It will now inherit specs from parent (No need to reimplement)
** Module upgrades?

'''Items to Discuss'''

=== September 16, 2015 ===
'''Updates'''
* [TE] Job Monitor tests and documentation done
** OK to leave document package in packages directory?

'''Items to Discuss'''
* [TE] Library wrapping: How to do code patching? [https://docs.google.com/drawings/d/1Sh3eOXot6v2y880jHKQrqXqAwr-0aoqYligg3z8G8MY/edit?usp=sharing Wrapping diagram]
** Insert code into module template (Old VTK code)
** Patch the library that is called (New VTK code)
** Somehow store code in spec and apply when executed?
*** Executed code needs at a minimum access to inputs, outputs, current class
*** Use standard input/output dict and obj reference that the code operates on?
*** Can this be done while keeping the execution abstract?

* Do new release now?

=== September 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* New release?
** [RR] wants reprounzip
** tej changes & doc
** job monitor & jobmixin fixes
** mongodb
** reprounzip
** warning: MplFigure type is int
** tabledata: add Reshape, DictoToTable & ListToTable, fix ListToTable with numpy arrays
** PythonSource can have same name for an input & output
** don't show spreadsheet at exit

=== September 2, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Limit autosaves? [https://github.com/VisTrails/VisTrails/pull/1126 #1126]

=== August 26, 2015 ===
'''Updates'''
* [TE] Added Job support to Parameter Explorations (Requested by Colin), and Mashups
** specify job ids, need to specify different ids for parameter explorations since they have the same version id
** how to deal with parameters passed in on command line
* [General] provenance: should be creating a new version when we execute workflow with changed parameters?
** currently, custom_params annotation stores this in provenance currently
** [RR] API doesn't record provenance if passing in parameters: http://git.io/vsAA5
'''Items to Discuss'''

=== August 19, 2015 ===
'''Updates'''
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [TE] Working on Job Monitor documentation

'''Items to Discuss'''
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [TE] Stop testing VisTrails 2.0?

=== August 12, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Build broken on Travis; because of IPython 4 released today? ([https://travis-ci.org/VisTrails/VisTrails/builds/75279795 build 992]; [https://github.com/VisTrails/VisTrails/issues/1123 #1123])

=== August 5, 2015 ===
'''Updates'''
* [TE] Fixes to Jobs
** Could not delete jobs
** Could not run job in group
** Job not reset when calling ModuleSuspended
** Added deleting job from context menu
* [RR] Writing documentation for everything [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

'''Items to Discuss'''

=== July 29, 2015 ===
'''Updates'''
* RR still looking into new interpreter thing
** Goal is to take out scheduling logic from Module so it can be split in multiple processes, and so that smarter strategies can be added in time
** This means some work on packages
** Spreadsheet can live in kernel process? Still some UI stuff that will take work (changing configuration, persistent archive's viewer, ...)
* [TE] Problems running examples [https://github.com/VisTrails/VisTrails/pull/1111 #1111]
** Testing of more examples requires additional packages on the test machines.
** Fixed faulty line-ending in PythonSource:s failing on Python 2.6.
** Test suite now testing SUDSWebServices (If web service is down, test suite will fail)
** preferences.py test failed reloading 'dialogs' package, switched to using 'URL'.

'''Items to Discuss'''

=== July 22, 2015 ===
'''Updates'''
* [TE] mailing lists back online
* [TE] Working on [https://github.com/VisTrails/VisTrails/issues/1107 #1107]
* [RR] Working on ReproZip package

'''Items to Discuss'''
* [RR] MongoDB package [https://github.com/VisTrails/VisTrails/pull/1106 #1106]
* [RR] Example for tej docs? [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

=== July 15, 2015 ===
'''Updates'''
* 2.2.2 released

'''Items to Discuss'''
* RR is considering executing everything in an IPython kernel (i.e. separate Python interpreter, like the one spawned for a notebook)
** It's a separate process that we can restart without restarting the app/gui
** We can isolate the execution environment (e.g. for the server)
** We can run the whole thing remotely (if your data is elsewhere, just run VisTrails locally and the pipeline elsewhere)
** Pipeline execution no longer makes the interface hang, it just makes the kernel hang (but that's fine)
** We can use notebooks as modules (probably way nicer than the PythonSource module)
** We can run multiple kernels so long as the ports carry things that are serializable
*** meaning we can put the multithreaded-interpreter without all the hacky parts it has now
*** we can run IPython kernels in all the languages IPython supports, [https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages currently 46]

=== July 8, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Buildbot github hook not working after IP address change
* [TE] No reference to VistrailsApplication ([https://github.com/VisTrails/VisTrails/issues/1103 #1103])
** [RR] Added PR [https://github.com/VisTrails/VisTrails/pull/1104 #1104]
* [TE] Reopening VT file after saving with bundled subworkflow won't offer subworkflow upgrade ([https://github.com/VisTrails/VisTrails/issues/1102 #1102])
** allow manual delete to fix right now
** fix this on top of the use-uuid branch
* [TE] Release VisTrails 2.2.1? ([https://github.com/VisTrails/VisTrails/blob/v2.2/CHANGELOG CHANGELOG])
** [https://github.com/VisTrails/VisTrails/pull/1093 output-modules-use-global-dir]
** [https://github.com/VisTrails/VisTrails/milestones/version%202.2 Current issues for 2.2]

=== July 1, 2015 ===
'''Updates'''
* [TE] PROV fixed
* [TE] Working on subworkflow issues
* [RR] Considering reworking the controller (log vs exception problem, retained upgrades causing interferences) and also the interpreter (IPython?)

'''Items to Discuss'''

=== June 24, 2015 ===
'''Updates'''

'''Items to Discuss'''
* UV-CDAT
* [TE] Can a cyclic workflow be valid? ([https://github.com/VisTrails/VisTrails/issues/1097 #1097])
** focus on disabling the ability to create cyclic pipelines because more things break than just this with a cyclic pipeline
* [RR] Relative paths ([https://github.com/VisTrails/VisTrails/pull/1057 #1057])
** This interacts with the new bundle; how do handle packing files inside the VT bundle?

=== June 17, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] current_version and reusing existing upgrades are broken ([https://github.com/VisTrails/VisTrails/issues/1095 ticket #1095])
** Could be that export to PROV is using an unflushed upgrade pipeline?
** current_version would then be correct.
** It may work to flush the actions before exporting?

=== June 10, 2015 ===
'''Updates'''
* DAT: fixed VTK issue on Linux and Mac
* Still crashes on Windows. Need help! Reminder: this works in the VisTrails spreadsheet (QCellPresenter), although no widget get changed there during a drag
** Is it a VTK bug?
** Is it simply impossible to change widgets during the drag, should we do it a different way?
** Did I miss something that is done in VisTrails but somehow not in DAT?
** Low prio, UV-CDAT doesn't run on Windows anyway

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 Updated pull request])
* Single instance code and batch mode

=== June 3, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 pr])
** Requires fixes to command line parameters, Output modules, and batch mode
** How to test this
** Updated missing/outdated flags
** Fixed view issues when generating graphs
* [TE] batch mode
** SpreadsheetOutput not enabled in batch mode. Should we check is_running_gui instead?
** Other instance setting flags from caller
** Is graphsAsPdf replacing spreadsheetDumpPdf?
** graphsAsPdf true by Default?
** Batch mode executing by default (Not needed when generating graphs)
** Re-added workflowInfo as withWorkflowInfo for writing graph and xml workflow
** [DK] batch mode should be outputting to files or stdout, shouldn't always trigger SpreadsheetMode
** execute flag, maybe make execution the default and allow a "--no-execute" if you only want to capture graphs, for example

=== May 27, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] API question
** http://lists.vistrails.org/pipermail/vistrails-users/2015-May/000357.html
* Status of DAT
** Can add VCS plot to DAT but need to work on configuration windows
** Documentation for graphics templates for UV-CDAT/vcs?
* Qt support?

=== May 20, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Reviving the DAT, integrating scripting & porting UV-CDAT!
** On [https://github.com/VisTrails/DAT GitHub] ([https://github.com/VisTrails/DAT/issues issues])
** Merging 2 years of development taking longer than expected, but getting there. The plan is to get the patches in VisTrails and never fork again, we never want to get in UV-CDAT's situation (and don't need to).
** VTK cell works fine on Linux but there was flickering on Mac & Windows before; still issues on Mac (Windows status unknown)
** Can get a VCS plot soon (but will need VTK cell fix)
** Integrate in UV-CDAT's build system (so we have cdms, VCS, ...) -> RR can do this, low priority
** How do we integrate scripting?
*** We want to be able to seamlessly make changes to a plot by changing Python code
*** Define new plots by entering Python code without writing modules/packages?
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 13, 2015 ===
'''Updates'''
* [RR] Test skipping whitelist ([https://github.com/VisTrails/VisTrails/pull/1069 #1069]) -- low priority
* [RR] Custom matplotlib modules can't be compatible with both 2.1 and 2.2 ([https://github.com/VisTrails/VisTrails/issues/1067 #1067]); should be fixed for ALPS ([https://github.com/VisTrails/VisTrails/issues/1070 #1070])

'''Items to Discuss'''
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 7, 2015 ===
'''Updates'''
* [RR] Export/import workflow to Python working!

'''Items to Discuss'''
* [Claudio] UV-CDAT
** The UV-CDAT project is the biggest user base of VisTrails
** VisTrails package management provides a lot of friction towards people plugging in their code
** Need to make it easy to integrate your random Python scripts in the system without having to deal with all the boilerplate, at least in the first step
** [RR] argues that modules are still good; UV-CDAT shouldn't move towards a purely script-based backend
** [RR] export/import with Python could reduce a lot of that friction by allowing 1) to edit workflow as Python 2) to open up boxes automatically if needed code doesn't match actual modules
** ...

=== April 29, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] <strike>Abstractions</strike> subworkflows status ([https://github.com/VisTrails/VisTrails/labels/subworkflows tickets])
* [RR] matplotlib compatibility (2.1 & 2.2), [https://github.com/VisTrails/VisTrails/issues/1067 #1067]
** RR to try and fix ALPS matplotlib modules

=== April 22, 2015 ===
'''Updates'''
* 2.2.0 has been released!
* Windows issue (via email from Ryan)
** issue with manifest file (may be a new file in VTK6?)
** Tommy has regenerated new Windows builds
* Binaries, pypi, and conda released
* [RR] Export as script
* Python sources using VTK need to switch to SetInputData (users should be aware of this)

=== April 15, 2015 ===
'''Updates'''
* Ready for 2.2.0 (apart from binary/deps issues)
** Missing some libs (scikit-learn, tej, tdparser, SQLAlchemy+connectors
** Windows: runvistrails.py is no longer used, so the PATH is wrong
** Windows: pip is broken, but it probably wouldn't work anyway because of permission issues (disable this?)
* Queries, upgrades and getPipeline() usage ([https://github.com/VisTrails/VisTrails/issues/1054 #1054])
** Getting a pipeline with getPipeline() is not safe: it might return an invalid pipeline
** This is used in many places throughout the code, like queries
** Upgrading would require going through the controller, but that creates new actions
* [TC] Avoid copying a module's output if it's used as input by exactly one downstream module ([https://github.com/VisTrails/VisTrails/issues/1060 #1060]) (useful for big numpy arrays you can update in-place)

=== April 8, 2015 ===
'''Updates'''
* [DK] Merged RR's changes for output modules (1012 and 1013)
** RR will merge remaining changes, then create v2.2 branch!

'''Items to Discuss'''
* BNL need numpy array to VTK image
** Looks like VTK has some helpers for this
** We will help if issues arise
** Will contribute back to VisTrails package
* Upgrade issue: [https://github.com/VisTrails/VisTrails/issues/1017 #1017]
** Automatic upgrades should happen between versions of provided upgrades
** Our existing upgrades work around this so it doesn't need to be 2.2.0
* Corner-case VTK modules
** No longer need VTKCell input port, so don't interfere with registry and API anymore
** Still work weirdly, people probably shouldn't use them
** But we have lots of clunky modules since we wrap the whole of VTK; some people might rely on this and know how to use them, let's keep them anyway
** Ready for 2.2.0

=== April 1, 2015 ===
'''Updates'''
* [RR] UV-CDAT: bugfixing for 2.2, long-term plans: implement scripting import/export in VisTrails, port to UV-CDAT
* Possibly, try to move to regular VisTrails to use new features

'''Items to Discuss'''
* 2.2 release: nothing much is pending anymore, release next week?
** [TE] vtkExporter classes [https://github.com/VisTrails/VisTrails/issues/1032 #1032]
** [RR] Hiding upgrades in version tree might make it (or might be 2.2.1 so we can test it out) [https://github.com/VisTrails/VisTrails/issues/949 #949]
** Output modules changes to go in
* add note to documentation about order of parameters in VTK
* add issue about exporter upgrades if not already there

=== March 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* 2.2 release
** Checklist on Github: https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist
** Review output modules
** RR has a couple more issues to fix
** Ready to go -- sign app package for OSX? [https://github.com/VisTrails/VisTrails/issues/984 #984] We need access to the Apple Membership team

=== March 18, 2015 ===
'''Updates'''
* [TE] VTK6 works

'''Items to Discuss'''
* [RR] Release v2.1.5 with backported tabledata?
** MTA example needs updated tabledata (for JoinTables)
** Google Maps package still not available
* [RR] Work torward v2.2.0?
** changes:
*** new persistence
*** API changes
*** output module changes (upgrades?), maintain cells but try to upgrade
*** not wrapping stuff
*** VTK6? yes
*** JobSubmission stuff?
*** relabeling for upgrades [https://github.com/VisTrails/VisTrails/issues/949 #949]
** makes sense, needs the tree view code to be updated, check selection
** See [https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist 2.2 checklist]
* Discussion of [https://github.com/VisTrails/VisTrails/issues/1016 #1016]
** plumbing between outputs and output modes, how to define a mode that works for many outputs without writing for each output?

=== March 11, 2015 ===
'''Updates'''
* [RR] persistent_archive done; merge? ([https://github.com/VisTrails/VisTrails/pull/755 #755])
** note about the focus events for widgets
** TE be aware of file_archive for future binaries that include persistent_archive
* [TE] [https://github.com/VisTrails/VisTrails/pull/998 New VTK package] finished

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails? (see last week; decision needed)
** RR email to JF about this
** yes; email sent to Github
* [RR] Switching order of output ports ([https://github.com/VisTrails/VisTrails/pull/1006 #1006])
** added port specs are sorted at a separate spot (Module.*_port_specs properties) than those in the registry (which are sorted in the registry), but those two lists are just combined without respect to sort keys
** need to determine whether the two lists should be merged or remain distinct
** should make sure that order of input ports and output ports makes parallel connections for things with same order
** DK suggests breaking backward compatibility here: workflows still run, can fix easily if a problem in an existing package.
* [RR] Question about output modes ([https://github.com/VisTrails/VisTrails/pull/1007 #1007]), how to integrate in API ([https://github.com/VisTrails/VisTrails/pull/24 #24])
** Should ImageFileMode be removed? ("image" is not a mode, "file" is)
** ImageOutput missing?
** Feel free to change how formats works
* [TE] Test suite segfaults on Fedora 17 virtualbox. Install newer version? (Support ended in 2013)

=== March 4, 2015 ===
'''Updates'''
* [TE] VTK wrapper
** Works on VTK 5.10
** Still need to test VTK 6
** New general wrappers for python functions and classes

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails?
** When [http://i.imgur.com/UTY2qfg.png filing a pull request] from UV-CDAT/VisTrails, VisTrails/VisTrails is selected by default
** People keep forgetting to change the default ([https://github.com/VisTrails/VisTrails/pull/956 #956] [https://github.com/VisTrails/VisTrails/pull/968 #968] [https://github.com/VisTrails/VisTrails/pull/999 #999] [https://github.com/VisTrails/VisTrails/pull/1000 #1000] [https://github.com/VisTrails/VisTrails/pull/1003 #1003] [https://github.com/VisTrails/VisTrails/pull/1004 #1004] [https://github.com/VisTrails/VisTrails/pull/1005 #1005])
** Only way to change that is to not have it marked as a fork of VisTrails/VisTrails
** Github staff [https://gist.github.com/remram44/b364c24ef1e462ce6e2f can make that change for us]; should we do it?
** Juliana: comments on this? visibility vs. convenience/annoyance for developers
* [RR] What about [https://github.com/VisTrails/VisTrails/issues/991 #991]?

=== February 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] vtkviewcell for infovis support, can we unify with VTKCell?
** need to test this
* [TE] vtk wrapping
** Mostly finished
** VTK 5.10 produce incorrect results with old wrapping
*** Old wrapper is based mostly on VTK 4
*** Most vtk_examples affected
*** [http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Replacement_of_SetInput]
*** should be able to upgrade from SetInput to SetInputData (need to drop GetOutput and replace with self ports)
*** can we change vtkInstance to just return self and not wrap things
** terminator example not working under 5.8?
* How does VTK wrapping fit into general wrapping framework?
* [RR] new persistence package

=== February 18, 2015 ===
'''Updates'''
* [RR] New VisTrails API and IPython integration ([https://github.com/VisTrails/VisTrails/pull/24 #24])

'''Items to Discuss'''
* [TE] VTK wrapping
** [https://gist.github.com/rexissimus/16b74693545b5e7c1035 Benchmarking vtk package]
*** Old: 24.7 seconds
*** New: 10.5 seconds (Except first time that adds 8 sec)
**** The parsing that calls is_abstract (that tries to instanciate all vtk classes) is now only run the first time.
**** get_items_from_sigstring takes 2 seconds, maybe we can use a lookup dict for already computed sigstrings?
** Now using a general python function wrapper
*** VTK classes are wrapped into python function that does not depend on vistrails
*** VTK functions can be executed without vistrails
*** The spec maps functions into vistrails modules, but can also describe wrapping
*** A general python function wrapper that supports
**** kwarg inputs
**** single, list, dict outputs
**** callback for progress reporting
**** temporary file generator for using FilePool
**** optional output generation
*** Creating specs:
***** Create spec by hand
***** Auto-create spec outline (TODO) and manually finish it
***** Dynamically create spec (VTK)
***** Implement documentation wrappers (Can use scikitlearn wrapper to wrap numpydoc) (TODO)
***** Classes as bad functions needs to be wrapped in new functions before they are wrapped. This is different for each package.
****** Classes is hard: Like VTK, and matplotlib. Scikit-learn does still not wrap classes
***** Spec diffing and patching could be done using code from matplotlib.
** Still needs upgrades from old VTK package
*** Is it possible to dynamically wrap functions, e.g, you see a SetFunc and just remove the 'Set' prefix. Or do you need to create a complete mapping?

=== February 11, 2015 ===
'''Updates'''
* Update from Friday's meeting
** discussed VisTrails internals
** discussed wrapping
*** xml discussion, hard to modify because tied to db code
*** TE has made it possible to add the schema-defined attributes to the intermediate representation
*** higher-level operations on the port specs
** make sure the simple case works
*** [JF] take a simple package with documentation and figure out what the base case for wrapping is

'''Items to Discuss'''
* [TE] VTK wrapping
** Dynamic loading works
** Reading XML is fast enough, but [https://gist.github.com/rexissimus/8272d3c776ccfa115d82 unserializing data is slow]
** Working on patterns for patching
** Matplotlib has many advanced patterns like argument ordering, nested arguments, alternateSpecs, output types.
*** Having all this in a general wrapper might confuse users?
** [RR] Delay module (except for identifiers) until you need it---e.g. don't deal with port specs, etc. until necessary
* Scripting Support [https://github.com/VisTrails/VisTrails/pull/950 #950]
** [RR] Issue with getting code from modules
** Design a simple solution
** [JF] Couldn't you use modules as black boxes without conversion, just to call into modules/subworkflows easily from e.g. IPython?
*** [RR] This is a job for the API, and a very separate use case. See [https://github.com/VisTrails/VisTrails/pull/24 #24]

=== February 4, 2015 ===
'''Updates'''

'''Items to Discuss'''
* Wrapping
** Format to use? Currently XML (like current matplotlib)
*** JSON and YAML have simple "to python dictionary" methods
*** But don't stream
*** YAML a lot easier for humans
** [DK] vtk-new-package also changes parameter names, creates enumerations
*** intermediate schema needs to be extensible
*** packages will want to store there specific infos for compute() method generation
*** also might have specs-altering info, like matplotlib's alternateSpec
** representation to code , registry already has schema for some aspects
** [RR] We might want to see if Module subclasses can be created lazily
*** no need to create all the classes just to register them in the registry and never actually use most of them
*** future effort
* [RR] Where should VisTrails packages live?
** tej installs as 'vistrailspkg.tej', TE installed it as 'userpackages.tej'
** Currently, standard packages are 'vistrails.packages.', user packages are 'userpackages.' and packages loaded through pkg_resources might be anything
** [RR] Use 'vistrailspkg.' everywhere?
** Long-term effort to simplify package distribution/installation (and have VisTrails get them automatically?)

=== January 28, 2015 ===
'''Updates'''
* T. Caswell to come visit on Fri 6 to discuss wrapping work

'''Items to Discuss'''
* [TE] New VTK wrapping
** Current code by DK seems a good deal faster
** Generates XML that can be patched/tweaked, generates Python code from it, VisTrails only loads generated Python code
** RR would rather have VisTrails load intermediate representation (= XML) directly, wants to make sure this is not slower
** The goal is to turn the intermediate step into something generic that would be used for every wrapped package (vtk, numpy, matplotlib, sklearn, java) instead of each having its own
** TC has its own code at [https://github.com/Nikea/VTTools/blob/master/vttools/wrap_lib.py github:VTTools] which parses numpy docstrings and generates modules, doesn't yet handle classes or persist anything
* Web crawler
** Right now, TE starts jobs for "start crawler", "stop crawler", "install classifier"
** RR would rather have the crawling be a job as far as VisTrails and tej are concerned
** The whole thing would be one pipeline: load examples, train classifier, start crawler [check for job, kill previous one, upload model, start processes], get snapshot, visualize
*** Need some support in tej and job submission system: long-running jobs, stop a job (wait for it to finish?), restart a job even though results are cached

=== January 21, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Unified wrapping method discussion [https://github.com/VisTrails/VisTrails/issues/991 #991]
** TE to work on reusable method with intermediate representation, starting with VTK
* [RR] Examples for scikit-learn: JF has an old example using Weka with parameter exploration (not currently in source tree)
** AM's examples are enough
* [AM] scikit-learn package is done, merge it in? [https://github.com/VisTrails/VisTrails/pull/955#issuecomment-70286788 #955]
** RR will merge
* [RR] What should copyright headers say? [https://github.com/VisTrails/VisTrails/pull/994#issuecomment-70173935 #994]
** Let's keep everything in there: Utah/Poly/NYU

=== January 14, 2015 ===
'''Updates'''
* [TE] Working on classifier
* [RR] Scripting integration, work in progress

'''Items to Discuss'''
* [RR] Unified wrapping method discussion ([https://github.com/VisTrails/VisTrails/issues/991 #991])
** Let's talk next week, [AM] and [DK] are not here

=== January 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* make sure that we address critical issues, questions, and pending review branches in a timely manner
* scripting support
** [RR] no issues if we want to just keep annotations in the generated code to allow the link back to a workflow
** [RR] can translate from workflow to script, working on script to workflow
** will work for parameter value changes, structural changes require changes to the annotations
** need to publish best practices here
** would be cool to do looping in scripts (easier interface than with workflows)
* notebook support (convert form notebook to workflow)
** RR will sync with FC on this
* Issue with console in built-from-scratch
** [TC] iPython rearranged some of the completion stuff in 2.2 and 2.3
** binary has old version of iPython -> 1.0.0, should we update?
* [TC] automated wrapping of numpy and scipy
** discovered a bunch of malformed documentation in numpy and scipy
** has github repo for vistrails tools
** example modules wrap a bunch of R stuff (not baked in, just how things are)
** will be pushing wrapping logic up
** port names forbidden (window and domain)
** have an import hook to get from yaml directly to VisTrails Modules
** should work for any python modules with well-formed numpy docstrings.
* [Action] should make it clear in documentation that Constant now means serializable not that the value doesn't change (e.g. List)
* [TC] might be interesting to try to build components of matplotlib and accumulate in figure (long-term project, but thinking about how this might work)
* [TE] build and build scripts
** completely automatic, buildbot
** need to set the build machines for the environment we want for the binary
** would virtualenv work here?
** [TC] anaconda can pin versions, potential path to test different configurations
** Q: upload nightly binary builds? A: makes sense, make sure they are well-labeled
* sourceforge stats: e.g. http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07
* package issues (see Remi's message)
* [TE] Scope of tej
** Support single ssh commands?
** Queue can be used as a remote machine (crawler is using queue.call*)
* SourceForge stats: http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07

== Older meetings ==
* [[Development/2014]]
* [[Development/2013]]
* [[Development/2012]]
* [[Development/2011]]
* [[Development/2010]]

Development

2016-06-29T14:43:26Z

Tommy: /* 2016 */

<div class="nonumtoc toclimit-1">
__TOC__
</div>

See also the [https://github.com/VisTrails/VisTrails/wiki/Development Github wiki]

== 2016 ==

=== June 29, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Export VTK as python script
** Works on Terminator (Isosurface, Volume Rendering, clipping plane, combined rendering) [https://gist.github.com/rexissimus/16caf5200802e150296f62a0c7844c5a example]
** Preludes (imports) still need improvements
** Works with vtkInteractionHandler (clipping plane)
** Resulting clipping plane is incorrect? (supposed to hide one side of the plane)
** vtkRendererOutput Uses VTKRenderWindow as output
*** Should support different output modes?
*** Does not work with multiple outputs (Next cell is displayed when current is closed)
*** Uses wrapped vtkInstance (as vvtk)
**** Create new patch system with code that can be used both in vistrails and in a python script?

=== June 22, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Fix for upgraded analogies (PR [https://github.com/VisTrails/VisTrails/pull/1177 #1177])
** Uses module location to find module remap (The best we can do right now?)
** Also fixes remapped port names for connections to existing modules
** May still fail on complex upgrades like adding a function on an upgraded module that has a different port name

* [TE] Working on exporting wrapped libraries (VTK)

=== June 15, 2016 ===

'''Updates'''
* [TE] Added depth logic to python script exporter ([https://github.com/VisTrails/VisTrails/commit/50f220e4f6abe5a7bb8689f73f456f43df2dbc12 full commit])
** Fully implements connection merging and list looping

'''Items to Discuss'''

* [TE] Making analogy work on upgraded workflows ([https://github.com/VisTrails/VisTrails/issues/1175 #1175])
** Analogy only works We need to use the non-upgraded action chain
** But pipelines need to be valid (matcher uses module portspecs)
** Tried to get upgrade remap from upgrade action, but this seems impossible
** Use module location instead?
*** Location should be identical for one-to-one module upgrades

=== June 1, 2016 ===

'''Updates'''
* VisTrails 2.2.4 announced (finally)
** 5 survey replies
** 47 downloads last week

'''Items to Discuss'''
* [TE] Export VTK as script (python-wrapper)
** to_python_script
*** needs the pipeline (or at least the connections)
**** Should not generate code for any possible VTK method (exporter detects which ports is used in the source)
**** VTK needs to know connection order
**** Adding functions directly to the script results in nicer code
** Add support for multiple input connections
** Add support for list looping

=== May 25, 2016 ===

'''Updates'''
* Mailing-list fixed
* Getting stats from the "server news" mechanism (via [https://github.com/remram44/apache-log-info parser])

'''Items to Discuss'''
* [RR] Alexis doing writeup on VisTrails, curious about interesting streaming use-cases (and potential future users)
* [TE] Union ports
** Show union ports in pipeline (DEMO)

=== May 18, 2016 ===

'''Items to Discuss'''
* [TE] mailing list still down - Julio working on it
* [TE] Improved union port
** New schema 1.0.5 adds portitem.union string attribute
** Works with pipeline view, parameter exploration view, and mashup view
** Should work well for matplotlib
** Use with VTK ports?
*** It uses [item_1,item_2] style ports usually with different tuple length.
* [TE] Remove emacs dependency from db generate [https://github.com/VisTrails/VisTrails/issues/1173 #1173]

=== May 11, 2016 ===

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]
** GUI-based solution [https://github.com/VisTrails/VisTrails/tree/union-port Branch union-port] Demo?
*** Shows single port for all ports with same sort_key
*** Select specific type when adding/showing
*** Only one type should be visible on the module at any time
*** Making tuple parameters union types is probably too complicated
*** Should work with alternate specs like matplotlib (if sort_key is defined correctly)

* [TE] Feature suggestion: Let connections connect to functions/parameters
** Show functions and parameters as ports and toggle port visibility directly for functions and parameters
** Use separate views for ports and functions (like before)
*** Allow rearranging of functions
** Pros:
*** Supports ordered connections. Create 2 functions, make them visible as ports, make connections to them.
**** We can also have, e.g., a line joining the ports on the module to indicate they are part of a list.
**** Makes List module simpler
*** Connect to parameter in tuple
*** Functions that are visible on the module can connect to an actual function, and not just to the first one it finds.
*** Can replace operation modules (in python-wrapper) in some cases for, e.g., numpy.
** Cons:
*** Interface more complicated and crowded
*** More difficult for users to grasp?
*** No immediate use case
*** Makes no union type for tuple parameters a bigger problem.

* [TE] Publish user survey?
** No response from vistrails release yet
** Not announced on vistrails-users yet.

=== May 4, 2016 ===
'''Updates'''
* VisTrails 2.2.4 released

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]

=== April 27, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Wrapping Bokeh
** New method type "operation"
*** Transforms Figure->Glyph->Output into Glyph->Figure->Output
**** Glyph sets function name and arguments as output
***** Not serializable, but should always be computed together with the subject of the operation.
**** Figure applies Glyph operation on itself
*** Useful for matplotlib?
**** matplotlib currently find actors by searching upstream?
**** But this is more difficult since matplotlib is not function-based.
** New "union" port type
*** Turns "x(float), x(list)" into "x (float, list)" and uses first set value
**** Uses only first value in tuple
**** Bokeh have many properties that support (list, string, Float)
*** Does not work with depth=1 types (e.g. Float of depth 1)
**** Turn Depth 1 types with known type into lists?

* [TE] New bugfix release
** Finalize survey

=== April 20, 2016 ===
'''Updates'''
* Merged upgrade fixes
** Now has infinite loop test
** loop test now correctly loops 5 times
*** remap_module used wrong (current) package version when creating ModuleDescriptor
* Fixed multi-step group upgrades (PR: [https://github.com/VisTrails/VisTrails/issues/1168 #1168])

'''Items to Discuss'''
* New bugfix release
** Merge usagestats
** Need to finalize survey

=== April 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Chaining upgrades done ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Replace "Upgrade" description annotation with "upgraded_from" annotation to identify which tags to hide?

* [TE] Iterating handle_invalid_pipeline ([https://github.com/VisTrails/VisTrails/pull/1165 #1165])
** Not based on [https://github.com/VisTrails/VisTrails/tree/chain-upgrades-loop chain-upgrades-loop]
** Cherry-pick test to preserve source?
** Need maxPipelineFixAttempts option?
*** The code is now smarter about recursion, so max attempts will "probably" never be reached.
** Need [https://github.com/VisTrails/VisTrails/commit/0ef0667426937eddb1d1c1e397f0657ffec039a9 debug messages]?
*** Would need to be moved into handle_invalid_pipeline

=== April 6, 2016 ===
'''Updates'''
* [TE] Query View improvements
** Done except for displaying "Version Info" and #1164
* [RR] Working on finishing new interpreter (finally!)

'''Items to Discuss'''
* [TE] Chaining upgrades ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Try latest upgrade first, then previous.
** If all fail, select latest upgrade?

=== March 30, 2016 ===
'''Updates'''

'''Items to Discuss'''

* [TE] Query View improvements
** Unified do_version_switch and get_upgrades as validate_version()
** Problems with query view using its own controller
*** Fixed module info not being displayed for query results
*** Still no version info for query results
*** Still an issue with version query view not being updated

=== March 23, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Usage reporting almost ready to go
** Need to record whether specific features are used: paramexpore, mashup, query
*** [DK] Record if LaTeX extension is used? But hard to distinguish from direct batch invocation
** How to record size of vistrail?
*** [DK] IdScope already walks over vistrail, use that
*** but total number of modules and versions doesn't give an idea of average size of individual pipelines

=== March 16, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Upgrades in Query Mode
** Now using code similar to do_version_switch
*** Uses handle_invalid_pipeline
*** Differences: Not using current_pipeline, flushes changes
*** New controller method get_pipeline optimized using cached pipelines (but not current_pipeline)
*** Integrate to avoid repeated code?
*** Use this for query mode?
* [TE] VisTrails 2.2.4 ready for release?
** tej package updated. Others?
* [JF] upgrades and the version tree
* [JF] provenance in Jupyter
* [DK] bundles: [https://github.com/VisTrails/VisTrails/pull/1092 #1092]

=== March 9, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixing search mode
** String query now matches all by default
*** This caused pipeline queries to never match
** String query can search: User/Notes/Tagname/Time/Module name
*** Should we search module names by default? (Disabled by default because it is expensive)
*** Fixed notes search
** '>' parameter queries in documentation but has been removed
** Fixed module matches for upgraded pipelines (By not upgrading pipeline)
*** Upgrades still a problem
*** Add "Upgrade all menu option?" (Or upgrade all on open when `hideUpgrades`)
*** [JF] Allow search on past tags

* [TE] Create new bugfix release
** Finish querying
** Path issue on windows

* [DK] Look into sqlalchemy and new bundle branches

=== March 2, 2016 ===
'''Updates'''
* [TE] Fixed cache bug with port specs
* [TE] VisTrails Next
** Most packages now work
** No qgis for Python 3

'''Items to Discuss'''
** Always dereference symlinks? [https://github.com/VisTrails/VisTrails/issues/1146 #1146]

=== February 23, 2016 ===
'''Updates'''
* [TE] Fixed PythonSource 100% CPU bug
* [TE] VisTrails Next
** Updated [http://opendap.co-ops.nos.noaa.gov/axis/webservices/wind/ NOAA Web Service] examples
*** Now uses REST service, tabledata, and Google Maps
*** Web Service replaced with DownloadFile

'''Items to Discuss'''
* [RR] Couple of fixes are in for API, and tej&reprounzip on the Mac binary. Also new release of tej, and working on anonymous usage reports.
** New 2.2 release soon?
* [RR] Anonymous usage reports
** Sends out info like number of modules & versions, packages used, Python & libs versions, execution time, specific features [https://github.com/VisTrails/VisTrails/pull/1154 #1154]
* [JF] Bring in noWorkflow to track variable dependencies, for the considered Jupyter integration?
* noWorkflow - provenance for python scripts
** Recent work on tracking dependencies
* Also integrates ReproZip with Jupyter
** [http://mybinder.org mybinder]
*** Use with ReproZip to automatically build Jupyter notebook interfaces
* Daves comments on Jupyter integration
** It is possible to identify cell order on the server side
** Not trivial to track order of cells on client side
* How does Galaxy workflows relate to VisTrails?
** Packaging in Galaxy is hard
** Galaxy for biomedical workflows, difficulty making it general
* Action items
** How difficult to track cell dependencies in Jupyter notebooks?
** Use noWorkflow to track cell dependencies?
** How difficult to modify mybinder to use ReproZip packages?

=== February 17, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixed Group memory usage
** Modules in groups are supposed to be freed when done executing
*** Prevented by logger that stored references to the modules (fixed, now using id(module))
*** Prevented by list iterator bug that stored list of modules on the 'self' port bug (fixed)
* [TE] VisTrails Next
** Removed deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** PythonSources will be upgraded
*** Fixes for Python < 3
*** fixes for VTK < 6
** TODOs
*** Remove RemoteQ
**** Port Hadoop to tej (Already have pbs)
*** Merge package wrapper
*** Finish SQLAlchemy branch
*** Finish new bundle branch
** [JF] Will contact Jeff and Matthias about moving to Python 3
* [JF] Query by Example is broken
* [JF] VisTrails Data Cleaning Project
** Use VisTrails to process and explore task-specific data while keeping provenance.
** Remi's Idea
*** Use VisTrails as the backend in a Jupyter notebook
*** Overcome problems with executing cells in random order
**** Interesting research topic, but little interest has yet been noted
*** Interesting to study how such a notebook would be used (Is there notebook usage data available?)
*** Impose restrictions to notebook cell boundaries
*** It will only work for functional operations
*** Can we fix, or detect, non-functional (mutating) operations?
*** Analyse code and data flow and see if it mutates data in unexpected ways?
*** Mutable operations can be created in many ways in Python
* Next meeting Tuesday 11:30

=== February 10, 2016 ===
'''Updates'''

'''Items to Discuss'''
* VisTrails Next
** Test suite passes
*** Python 3 less deterministic, module upgrade order random.
** [RR] updating packages: Reprounzip (pushed), tej, persistent_archive, ...
** All of our packages should run fine :)
** VTK thumbnail comparison works
*** Rendering bug on some systems
**** QVTKCell now inherits QGLWidget
*** Old thumbnails had wrong height due to spreadsheetwindow being too small
**** Fixed by regenerating thumbnails
*** Silenced deprecation messages when generating modules
*** Many new classes in VTK 7
** Remove deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** Will break existing PythonSources
**** Try to upgrade?
*** Old-style packages
**** Or only allow a new style, like __init__.py renamed to info.py? (merge with identifiers.py?)
***** Read info.py without importing package?
*** Fixes for Python < 3
*** Fixes for Qt < 5
*** fixes for VTK < 7
*** Remove self port?

=== February 3, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] [http://lists.vistrails.org/pipermail/vistrails-users/2016-January/000402.html Rendering a .pvd (ParaView) file?]

* VisTrails Next
** All tests but thumbnail comparison passes
** Still issues with gui and more packages needs to be tested
** PythonSource and MplSource upgraded with lib2to3
** Keep contrib packages? Update?
** [https://blog.kitware.com/vtk-7-0-0/ VTK 7 is released]
*** Supports Python 3
*** Will hopefully get into conda and others soon
*** Deprecates a bunch of modules

* [https://travis-ci.org/VisTrails/VisTrails/builds/106743348 Travis builder] for VisTrails Next
** Runs!
** Uses conda
*** Many levels of requirements
**** apt packages
**** conda packages
**** python packages in requirements.txt
**** python packages in setup.py
*** Can probably drop conda. Default builder does not have Qt5, but beta builder do!
*** But useful if we want to use conda in our own build process.
** Lots of errors I do not get locally?

* [http://goo.gl/forms/Z4HBrwaBWL User Survey]
** Have you used any alternatives to vistrails?
*** Relevant? More options?
** How often do you use any of these particular features in VisTrails?
*** Add/Remove alternatives?
** How important would you rank the following potential improvements to VisTrails?
*** Add alternatives?

=== January 27, 2016 ===
'''Updates'''
* New interpreter
** Working prototype soon
** Looping not completely done (and port combination mode: pairwise/cartesian...)
** Need to integrate with VisTrails
*** Compatibility with existing modules
*** Use log controller
*** Want to cache at multiple levels (whole stream/single element of stream)
*** Non-runtime attributes of modules (cache check, automatic conversion check, constant from/to string)

'''Items to Discuss'''
* User Survey

* ZMQ failing on windows (vistrails-users)

* [TE] [https://github.com/VisTrails/VisTrails/pull/1143 Python 3 branch]
** Testsuite almost passes
*** Failing are unicode filenames, some users guide examples, and thumbnail comparisons.
** Fixed issues
*** Signatures are now bytes (convert to string to show in widget)
*** Cannot compare different types, e.g., (None < 1)
**** PortSpec.depth and min/maxConn could be None. (Backport!)
**** cell.row could be None
*** Lots of unicode/bytes fixes to serializations
**** We have encryption implementations in the code! (keychain)
*** Lots of small fixes to package method differences
** Current issues
*** logging widget empty?
*** version tree signals messed up
*** provenance view legend icons black
*** Text do not fit in some widgets
*** VTK thumbnail comparison fails
**** VTK Cells have some faces in wrong direction?
**** Because running in VM?
** Installing on Ubuntu LTS/Latest Mint
*** Install latest matplotlib from pip
*** Install VTK 7.0.0rc2 from source
*** No QtWebEngine binary (controversial) (Must install sip/PyQt5/Qt5 from source)

=== January 20, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Backporting features from Python 3 + PyQt5 + Qt5
** Merged unicode with master ([https://github.com/VisTrails/VisTrails/tree/unicode unicode])
*** One unicode test failing
*** Problem saving to xml
** Used [http://python-future.org/ python-future] to run futurize stage 1 to update legacy (pre 2.6) code ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized unicode-futurized])
*** Updates print to functions 'from __future__ import print_function'
*** Updates exception calls to use 'as'
*** removes most usages of 'long' (mostly used unnecessarily)
**** Only needed for 32-bit support
*** Fixes relative imports (from __future__ import absolute_import)
** Fixing code that is deprecated in Qt 4.8 and removed in Qt 5 ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized-qt5 unicode-futurized-qt5])
*** Updated all signals to new-style
* If we go 2 to 3, this could break packages
** means we should schedule any package format changes for the same time
** e.g., imports should be unrelated to code path (function to load module from package identifier?) (take them out of vistrails.* [https://github.com/VisTrails/VisTrails/pull/1002 #1002])
** any structural changes (e.g. the __init__ versus init thing) (RR thinks it makes sense, though having both named "init" is unfortunate)
** putting package identifier as xml?
*** Python not so bad, plus some stuff in there is Python code (checking dependencies)
** version the APIs?
*** RR planning on versioning vistrails_module.Module, no point versioning the whole package?
* file formats on 2 to 3:
** no real translation/upgrade, but non-ascii values that work on 3 won't load in 2

=== January 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://gist.github.com/rexissimus/dfd27e466427529c385c Porting to Python 3 / PyQt5]
** Basic GUI and execution works
** Minimal work to support 2to3
** Hard to support both PyQt4 and PyQt5

=== January 6, 2016 ===
'''Updates'''
'''Items to Discuss'''
* Updating VisTrails dependencies
** Successfully built [https://gist.github.com/rexissimus/f1a1aada7de1c00a57c7 Win7-64/Python3/PyQt5/Qt5/WebEngine/VTK7]
*** VTK 7 is the first supporting Python 3 but is only in release candidate phase.
**** Next version of VTK 6 is rumored to support Python 3
**** There is a development branch of VTK 6 supporting Python 3
*** Can travis build this?
**** We can skip tests for WebEngine and VTK if needed
** Python 3 [https://python3wos.appspot.com/ showstoppers]
*** No MySQL-python (sqlalchemy supports mysql through other drivers)
*** No suds (there are active forks but we could also drop support?)
* Options for python2/3 support:
** Interpreter could be python2/python3 based on packages
** six layer works but not the easiest to maintain (e.g. in reprozip)
* Drop support for win-64
* Update copyright headers to 2016

== 2015 ==

=== December 30, 2015 ===
'''Updates'''
* Bokeh package finished
** Can output to Browser/IPython/Spreadsheet (Limited functionality in spreadsheet)
'''Items to Discuss'''
* Updating VisTrails dependencies
** Bokeh needs QWebEngine (Chromium) in Qt5 which requires PyQt5
*** Many plotting libraries only work in browsers
*** But Chromium may be a big and controversial dependency
*** Or create a browser version of the spreadsheet?
** Some users have requested Python 3
** Not backwards compatible?
** Target for VisTrails 3.0 with new interpreter?

=== December 16, 2015 ===
'''Updates'''
'''Items to Discuss'''
* Users list question
* [TE] Wrapping Bokeh
** Added bokeh property parser
*** complements numpydoc parser
*** Not all attributes are available, partially because I am using a pre-release version.
** Wrapped modules
*** bokeh.plotting finished (Backwards like matplotlib: Create plot then draw on it)
*** bokeh.charts mostly done (Missing arguments)
** QWebView mostly works (but no zooming or buttons)
*** It would be better to use external browser or QWebEngineView
** Added improvements to wrapper
*** Generalized port translations (Color/Path to native types)
*** Can use multiple docstring/property parsers simultaneously

=== December 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Looking into wrapper
** Will port TensorFlow
** Doing a pass on the wrapper code & doc
*** UX improvements
** Factorize high-level docstring parsers into core.wrapper? (sphinx, numpy, google)
** Problem with name vs module_name (fails sklearn tests because class_by_name() is broken)
** Looking into compressing specs, lazy registration of modules

=== December 2, 2015 ===
'''Updates'''
* [TE] Package wrapping
** Wrapped most of numpy/scipy using __all__
** Added class attribute and method access for classes (Can add to class or to separate inspector module)
** TODO: Document wrapping procedure

'''Items to Discuss'''

=== November 25, 2015 ===
'''Updates'''
* [RR] New interpreter is coming along
** Everything is a stream
** Task system, eventually work-stealing parallelism
** Streams no longer advance in lock-step
*** Allows for constructions like filter, join, sorted-merge
** depth>1 still to be tested, no current plan to allow this through the module interface
*** Through looping though, can do streams of streams

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapped most numpy functions (no polynomials)
** and half of scipy classes and functions
** Added functions manually from documentation (no parseable lists?)
** Focusing on data flow constructs (no property/method access for classes)
*** Using spec diff (empty for now) and dynamic parser (stores spec in .vistrails/)
** Python class/function wrapper now stable
** Add google doc parser?
*** Is there a parser available?

=== November 18, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Numpy class wrapping works
*** Basic type is List, since most types are array_likes.
*** TODO: More classes and functions
*** Some operations are in-place and some aren't, and docstring not super clear
*** [RR] It seems only methods mutate, and most have a numpy.xx function equivalent; just manually go through the methods and remove the mutating ones?
** Class wrapper is modular
*** Docstring parser and type string parser can be customized
*** Classes can have optional attribute/method ports
**** Inspectors and attribute/method modules can be created separately
** Use PythonCalc as an example
*** Can be re-implemented as a function with a parseable docstring
*** [RR] PythonCalc is just an example, and it might actually make sense to get rid of it, or do a proper math package with scalar operations (as separate modules, no combobox)
** [RR] TensorFlow to use wrapping as well
*** Very simple (only types 'tensor' & 'variable')

=== November 11, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapping numpy's classes using numpydoc (ndarray)
*** Wrapping constructor arguments, attribute getters/setters as module ports
**** Then how to access attributes afterwards?
***** Use input value port to class modules?
*** Wrap methods as modules? E.g., `ndarray.shape`.
*** Function wrapping is almost a subset of class wrapping
**** May be able to use the same parsing/execution methods
** VTK's non-getter/setter methods could be wrapped as modules
*** We could then remove extra logic in interpreter for keeping function order
** Bokeh uses autogenerated docstrings
*** We may be able to read the specification directly

* [RR] [https://github.com/VisTrails/VisTrails/pull/1138 TensorFlow package]
** Basic setup working, can execute the Mandelbrot example
** Will autogenerate the operations

=== November 4, 2015 ===
'''Updates'''
* [RR] Interpreter work requires a fix for [https://github.com/VisTrails/VisTrails/issues/1137 DB issue #1137]
* [DK] Kitware's Resonant [http://www.kitware.com/source/home/post/173]
** [https://github.com/girder/girder Girder]: data management system
** [https://github.com/Kitware/romanesco Romanesco]: execution engine, uses [http://www.celeryproject.org/ Celery] for task management
** Resonant Flow: web app for editing and executing workflows

'''Items to Discuss'''
* [TE] Added OSX Lion (10.7) VM on build machine using vagrant (seems ok with license?)
** New builds works on Lion
** Change the minimum requirement to 10.7?
* [TE] Package wrapping
* Added upgrade suggestions using 2 spec versions ([http://pastebin.com/30XUU8Gp example])
** using name edit distance to find matches
** Could use something better like port similarity for modules, and type similarity for ports
** Should write python upgrade code?
** Added spec to sklearn package
*** Can now diff spec versions and keep the spec static
*** There will be problems with downgrades and package versions

=== October 29, 2015 ===
'''Updates'''
* [TE] nightly-build-mac fixed (Needed to approve xcode license)

'''Items to Discuss'''
* [TE] matplotlib wrapper
** ported to general spec
** Diff can be used on general spec
*** Only needed minor changes
*** Fixed indexing bug that corrupted specs
*** Can now move diff tools to core/wrapper
** Add new plots?
*** New plots in mpl 1.3: eventplot
*** New plots in mpl 1.4: angle_spectrum, magnitude_spectrum, phase_spectrum', violinplot
*** No new plots in mpl 1.5 (from looking at boilerplate.py)

=== October 21, 2015 ===
'''Updates'''
* [RR] Alexis has arrived, will be working with [RR] on a more efficient interpreter

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package]
** Supporting multiple package versions
*** Check which version can be loaded [https://github.com/VisTrails/VisTrails/pull/1135 #1135]
*** We cannot show version requirements in the list of packages because old packages are loaded when importing the codepath
** Visual diff does not work well, but we can use the spec differ to see differences.
** Unifying vtk and matplotlib wrapping specs (WIP)
*** And porting matplotlibs spec differ to work on the general spec
*** Spec differ can then be used on vtk and other packages in the future
*** Will enable automatic upgrade generation
* [RR] Rework interpreter
** restore abstraction between interpreter/module code
** build looping, streaming, caching into the interpreter
** rework cache
** look into parallelism once basic functionality is there

=== October 14, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package] (adding numpydoc parser)

=== October 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/tree/fix-matplotlib-parser New matplotlib parser] (adding numpydoc parser)
** Added numpydoc attribute parser for plots.
*** TODO: Need better port spec reconciliation with call signature parser.
*** We can create a general numpydoc parser, but attribute types are unique to matplotlib.
** Needs package versioning
*** New spec will not support matplotlib < v1.4 due to changed path to axes classes.
*** Load spec version corresponding to installed matplotlib version?
*** Need version downgrades?

=== September 30, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Updating Matplotlib parser
** Matplotlib docstring parser fails on numpy docstrings
** I have [https://github.com/VisTrails/VisTrails/commit/eae8b0c16260810587e47c41cab53552cbb3cf0a added basic numpydoc parsing]
*** Only used by a few docstrings so far
*** Parsing uses many sources (class tables, signatures, ACCEPTS, method docstrings, definition parsing).
** Caswell said they were thinking about moving to traitlets, but this is not ready yet

=== September 23, 2015 ===
'''Updates'''
* [TE] VisTrails 2.2.3 released
** Also have pushed to PyPI, binstar, etc.
** Sourceforge vs. GitHub
*** should be able to host releases on GitHub
*** nightly binaries pushed to sf each night
*** old binaries?
* [TE] Re-wrapping MatPlotlib
** Keep static generation - Docstrings are brittle beween matplotlib versions
** Keep generating the executable classes - but create functions, not vistrails Modules
*** Why is there so much patching?
** Re-implemented Alternate PortSpec for InputPortSpec
*** It will now inherit specs from parent (No need to reimplement)
** Module upgrades?

'''Items to Discuss'''

=== September 16, 2015 ===
'''Updates'''
* [TE] Job Monitor tests and documentation done
** OK to leave document package in packages directory?

'''Items to Discuss'''
* [TE] Library wrapping: How to do code patching? [https://docs.google.com/drawings/d/1Sh3eOXot6v2y880jHKQrqXqAwr-0aoqYligg3z8G8MY/edit?usp=sharing Wrapping diagram]
** Insert code into module template (Old VTK code)
** Patch the library that is called (New VTK code)
** Somehow store code in spec and apply when executed?
*** Executed code needs at a minimum access to inputs, outputs, current class
*** Use standard input/output dict and obj reference that the code operates on?
*** Can this be done while keeping the execution abstract?

* Do new release now?

=== September 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* New release?
** [RR] wants reprounzip
** tej changes & doc
** job monitor & jobmixin fixes
** mongodb
** reprounzip
** warning: MplFigure type is int
** tabledata: add Reshape, DictoToTable & ListToTable, fix ListToTable with numpy arrays
** PythonSource can have same name for an input & output
** don't show spreadsheet at exit

=== September 2, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Limit autosaves? [https://github.com/VisTrails/VisTrails/pull/1126 #1126]

=== August 26, 2015 ===
'''Updates'''
* [TE] Added Job support to Parameter Explorations (Requested by Colin), and Mashups
** specify job ids, need to specify different ids for parameter explorations since they have the same version id
** how to deal with parameters passed in on command line
* [General] provenance: should be creating a new version when we execute workflow with changed parameters?
** currently, custom_params annotation stores this in provenance currently
** [RR] API doesn't record provenance if passing in parameters: http://git.io/vsAA5
'''Items to Discuss'''

=== August 19, 2015 ===
'''Updates'''
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [TE] Working on Job Monitor documentation

'''Items to Discuss'''
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [TE] Stop testing VisTrails 2.0?

=== August 12, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Build broken on Travis; because of IPython 4 released today? ([https://travis-ci.org/VisTrails/VisTrails/builds/75279795 build 992]; [https://github.com/VisTrails/VisTrails/issues/1123 #1123])

=== August 5, 2015 ===
'''Updates'''
* [TE] Fixes to Jobs
** Could not delete jobs
** Could not run job in group
** Job not reset when calling ModuleSuspended
** Added deleting job from context menu
* [RR] Writing documentation for everything [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

'''Items to Discuss'''

=== July 29, 2015 ===
'''Updates'''
* RR still looking into new interpreter thing
** Goal is to take out scheduling logic from Module so it can be split in multiple processes, and so that smarter strategies can be added in time
** This means some work on packages
** Spreadsheet can live in kernel process? Still some UI stuff that will take work (changing configuration, persistent archive's viewer, ...)
* [TE] Problems running examples [https://github.com/VisTrails/VisTrails/pull/1111 #1111]
** Testing of more examples requires additional packages on the test machines.
** Fixed faulty line-ending in PythonSource:s failing on Python 2.6.
** Test suite now testing SUDSWebServices (If web service is down, test suite will fail)
** preferences.py test failed reloading 'dialogs' package, switched to using 'URL'.

'''Items to Discuss'''

=== July 22, 2015 ===
'''Updates'''
* [TE] mailing lists back online
* [TE] Working on [https://github.com/VisTrails/VisTrails/issues/1107 #1107]
* [RR] Working on ReproZip package

'''Items to Discuss'''
* [RR] MongoDB package [https://github.com/VisTrails/VisTrails/pull/1106 #1106]
* [RR] Example for tej docs? [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

=== July 15, 2015 ===
'''Updates'''
* 2.2.2 released

'''Items to Discuss'''
* RR is considering executing everything in an IPython kernel (i.e. separate Python interpreter, like the one spawned for a notebook)
** It's a separate process that we can restart without restarting the app/gui
** We can isolate the execution environment (e.g. for the server)
** We can run the whole thing remotely (if your data is elsewhere, just run VisTrails locally and the pipeline elsewhere)
** Pipeline execution no longer makes the interface hang, it just makes the kernel hang (but that's fine)
** We can use notebooks as modules (probably way nicer than the PythonSource module)
** We can run multiple kernels so long as the ports carry things that are serializable
*** meaning we can put the multithreaded-interpreter without all the hacky parts it has now
*** we can run IPython kernels in all the languages IPython supports, [https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages currently 46]

=== July 8, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Buildbot github hook not working after IP address change
* [TE] No reference to VistrailsApplication ([https://github.com/VisTrails/VisTrails/issues/1103 #1103])
** [RR] Added PR [https://github.com/VisTrails/VisTrails/pull/1104 #1104]
* [TE] Reopening VT file after saving with bundled subworkflow won't offer subworkflow upgrade ([https://github.com/VisTrails/VisTrails/issues/1102 #1102])
** allow manual delete to fix right now
** fix this on top of the use-uuid branch
* [TE] Release VisTrails 2.2.1? ([https://github.com/VisTrails/VisTrails/blob/v2.2/CHANGELOG CHANGELOG])
** [https://github.com/VisTrails/VisTrails/pull/1093 output-modules-use-global-dir]
** [https://github.com/VisTrails/VisTrails/milestones/version%202.2 Current issues for 2.2]

=== July 1, 2015 ===
'''Updates'''
* [TE] PROV fixed
* [TE] Working on subworkflow issues
* [RR] Considering reworking the controller (log vs exception problem, retained upgrades causing interferences) and also the interpreter (IPython?)

'''Items to Discuss'''

=== June 24, 2015 ===
'''Updates'''

'''Items to Discuss'''
* UV-CDAT
* [TE] Can a cyclic workflow be valid? ([https://github.com/VisTrails/VisTrails/issues/1097 #1097])
** focus on disabling the ability to create cyclic pipelines because more things break than just this with a cyclic pipeline
* [RR] Relative paths ([https://github.com/VisTrails/VisTrails/pull/1057 #1057])
** This interacts with the new bundle; how do handle packing files inside the VT bundle?

=== June 17, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] current_version and reusing existing upgrades are broken ([https://github.com/VisTrails/VisTrails/issues/1095 ticket #1095])
** Could be that export to PROV is using an unflushed upgrade pipeline?
** current_version would then be correct.
** It may work to flush the actions before exporting?

=== June 10, 2015 ===
'''Updates'''
* DAT: fixed VTK issue on Linux and Mac
* Still crashes on Windows. Need help! Reminder: this works in the VisTrails spreadsheet (QCellPresenter), although no widget get changed there during a drag
** Is it a VTK bug?
** Is it simply impossible to change widgets during the drag, should we do it a different way?
** Did I miss something that is done in VisTrails but somehow not in DAT?
** Low prio, UV-CDAT doesn't run on Windows anyway

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 Updated pull request])
* Single instance code and batch mode

=== June 3, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 pr])
** Requires fixes to command line parameters, Output modules, and batch mode
** How to test this
** Updated missing/outdated flags
** Fixed view issues when generating graphs
* [TE] batch mode
** SpreadsheetOutput not enabled in batch mode. Should we check is_running_gui instead?
** Other instance setting flags from caller
** Is graphsAsPdf replacing spreadsheetDumpPdf?
** graphsAsPdf true by Default?
** Batch mode executing by default (Not needed when generating graphs)
** Re-added workflowInfo as withWorkflowInfo for writing graph and xml workflow
** [DK] batch mode should be outputting to files or stdout, shouldn't always trigger SpreadsheetMode
** execute flag, maybe make execution the default and allow a "--no-execute" if you only want to capture graphs, for example

=== May 27, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] API question
** http://lists.vistrails.org/pipermail/vistrails-users/2015-May/000357.html
* Status of DAT
** Can add VCS plot to DAT but need to work on configuration windows
** Documentation for graphics templates for UV-CDAT/vcs?
* Qt support?

=== May 20, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Reviving the DAT, integrating scripting & porting UV-CDAT!
** On [https://github.com/VisTrails/DAT GitHub] ([https://github.com/VisTrails/DAT/issues issues])
** Merging 2 years of development taking longer than expected, but getting there. The plan is to get the patches in VisTrails and never fork again, we never want to get in UV-CDAT's situation (and don't need to).
** VTK cell works fine on Linux but there was flickering on Mac & Windows before; still issues on Mac (Windows status unknown)
** Can get a VCS plot soon (but will need VTK cell fix)
** Integrate in UV-CDAT's build system (so we have cdms, VCS, ...) -> RR can do this, low priority
** How do we integrate scripting?
*** We want to be able to seamlessly make changes to a plot by changing Python code
*** Define new plots by entering Python code without writing modules/packages?
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 13, 2015 ===
'''Updates'''
* [RR] Test skipping whitelist ([https://github.com/VisTrails/VisTrails/pull/1069 #1069]) -- low priority
* [RR] Custom matplotlib modules can't be compatible with both 2.1 and 2.2 ([https://github.com/VisTrails/VisTrails/issues/1067 #1067]); should be fixed for ALPS ([https://github.com/VisTrails/VisTrails/issues/1070 #1070])

'''Items to Discuss'''
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 7, 2015 ===
'''Updates'''
* [RR] Export/import workflow to Python working!

'''Items to Discuss'''
* [Claudio] UV-CDAT
** The UV-CDAT project is the biggest user base of VisTrails
** VisTrails package management provides a lot of friction towards people plugging in their code
** Need to make it easy to integrate your random Python scripts in the system without having to deal with all the boilerplate, at least in the first step
** [RR] argues that modules are still good; UV-CDAT shouldn't move towards a purely script-based backend
** [RR] export/import with Python could reduce a lot of that friction by allowing 1) to edit workflow as Python 2) to open up boxes automatically if needed code doesn't match actual modules
** ...

=== April 29, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] <strike>Abstractions</strike> subworkflows status ([https://github.com/VisTrails/VisTrails/labels/subworkflows tickets])
* [RR] matplotlib compatibility (2.1 & 2.2), [https://github.com/VisTrails/VisTrails/issues/1067 #1067]
** RR to try and fix ALPS matplotlib modules

=== April 22, 2015 ===
'''Updates'''
* 2.2.0 has been released!
* Windows issue (via email from Ryan)
** issue with manifest file (may be a new file in VTK6?)
** Tommy has regenerated new Windows builds
* Binaries, pypi, and conda released
* [RR] Export as script
* Python sources using VTK need to switch to SetInputData (users should be aware of this)

=== April 15, 2015 ===
'''Updates'''
* Ready for 2.2.0 (apart from binary/deps issues)
** Missing some libs (scikit-learn, tej, tdparser, SQLAlchemy+connectors
** Windows: runvistrails.py is no longer used, so the PATH is wrong
** Windows: pip is broken, but it probably wouldn't work anyway because of permission issues (disable this?)
* Queries, upgrades and getPipeline() usage ([https://github.com/VisTrails/VisTrails/issues/1054 #1054])
** Getting a pipeline with getPipeline() is not safe: it might return an invalid pipeline
** This is used in many places throughout the code, like queries
** Upgrading would require going through the controller, but that creates new actions
* [TC] Avoid copying a module's output if it's used as input by exactly one downstream module ([https://github.com/VisTrails/VisTrails/issues/1060 #1060]) (useful for big numpy arrays you can update in-place)

=== April 8, 2015 ===
'''Updates'''
* [DK] Merged RR's changes for output modules (1012 and 1013)
** RR will merge remaining changes, then create v2.2 branch!

'''Items to Discuss'''
* BNL need numpy array to VTK image
** Looks like VTK has some helpers for this
** We will help if issues arise
** Will contribute back to VisTrails package
* Upgrade issue: [https://github.com/VisTrails/VisTrails/issues/1017 #1017]
** Automatic upgrades should happen between versions of provided upgrades
** Our existing upgrades work around this so it doesn't need to be 2.2.0
* Corner-case VTK modules
** No longer need VTKCell input port, so don't interfere with registry and API anymore
** Still work weirdly, people probably shouldn't use them
** But we have lots of clunky modules since we wrap the whole of VTK; some people might rely on this and know how to use them, let's keep them anyway
** Ready for 2.2.0

=== April 1, 2015 ===
'''Updates'''
* [RR] UV-CDAT: bugfixing for 2.2, long-term plans: implement scripting import/export in VisTrails, port to UV-CDAT
* Possibly, try to move to regular VisTrails to use new features

'''Items to Discuss'''
* 2.2 release: nothing much is pending anymore, release next week?
** [TE] vtkExporter classes [https://github.com/VisTrails/VisTrails/issues/1032 #1032]
** [RR] Hiding upgrades in version tree might make it (or might be 2.2.1 so we can test it out) [https://github.com/VisTrails/VisTrails/issues/949 #949]
** Output modules changes to go in
* add note to documentation about order of parameters in VTK
* add issue about exporter upgrades if not already there

=== March 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* 2.2 release
** Checklist on Github: https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist
** Review output modules
** RR has a couple more issues to fix
** Ready to go -- sign app package for OSX? [https://github.com/VisTrails/VisTrails/issues/984 #984] We need access to the Apple Membership team

=== March 18, 2015 ===
'''Updates'''
* [TE] VTK6 works

'''Items to Discuss'''
* [RR] Release v2.1.5 with backported tabledata?
** MTA example needs updated tabledata (for JoinTables)
** Google Maps package still not available
* [RR] Work torward v2.2.0?
** changes:
*** new persistence
*** API changes
*** output module changes (upgrades?), maintain cells but try to upgrade
*** not wrapping stuff
*** VTK6? yes
*** JobSubmission stuff?
*** relabeling for upgrades [https://github.com/VisTrails/VisTrails/issues/949 #949]
** makes sense, needs the tree view code to be updated, check selection
** See [https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist 2.2 checklist]
* Discussion of [https://github.com/VisTrails/VisTrails/issues/1016 #1016]
** plumbing between outputs and output modes, how to define a mode that works for many outputs without writing for each output?

=== March 11, 2015 ===
'''Updates'''
* [RR] persistent_archive done; merge? ([https://github.com/VisTrails/VisTrails/pull/755 #755])
** note about the focus events for widgets
** TE be aware of file_archive for future binaries that include persistent_archive
* [TE] [https://github.com/VisTrails/VisTrails/pull/998 New VTK package] finished

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails? (see last week; decision needed)
** RR email to JF about this
** yes; email sent to Github
* [RR] Switching order of output ports ([https://github.com/VisTrails/VisTrails/pull/1006 #1006])
** added port specs are sorted at a separate spot (Module.*_port_specs properties) than those in the registry (which are sorted in the registry), but those two lists are just combined without respect to sort keys
** need to determine whether the two lists should be merged or remain distinct
** should make sure that order of input ports and output ports makes parallel connections for things with same order
** DK suggests breaking backward compatibility here: workflows still run, can fix easily if a problem in an existing package.
* [RR] Question about output modes ([https://github.com/VisTrails/VisTrails/pull/1007 #1007]), how to integrate in API ([https://github.com/VisTrails/VisTrails/pull/24 #24])
** Should ImageFileMode be removed? ("image" is not a mode, "file" is)
** ImageOutput missing?
** Feel free to change how formats works
* [TE] Test suite segfaults on Fedora 17 virtualbox. Install newer version? (Support ended in 2013)

=== March 4, 2015 ===
'''Updates'''
* [TE] VTK wrapper
** Works on VTK 5.10
** Still need to test VTK 6
** New general wrappers for python functions and classes

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails?
** When [http://i.imgur.com/UTY2qfg.png filing a pull request] from UV-CDAT/VisTrails, VisTrails/VisTrails is selected by default
** People keep forgetting to change the default ([https://github.com/VisTrails/VisTrails/pull/956 #956] [https://github.com/VisTrails/VisTrails/pull/968 #968] [https://github.com/VisTrails/VisTrails/pull/999 #999] [https://github.com/VisTrails/VisTrails/pull/1000 #1000] [https://github.com/VisTrails/VisTrails/pull/1003 #1003] [https://github.com/VisTrails/VisTrails/pull/1004 #1004] [https://github.com/VisTrails/VisTrails/pull/1005 #1005])
** Only way to change that is to not have it marked as a fork of VisTrails/VisTrails
** Github staff [https://gist.github.com/remram44/b364c24ef1e462ce6e2f can make that change for us]; should we do it?
** Juliana: comments on this? visibility vs. convenience/annoyance for developers
* [RR] What about [https://github.com/VisTrails/VisTrails/issues/991 #991]?

=== February 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] vtkviewcell for infovis support, can we unify with VTKCell?
** need to test this
* [TE] vtk wrapping
** Mostly finished
** VTK 5.10 produce incorrect results with old wrapping
*** Old wrapper is based mostly on VTK 4
*** Most vtk_examples affected
*** [http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Replacement_of_SetInput]
*** should be able to upgrade from SetInput to SetInputData (need to drop GetOutput and replace with self ports)
*** can we change vtkInstance to just return self and not wrap things
** terminator example not working under 5.8?
* How does VTK wrapping fit into general wrapping framework?
* [RR] new persistence package

=== February 18, 2015 ===
'''Updates'''
* [RR] New VisTrails API and IPython integration ([https://github.com/VisTrails/VisTrails/pull/24 #24])

'''Items to Discuss'''
* [TE] VTK wrapping
** [https://gist.github.com/rexissimus/16b74693545b5e7c1035 Benchmarking vtk package]
*** Old: 24.7 seconds
*** New: 10.5 seconds (Except first time that adds 8 sec)
**** The parsing that calls is_abstract (that tries to instanciate all vtk classes) is now only run the first time.
**** get_items_from_sigstring takes 2 seconds, maybe we can use a lookup dict for already computed sigstrings?
** Now using a general python function wrapper
*** VTK classes are wrapped into python function that does not depend on vistrails
*** VTK functions can be executed without vistrails
*** The spec maps functions into vistrails modules, but can also describe wrapping
*** A general python function wrapper that supports
**** kwarg inputs
**** single, list, dict outputs
**** callback for progress reporting
**** temporary file generator for using FilePool
**** optional output generation
*** Creating specs:
***** Create spec by hand
***** Auto-create spec outline (TODO) and manually finish it
***** Dynamically create spec (VTK)
***** Implement documentation wrappers (Can use scikitlearn wrapper to wrap numpydoc) (TODO)
***** Classes as bad functions needs to be wrapped in new functions before they are wrapped. This is different for each package.
****** Classes is hard: Like VTK, and matplotlib. Scikit-learn does still not wrap classes
***** Spec diffing and patching could be done using code from matplotlib.
** Still needs upgrades from old VTK package
*** Is it possible to dynamically wrap functions, e.g, you see a SetFunc and just remove the 'Set' prefix. Or do you need to create a complete mapping?

=== February 11, 2015 ===
'''Updates'''
* Update from Friday's meeting
** discussed VisTrails internals
** discussed wrapping
*** xml discussion, hard to modify because tied to db code
*** TE has made it possible to add the schema-defined attributes to the intermediate representation
*** higher-level operations on the port specs
** make sure the simple case works
*** [JF] take a simple package with documentation and figure out what the base case for wrapping is

'''Items to Discuss'''
* [TE] VTK wrapping
** Dynamic loading works
** Reading XML is fast enough, but [https://gist.github.com/rexissimus/8272d3c776ccfa115d82 unserializing data is slow]
** Working on patterns for patching
** Matplotlib has many advanced patterns like argument ordering, nested arguments, alternateSpecs, output types.
*** Having all this in a general wrapper might confuse users?
** [RR] Delay module (except for identifiers) until you need it---e.g. don't deal with port specs, etc. until necessary
* Scripting Support [https://github.com/VisTrails/VisTrails/pull/950 #950]
** [RR] Issue with getting code from modules
** Design a simple solution
** [JF] Couldn't you use modules as black boxes without conversion, just to call into modules/subworkflows easily from e.g. IPython?
*** [RR] This is a job for the API, and a very separate use case. See [https://github.com/VisTrails/VisTrails/pull/24 #24]

=== February 4, 2015 ===
'''Updates'''

'''Items to Discuss'''
* Wrapping
** Format to use? Currently XML (like current matplotlib)
*** JSON and YAML have simple "to python dictionary" methods
*** But don't stream
*** YAML a lot easier for humans
** [DK] vtk-new-package also changes parameter names, creates enumerations
*** intermediate schema needs to be extensible
*** packages will want to store there specific infos for compute() method generation
*** also might have specs-altering info, like matplotlib's alternateSpec
** representation to code , registry already has schema for some aspects
** [RR] We might want to see if Module subclasses can be created lazily
*** no need to create all the classes just to register them in the registry and never actually use most of them
*** future effort
* [RR] Where should VisTrails packages live?
** tej installs as 'vistrailspkg.tej', TE installed it as 'userpackages.tej'
** Currently, standard packages are 'vistrails.packages.', user packages are 'userpackages.' and packages loaded through pkg_resources might be anything
** [RR] Use 'vistrailspkg.' everywhere?
** Long-term effort to simplify package distribution/installation (and have VisTrails get them automatically?)

=== January 28, 2015 ===
'''Updates'''
* T. Caswell to come visit on Fri 6 to discuss wrapping work

'''Items to Discuss'''
* [TE] New VTK wrapping
** Current code by DK seems a good deal faster
** Generates XML that can be patched/tweaked, generates Python code from it, VisTrails only loads generated Python code
** RR would rather have VisTrails load intermediate representation (= XML) directly, wants to make sure this is not slower
** The goal is to turn the intermediate step into something generic that would be used for every wrapped package (vtk, numpy, matplotlib, sklearn, java) instead of each having its own
** TC has its own code at [https://github.com/Nikea/VTTools/blob/master/vttools/wrap_lib.py github:VTTools] which parses numpy docstrings and generates modules, doesn't yet handle classes or persist anything
* Web crawler
** Right now, TE starts jobs for "start crawler", "stop crawler", "install classifier"
** RR would rather have the crawling be a job as far as VisTrails and tej are concerned
** The whole thing would be one pipeline: load examples, train classifier, start crawler [check for job, kill previous one, upload model, start processes], get snapshot, visualize
*** Need some support in tej and job submission system: long-running jobs, stop a job (wait for it to finish?), restart a job even though results are cached

=== January 21, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Unified wrapping method discussion [https://github.com/VisTrails/VisTrails/issues/991 #991]
** TE to work on reusable method with intermediate representation, starting with VTK
* [RR] Examples for scikit-learn: JF has an old example using Weka with parameter exploration (not currently in source tree)
** AM's examples are enough
* [AM] scikit-learn package is done, merge it in? [https://github.com/VisTrails/VisTrails/pull/955#issuecomment-70286788 #955]
** RR will merge
* [RR] What should copyright headers say? [https://github.com/VisTrails/VisTrails/pull/994#issuecomment-70173935 #994]
** Let's keep everything in there: Utah/Poly/NYU

=== January 14, 2015 ===
'''Updates'''
* [TE] Working on classifier
* [RR] Scripting integration, work in progress

'''Items to Discuss'''
* [RR] Unified wrapping method discussion ([https://github.com/VisTrails/VisTrails/issues/991 #991])
** Let's talk next week, [AM] and [DK] are not here

=== January 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* make sure that we address critical issues, questions, and pending review branches in a timely manner
* scripting support
** [RR] no issues if we want to just keep annotations in the generated code to allow the link back to a workflow
** [RR] can translate from workflow to script, working on script to workflow
** will work for parameter value changes, structural changes require changes to the annotations
** need to publish best practices here
** would be cool to do looping in scripts (easier interface than with workflows)
* notebook support (convert form notebook to workflow)
** RR will sync with FC on this
* Issue with console in built-from-scratch
** [TC] iPython rearranged some of the completion stuff in 2.2 and 2.3
** binary has old version of iPython -> 1.0.0, should we update?
* [TC] automated wrapping of numpy and scipy
** discovered a bunch of malformed documentation in numpy and scipy
** has github repo for vistrails tools
** example modules wrap a bunch of R stuff (not baked in, just how things are)
** will be pushing wrapping logic up
** port names forbidden (window and domain)
** have an import hook to get from yaml directly to VisTrails Modules
** should work for any python modules with well-formed numpy docstrings.
* [Action] should make it clear in documentation that Constant now means serializable not that the value doesn't change (e.g. List)
* [TC] might be interesting to try to build components of matplotlib and accumulate in figure (long-term project, but thinking about how this might work)
* [TE] build and build scripts
** completely automatic, buildbot
** need to set the build machines for the environment we want for the binary
** would virtualenv work here?
** [TC] anaconda can pin versions, potential path to test different configurations
** Q: upload nightly binary builds? A: makes sense, make sure they are well-labeled
* sourceforge stats: e.g. http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07
* package issues (see Remi's message)
* [TE] Scope of tej
** Support single ssh commands?
** Queue can be used as a remote machine (crawler is using queue.call*)
* SourceForge stats: http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07

== Older meetings ==
* [[Development/2014]]
* [[Development/2013]]
* [[Development/2012]]
* [[Development/2011]]
* [[Development/2010]]

Building From Source

2016-06-29T14:07:43Z

Tommy: /* Instructions */

__NOTOC__

== Requirements ==

* Python 2.6 or 2.7 http://www.python.org
* Qt 4.6 (or above) Open Source Edition http://qt.nokia.com/downloads
* PyQt4 (v4.7 or above) http://www.riverbankcomputing.com/software/pyqt and SIP (4.10 or above) http://www.riverbankcomputing.co.uk/software/sip
* numpy (1.4 or above) http://www.numpy.org (scipy)
* scipy (0.7 or above) http://www.scipy.org (scipy)
* matplotlib (0.99 or above) http://www.scipy.org (scipy)

For running various not-required packages and features (packages are listed last, in parentheses):
* SUDS https://fedorahosted.org/suds/ (web services) [http://www.vistrails.org/index.php/SUDS_Patch optional patch]
* MySQLdb http://sourceforge.net/projects/mysql-python (accessing databases)
* VTK (5.4.2 and above) http://www.vtk.org (vtk)
* matplotlib http://matplotlib.sourceforge.net/ (pylab)

== Instructions ==

'''[[Mac Intel Instructions|Click here for specific instructions for Mac OS X]]'''

* Install Python
** On most Linux distributions it comes by default.
** On Windows: Get the msi release 2.7.x [http://www.python.org/download/ here]
** Add the installation directory to the PATH variable

* Install Python Extensions
** Install SUDS if you plan to use web services package
* Install VTK (if you need VTK - for infovis support install the development version)
** First you'll need CMake: get the latest release [http://www.cmake.org/HTML/Download.html here]
** Then you can get vtk: follow the instructions to download the source code on this [http://www.vtk.org/get-software.php page]
** '''(Skip this step if you don't need to run CORIE workflows)''' Follow [[ExtraVTKFIles|these instructions]] to add CORIE and other needed files to VTK.
** To compile VTK follow the instructions in the file ''README.html'' in the root of VTK directory tree
** On configuring CMake, make sure that the variables VTK_WRAP_PYTHON, VTK_USE_GUISUPPORT, VTK_USE_DISPLAY are ON and VTK_USE_QVTK is OFF
** It is recommended to create a environment variable called PYTHONPATH
*** PYTHONPATH=''<path/to/vtk_build>''/Wrapping/Python:''<path/to/vtk_build>''/bin:.
* '''For Linux only''': Install Qt 4.6.3 or above (Qt 4.8.X recommended)
** You can get the open source version for all platforms [http://www.trolltech.com/download/opensource.html here]
** Run '''configure''' then '''make'''
* '''For Linux only''': Install SIP
** Downloads available '''[http://www.riverbankcomputing.com/software/sip/download here]'''.
** Uncompress the file, and inside the directory, type '''python configure.py'''. On 64-bit Linux type '''python configure.py -d /usr/lib64/python2.7/site-packages/'''. Then '''make''' and '''make install'''
* Install PyQt4
** Downloads of the latest stable release and latest snapshots are available '''[http://www.riverbankcomputing.com/software/pyqt/download here]'''.
** '''Windows only''': Download the binary package that contains everything you need to run PyQt4. This will install SIP and Qt for you.
** '''For Linux only''': Uncompress the file, and inside the directory, type '''python configure.py'''. On 64-bit Linux type '''python configure.py -d /usr/lib64/python2.7/site-packages/'''. Then '''make''' and '''make install'''

* Install MySQLdb (Python library allowing MySQL databases access)
** The file is available [http://sourceforge.net/project/showfiles.php?group_id=22307&package_id=15775 here]
* Install SciPy
** Windows
*** First download and install [http://sourceforge.net/project/showfiles.php?group_id=1369&package_id=175103 NumPy] and then [http://sourceforge.net/project/showfiles.php?group_id=27747 SciPy]
** Linux
*** Download and install BLAS [http://www.netlib.org/blas] - Note: Most package managers allow easy download and installation through the native interface however; you must also get the source code and set the environment variable BLAS_SRC
*** Download and install LAPACK [http://www.netlib.org/lapack] - Note: Most package managers allow easy download and installation through the native interface however; you must also get the source code and set the environment variable LAPACK_SRC
*** Download and install numpy [http://numpy.scipy.org]
*** Download and install scipy [http://www.scipy.org]
* Install matplotlib
** Windows
*** Get it [http://sourceforge.net/project/showfiles.php?group_id=80706&package_id=278194 here]
** Linux
*** Files are available [http://sourceforge.net/project/showfiles.php?group_id=80706&package_id=82474 here]

* To run VisTrails from source:
** Excute this on a terminal window or on a command prompt on Windows:
cd /path/to/vistrails_src
python vistrails/run.py

Building From Source

2016-06-29T14:06:39Z

Tommy: removed zip/unzip added VTK 6

Development

2016-06-22T15:04:04Z

Tommy: /* 2016 */

<div class="nonumtoc toclimit-1">
__TOC__
</div>

See also the [https://github.com/VisTrails/VisTrails/wiki/Development Github wiki]

== 2016 ==

=== June 22, 2016 ===

'''Updates'''

'''Items to Discuss'''
* [TE] Fix for upgraded analogies (PR [https://github.com/VisTrails/VisTrails/pull/1177 #1177])
** Uses module location to find module remap (The best we can do right now?)
** Also fixes remapped port names for connections to existing modules
** May still fail on complex upgrades like adding a function on an upgraded module that has a different port name

* [TE] Working on exporting wrapped libraries (VTK)

=== June 15, 2016 ===

'''Updates'''
* [TE] Added depth logic to python script exporter ([https://github.com/VisTrails/VisTrails/commit/50f220e4f6abe5a7bb8689f73f456f43df2dbc12 full commit])
** Fully implements connection merging and list looping

'''Items to Discuss'''

* [TE] Making analogy work on upgraded workflows ([https://github.com/VisTrails/VisTrails/issues/1175 #1175])
** Analogy only works We need to use the non-upgraded action chain
** But pipelines need to be valid (matcher uses module portspecs)
** Tried to get upgrade remap from upgrade action, but this seems impossible
** Use module location instead?
*** Location should be identical for one-to-one module upgrades

=== June 1, 2016 ===

'''Updates'''
* VisTrails 2.2.4 announced (finally)
** 5 survey replies
** 47 downloads last week

'''Items to Discuss'''
* [TE] Export VTK as script (python-wrapper)
** to_python_script
*** needs the pipeline (or at least the connections)
**** Should not generate code for any possible VTK method (exporter detects which ports is used in the source)
**** VTK needs to know connection order
**** Adding functions directly to the script results in nicer code
** Add support for multiple input connections
** Add support for list looping

=== May 25, 2016 ===

'''Updates'''
* Mailing-list fixed
* Getting stats from the "server news" mechanism (via [https://github.com/remram44/apache-log-info parser])

'''Items to Discuss'''
* [RR] Alexis doing writeup on VisTrails, curious about interesting streaming use-cases (and potential future users)
* [TE] Union ports
** Show union ports in pipeline (DEMO)

=== May 18, 2016 ===

'''Items to Discuss'''
* [TE] mailing list still down - Julio working on it
* [TE] Improved union port
** New schema 1.0.5 adds portitem.union string attribute
** Works with pipeline view, parameter exploration view, and mashup view
** Should work well for matplotlib
** Use with VTK ports?
*** It uses [item_1,item_2] style ports usually with different tuple length.
* [TE] Remove emacs dependency from db generate [https://github.com/VisTrails/VisTrails/issues/1173 #1173]

=== May 11, 2016 ===

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]
** GUI-based solution [https://github.com/VisTrails/VisTrails/tree/union-port Branch union-port] Demo?
*** Shows single port for all ports with same sort_key
*** Select specific type when adding/showing
*** Only one type should be visible on the module at any time
*** Making tuple parameters union types is probably too complicated
*** Should work with alternate specs like matplotlib (if sort_key is defined correctly)

* [TE] Feature suggestion: Let connections connect to functions/parameters
** Show functions and parameters as ports and toggle port visibility directly for functions and parameters
** Use separate views for ports and functions (like before)
*** Allow rearranging of functions
** Pros:
*** Supports ordered connections. Create 2 functions, make them visible as ports, make connections to them.
**** We can also have, e.g., a line joining the ports on the module to indicate they are part of a list.
**** Makes List module simpler
*** Connect to parameter in tuple
*** Functions that are visible on the module can connect to an actual function, and not just to the first one it finds.
*** Can replace operation modules (in python-wrapper) in some cases for, e.g., numpy.
** Cons:
*** Interface more complicated and crowded
*** More difficult for users to grasp?
*** No immediate use case
*** Makes no union type for tuple parameters a bigger problem.

* [TE] Publish user survey?
** No response from vistrails release yet
** Not announced on vistrails-users yet.

=== May 4, 2016 ===
'''Updates'''
* VisTrails 2.2.4 released

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]

=== April 27, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Wrapping Bokeh
** New method type "operation"
*** Transforms Figure->Glyph->Output into Glyph->Figure->Output
**** Glyph sets function name and arguments as output
***** Not serializable, but should always be computed together with the subject of the operation.
**** Figure applies Glyph operation on itself
*** Useful for matplotlib?
**** matplotlib currently find actors by searching upstream?
**** But this is more difficult since matplotlib is not function-based.
** New "union" port type
*** Turns "x(float), x(list)" into "x (float, list)" and uses first set value
**** Uses only first value in tuple
**** Bokeh have many properties that support (list, string, Float)
*** Does not work with depth=1 types (e.g. Float of depth 1)
**** Turn Depth 1 types with known type into lists?

* [TE] New bugfix release
** Finalize survey

=== April 20, 2016 ===
'''Updates'''
* Merged upgrade fixes
** Now has infinite loop test
** loop test now correctly loops 5 times
*** remap_module used wrong (current) package version when creating ModuleDescriptor
* Fixed multi-step group upgrades (PR: [https://github.com/VisTrails/VisTrails/issues/1168 #1168])

'''Items to Discuss'''
* New bugfix release
** Merge usagestats
** Need to finalize survey

=== April 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Chaining upgrades done ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Replace "Upgrade" description annotation with "upgraded_from" annotation to identify which tags to hide?

* [TE] Iterating handle_invalid_pipeline ([https://github.com/VisTrails/VisTrails/pull/1165 #1165])
** Not based on [https://github.com/VisTrails/VisTrails/tree/chain-upgrades-loop chain-upgrades-loop]
** Cherry-pick test to preserve source?
** Need maxPipelineFixAttempts option?
*** The code is now smarter about recursion, so max attempts will "probably" never be reached.
** Need [https://github.com/VisTrails/VisTrails/commit/0ef0667426937eddb1d1c1e397f0657ffec039a9 debug messages]?
*** Would need to be moved into handle_invalid_pipeline

=== April 6, 2016 ===
'''Updates'''
* [TE] Query View improvements
** Done except for displaying "Version Info" and #1164
* [RR] Working on finishing new interpreter (finally!)

'''Items to Discuss'''
* [TE] Chaining upgrades ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Try latest upgrade first, then previous.
** If all fail, select latest upgrade?

=== March 30, 2016 ===
'''Updates'''

'''Items to Discuss'''

* [TE] Query View improvements
** Unified do_version_switch and get_upgrades as validate_version()
** Problems with query view using its own controller
*** Fixed module info not being displayed for query results
*** Still no version info for query results
*** Still an issue with version query view not being updated

=== March 23, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Usage reporting almost ready to go
** Need to record whether specific features are used: paramexpore, mashup, query
*** [DK] Record if LaTeX extension is used? But hard to distinguish from direct batch invocation
** How to record size of vistrail?
*** [DK] IdScope already walks over vistrail, use that
*** but total number of modules and versions doesn't give an idea of average size of individual pipelines

=== March 16, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Upgrades in Query Mode
** Now using code similar to do_version_switch
*** Uses handle_invalid_pipeline
*** Differences: Not using current_pipeline, flushes changes
*** New controller method get_pipeline optimized using cached pipelines (but not current_pipeline)
*** Integrate to avoid repeated code?
*** Use this for query mode?
* [TE] VisTrails 2.2.4 ready for release?
** tej package updated. Others?
* [JF] upgrades and the version tree
* [JF] provenance in Jupyter
* [DK] bundles: [https://github.com/VisTrails/VisTrails/pull/1092 #1092]

=== March 9, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixing search mode
** String query now matches all by default
*** This caused pipeline queries to never match
** String query can search: User/Notes/Tagname/Time/Module name
*** Should we search module names by default? (Disabled by default because it is expensive)
*** Fixed notes search
** '>' parameter queries in documentation but has been removed
** Fixed module matches for upgraded pipelines (By not upgrading pipeline)
*** Upgrades still a problem
*** Add "Upgrade all menu option?" (Or upgrade all on open when `hideUpgrades`)
*** [JF] Allow search on past tags

* [TE] Create new bugfix release
** Finish querying
** Path issue on windows

* [DK] Look into sqlalchemy and new bundle branches

=== March 2, 2016 ===
'''Updates'''
* [TE] Fixed cache bug with port specs
* [TE] VisTrails Next
** Most packages now work
** No qgis for Python 3

'''Items to Discuss'''
** Always dereference symlinks? [https://github.com/VisTrails/VisTrails/issues/1146 #1146]

=== February 23, 2016 ===
'''Updates'''
* [TE] Fixed PythonSource 100% CPU bug
* [TE] VisTrails Next
** Updated [http://opendap.co-ops.nos.noaa.gov/axis/webservices/wind/ NOAA Web Service] examples
*** Now uses REST service, tabledata, and Google Maps
*** Web Service replaced with DownloadFile

'''Items to Discuss'''
* [RR] Couple of fixes are in for API, and tej&reprounzip on the Mac binary. Also new release of tej, and working on anonymous usage reports.
** New 2.2 release soon?
* [RR] Anonymous usage reports
** Sends out info like number of modules & versions, packages used, Python & libs versions, execution time, specific features [https://github.com/VisTrails/VisTrails/pull/1154 #1154]
* [JF] Bring in noWorkflow to track variable dependencies, for the considered Jupyter integration?
* noWorkflow - provenance for python scripts
** Recent work on tracking dependencies
* Also integrates ReproZip with Jupyter
** [http://mybinder.org mybinder]
*** Use with ReproZip to automatically build Jupyter notebook interfaces
* Daves comments on Jupyter integration
** It is possible to identify cell order on the server side
** Not trivial to track order of cells on client side
* How does Galaxy workflows relate to VisTrails?
** Packaging in Galaxy is hard
** Galaxy for biomedical workflows, difficulty making it general
* Action items
** How difficult to track cell dependencies in Jupyter notebooks?
** Use noWorkflow to track cell dependencies?
** How difficult to modify mybinder to use ReproZip packages?

=== February 17, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixed Group memory usage
** Modules in groups are supposed to be freed when done executing
*** Prevented by logger that stored references to the modules (fixed, now using id(module))
*** Prevented by list iterator bug that stored list of modules on the 'self' port bug (fixed)
* [TE] VisTrails Next
** Removed deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** PythonSources will be upgraded
*** Fixes for Python < 3
*** fixes for VTK < 6
** TODOs
*** Remove RemoteQ
**** Port Hadoop to tej (Already have pbs)
*** Merge package wrapper
*** Finish SQLAlchemy branch
*** Finish new bundle branch
** [JF] Will contact Jeff and Matthias about moving to Python 3
* [JF] Query by Example is broken
* [JF] VisTrails Data Cleaning Project
** Use VisTrails to process and explore task-specific data while keeping provenance.
** Remi's Idea
*** Use VisTrails as the backend in a Jupyter notebook
*** Overcome problems with executing cells in random order
**** Interesting research topic, but little interest has yet been noted
*** Interesting to study how such a notebook would be used (Is there notebook usage data available?)
*** Impose restrictions to notebook cell boundaries
*** It will only work for functional operations
*** Can we fix, or detect, non-functional (mutating) operations?
*** Analyse code and data flow and see if it mutates data in unexpected ways?
*** Mutable operations can be created in many ways in Python
* Next meeting Tuesday 11:30

=== February 10, 2016 ===
'''Updates'''

'''Items to Discuss'''
* VisTrails Next
** Test suite passes
*** Python 3 less deterministic, module upgrade order random.
** [RR] updating packages: Reprounzip (pushed), tej, persistent_archive, ...
** All of our packages should run fine :)
** VTK thumbnail comparison works
*** Rendering bug on some systems
**** QVTKCell now inherits QGLWidget
*** Old thumbnails had wrong height due to spreadsheetwindow being too small
**** Fixed by regenerating thumbnails
*** Silenced deprecation messages when generating modules
*** Many new classes in VTK 7
** Remove deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** Will break existing PythonSources
**** Try to upgrade?
*** Old-style packages
**** Or only allow a new style, like __init__.py renamed to info.py? (merge with identifiers.py?)
***** Read info.py without importing package?
*** Fixes for Python < 3
*** Fixes for Qt < 5
*** fixes for VTK < 7
*** Remove self port?

=== February 3, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] [http://lists.vistrails.org/pipermail/vistrails-users/2016-January/000402.html Rendering a .pvd (ParaView) file?]

* VisTrails Next
** All tests but thumbnail comparison passes
** Still issues with gui and more packages needs to be tested
** PythonSource and MplSource upgraded with lib2to3
** Keep contrib packages? Update?
** [https://blog.kitware.com/vtk-7-0-0/ VTK 7 is released]
*** Supports Python 3
*** Will hopefully get into conda and others soon
*** Deprecates a bunch of modules

* [https://travis-ci.org/VisTrails/VisTrails/builds/106743348 Travis builder] for VisTrails Next
** Runs!
** Uses conda
*** Many levels of requirements
**** apt packages
**** conda packages
**** python packages in requirements.txt
**** python packages in setup.py
*** Can probably drop conda. Default builder does not have Qt5, but beta builder do!
*** But useful if we want to use conda in our own build process.
** Lots of errors I do not get locally?

* [http://goo.gl/forms/Z4HBrwaBWL User Survey]
** Have you used any alternatives to vistrails?
*** Relevant? More options?
** How often do you use any of these particular features in VisTrails?
*** Add/Remove alternatives?
** How important would you rank the following potential improvements to VisTrails?
*** Add alternatives?

=== January 27, 2016 ===
'''Updates'''
* New interpreter
** Working prototype soon
** Looping not completely done (and port combination mode: pairwise/cartesian...)
** Need to integrate with VisTrails
*** Compatibility with existing modules
*** Use log controller
*** Want to cache at multiple levels (whole stream/single element of stream)
*** Non-runtime attributes of modules (cache check, automatic conversion check, constant from/to string)

'''Items to Discuss'''
* User Survey

* ZMQ failing on windows (vistrails-users)

* [TE] [https://github.com/VisTrails/VisTrails/pull/1143 Python 3 branch]
** Testsuite almost passes
*** Failing are unicode filenames, some users guide examples, and thumbnail comparisons.
** Fixed issues
*** Signatures are now bytes (convert to string to show in widget)
*** Cannot compare different types, e.g., (None < 1)
**** PortSpec.depth and min/maxConn could be None. (Backport!)
**** cell.row could be None
*** Lots of unicode/bytes fixes to serializations
**** We have encryption implementations in the code! (keychain)
*** Lots of small fixes to package method differences
** Current issues
*** logging widget empty?
*** version tree signals messed up
*** provenance view legend icons black
*** Text do not fit in some widgets
*** VTK thumbnail comparison fails
**** VTK Cells have some faces in wrong direction?
**** Because running in VM?
** Installing on Ubuntu LTS/Latest Mint
*** Install latest matplotlib from pip
*** Install VTK 7.0.0rc2 from source
*** No QtWebEngine binary (controversial) (Must install sip/PyQt5/Qt5 from source)

=== January 20, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Backporting features from Python 3 + PyQt5 + Qt5
** Merged unicode with master ([https://github.com/VisTrails/VisTrails/tree/unicode unicode])
*** One unicode test failing
*** Problem saving to xml
** Used [http://python-future.org/ python-future] to run futurize stage 1 to update legacy (pre 2.6) code ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized unicode-futurized])
*** Updates print to functions 'from __future__ import print_function'
*** Updates exception calls to use 'as'
*** removes most usages of 'long' (mostly used unnecessarily)
**** Only needed for 32-bit support
*** Fixes relative imports (from __future__ import absolute_import)
** Fixing code that is deprecated in Qt 4.8 and removed in Qt 5 ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized-qt5 unicode-futurized-qt5])
*** Updated all signals to new-style
* If we go 2 to 3, this could break packages
** means we should schedule any package format changes for the same time
** e.g., imports should be unrelated to code path (function to load module from package identifier?) (take them out of vistrails.* [https://github.com/VisTrails/VisTrails/pull/1002 #1002])
** any structural changes (e.g. the __init__ versus init thing) (RR thinks it makes sense, though having both named "init" is unfortunate)
** putting package identifier as xml?
*** Python not so bad, plus some stuff in there is Python code (checking dependencies)
** version the APIs?
*** RR planning on versioning vistrails_module.Module, no point versioning the whole package?
* file formats on 2 to 3:
** no real translation/upgrade, but non-ascii values that work on 3 won't load in 2

=== January 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://gist.github.com/rexissimus/dfd27e466427529c385c Porting to Python 3 / PyQt5]
** Basic GUI and execution works
** Minimal work to support 2to3
** Hard to support both PyQt4 and PyQt5

=== January 6, 2016 ===
'''Updates'''
'''Items to Discuss'''
* Updating VisTrails dependencies
** Successfully built [https://gist.github.com/rexissimus/f1a1aada7de1c00a57c7 Win7-64/Python3/PyQt5/Qt5/WebEngine/VTK7]
*** VTK 7 is the first supporting Python 3 but is only in release candidate phase.
**** Next version of VTK 6 is rumored to support Python 3
**** There is a development branch of VTK 6 supporting Python 3
*** Can travis build this?
**** We can skip tests for WebEngine and VTK if needed
** Python 3 [https://python3wos.appspot.com/ showstoppers]
*** No MySQL-python (sqlalchemy supports mysql through other drivers)
*** No suds (there are active forks but we could also drop support?)
* Options for python2/3 support:
** Interpreter could be python2/python3 based on packages
** six layer works but not the easiest to maintain (e.g. in reprozip)
* Drop support for win-64
* Update copyright headers to 2016

== 2015 ==

=== December 30, 2015 ===
'''Updates'''
* Bokeh package finished
** Can output to Browser/IPython/Spreadsheet (Limited functionality in spreadsheet)
'''Items to Discuss'''
* Updating VisTrails dependencies
** Bokeh needs QWebEngine (Chromium) in Qt5 which requires PyQt5
*** Many plotting libraries only work in browsers
*** But Chromium may be a big and controversial dependency
*** Or create a browser version of the spreadsheet?
** Some users have requested Python 3
** Not backwards compatible?
** Target for VisTrails 3.0 with new interpreter?

=== December 16, 2015 ===
'''Updates'''
'''Items to Discuss'''
* Users list question
* [TE] Wrapping Bokeh
** Added bokeh property parser
*** complements numpydoc parser
*** Not all attributes are available, partially because I am using a pre-release version.
** Wrapped modules
*** bokeh.plotting finished (Backwards like matplotlib: Create plot then draw on it)
*** bokeh.charts mostly done (Missing arguments)
** QWebView mostly works (but no zooming or buttons)
*** It would be better to use external browser or QWebEngineView
** Added improvements to wrapper
*** Generalized port translations (Color/Path to native types)
*** Can use multiple docstring/property parsers simultaneously

=== December 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Looking into wrapper
** Will port TensorFlow
** Doing a pass on the wrapper code & doc
*** UX improvements
** Factorize high-level docstring parsers into core.wrapper? (sphinx, numpy, google)
** Problem with name vs module_name (fails sklearn tests because class_by_name() is broken)
** Looking into compressing specs, lazy registration of modules

=== December 2, 2015 ===
'''Updates'''
* [TE] Package wrapping
** Wrapped most of numpy/scipy using __all__
** Added class attribute and method access for classes (Can add to class or to separate inspector module)
** TODO: Document wrapping procedure

'''Items to Discuss'''

=== November 25, 2015 ===
'''Updates'''
* [RR] New interpreter is coming along
** Everything is a stream
** Task system, eventually work-stealing parallelism
** Streams no longer advance in lock-step
*** Allows for constructions like filter, join, sorted-merge
** depth>1 still to be tested, no current plan to allow this through the module interface
*** Through looping though, can do streams of streams

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapped most numpy functions (no polynomials)
** and half of scipy classes and functions
** Added functions manually from documentation (no parseable lists?)
** Focusing on data flow constructs (no property/method access for classes)
*** Using spec diff (empty for now) and dynamic parser (stores spec in .vistrails/)
** Python class/function wrapper now stable
** Add google doc parser?
*** Is there a parser available?

=== November 18, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Numpy class wrapping works
*** Basic type is List, since most types are array_likes.
*** TODO: More classes and functions
*** Some operations are in-place and some aren't, and docstring not super clear
*** [RR] It seems only methods mutate, and most have a numpy.xx function equivalent; just manually go through the methods and remove the mutating ones?
** Class wrapper is modular
*** Docstring parser and type string parser can be customized
*** Classes can have optional attribute/method ports
**** Inspectors and attribute/method modules can be created separately
** Use PythonCalc as an example
*** Can be re-implemented as a function with a parseable docstring
*** [RR] PythonCalc is just an example, and it might actually make sense to get rid of it, or do a proper math package with scalar operations (as separate modules, no combobox)
** [RR] TensorFlow to use wrapping as well
*** Very simple (only types 'tensor' & 'variable')

=== November 11, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapping numpy's classes using numpydoc (ndarray)
*** Wrapping constructor arguments, attribute getters/setters as module ports
**** Then how to access attributes afterwards?
***** Use input value port to class modules?
*** Wrap methods as modules? E.g., `ndarray.shape`.
*** Function wrapping is almost a subset of class wrapping
**** May be able to use the same parsing/execution methods
** VTK's non-getter/setter methods could be wrapped as modules
*** We could then remove extra logic in interpreter for keeping function order
** Bokeh uses autogenerated docstrings
*** We may be able to read the specification directly

* [RR] [https://github.com/VisTrails/VisTrails/pull/1138 TensorFlow package]
** Basic setup working, can execute the Mandelbrot example
** Will autogenerate the operations

=== November 4, 2015 ===
'''Updates'''
* [RR] Interpreter work requires a fix for [https://github.com/VisTrails/VisTrails/issues/1137 DB issue #1137]
* [DK] Kitware's Resonant [http://www.kitware.com/source/home/post/173]
** [https://github.com/girder/girder Girder]: data management system
** [https://github.com/Kitware/romanesco Romanesco]: execution engine, uses [http://www.celeryproject.org/ Celery] for task management
** Resonant Flow: web app for editing and executing workflows

'''Items to Discuss'''
* [TE] Added OSX Lion (10.7) VM on build machine using vagrant (seems ok with license?)
** New builds works on Lion
** Change the minimum requirement to 10.7?
* [TE] Package wrapping
* Added upgrade suggestions using 2 spec versions ([http://pastebin.com/30XUU8Gp example])
** using name edit distance to find matches
** Could use something better like port similarity for modules, and type similarity for ports
** Should write python upgrade code?
** Added spec to sklearn package
*** Can now diff spec versions and keep the spec static
*** There will be problems with downgrades and package versions

=== October 29, 2015 ===
'''Updates'''
* [TE] nightly-build-mac fixed (Needed to approve xcode license)

'''Items to Discuss'''
* [TE] matplotlib wrapper
** ported to general spec
** Diff can be used on general spec
*** Only needed minor changes
*** Fixed indexing bug that corrupted specs
*** Can now move diff tools to core/wrapper
** Add new plots?
*** New plots in mpl 1.3: eventplot
*** New plots in mpl 1.4: angle_spectrum, magnitude_spectrum, phase_spectrum', violinplot
*** No new plots in mpl 1.5 (from looking at boilerplate.py)

=== October 21, 2015 ===
'''Updates'''
* [RR] Alexis has arrived, will be working with [RR] on a more efficient interpreter

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package]
** Supporting multiple package versions
*** Check which version can be loaded [https://github.com/VisTrails/VisTrails/pull/1135 #1135]
*** We cannot show version requirements in the list of packages because old packages are loaded when importing the codepath
** Visual diff does not work well, but we can use the spec differ to see differences.
** Unifying vtk and matplotlib wrapping specs (WIP)
*** And porting matplotlibs spec differ to work on the general spec
*** Spec differ can then be used on vtk and other packages in the future
*** Will enable automatic upgrade generation
* [RR] Rework interpreter
** restore abstraction between interpreter/module code
** build looping, streaming, caching into the interpreter
** rework cache
** look into parallelism once basic functionality is there

=== October 14, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package] (adding numpydoc parser)

=== October 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/tree/fix-matplotlib-parser New matplotlib parser] (adding numpydoc parser)
** Added numpydoc attribute parser for plots.
*** TODO: Need better port spec reconciliation with call signature parser.
*** We can create a general numpydoc parser, but attribute types are unique to matplotlib.
** Needs package versioning
*** New spec will not support matplotlib < v1.4 due to changed path to axes classes.
*** Load spec version corresponding to installed matplotlib version?
*** Need version downgrades?

=== September 30, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Updating Matplotlib parser
** Matplotlib docstring parser fails on numpy docstrings
** I have [https://github.com/VisTrails/VisTrails/commit/eae8b0c16260810587e47c41cab53552cbb3cf0a added basic numpydoc parsing]
*** Only used by a few docstrings so far
*** Parsing uses many sources (class tables, signatures, ACCEPTS, method docstrings, definition parsing).
** Caswell said they were thinking about moving to traitlets, but this is not ready yet

=== September 23, 2015 ===
'''Updates'''
* [TE] VisTrails 2.2.3 released
** Also have pushed to PyPI, binstar, etc.
** Sourceforge vs. GitHub
*** should be able to host releases on GitHub
*** nightly binaries pushed to sf each night
*** old binaries?
* [TE] Re-wrapping MatPlotlib
** Keep static generation - Docstrings are brittle beween matplotlib versions
** Keep generating the executable classes - but create functions, not vistrails Modules
*** Why is there so much patching?
** Re-implemented Alternate PortSpec for InputPortSpec
*** It will now inherit specs from parent (No need to reimplement)
** Module upgrades?

'''Items to Discuss'''

=== September 16, 2015 ===
'''Updates'''
* [TE] Job Monitor tests and documentation done
** OK to leave document package in packages directory?

'''Items to Discuss'''
* [TE] Library wrapping: How to do code patching? [https://docs.google.com/drawings/d/1Sh3eOXot6v2y880jHKQrqXqAwr-0aoqYligg3z8G8MY/edit?usp=sharing Wrapping diagram]
** Insert code into module template (Old VTK code)
** Patch the library that is called (New VTK code)
** Somehow store code in spec and apply when executed?
*** Executed code needs at a minimum access to inputs, outputs, current class
*** Use standard input/output dict and obj reference that the code operates on?
*** Can this be done while keeping the execution abstract?

* Do new release now?

=== September 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* New release?
** [RR] wants reprounzip
** tej changes & doc
** job monitor & jobmixin fixes
** mongodb
** reprounzip
** warning: MplFigure type is int
** tabledata: add Reshape, DictoToTable & ListToTable, fix ListToTable with numpy arrays
** PythonSource can have same name for an input & output
** don't show spreadsheet at exit

=== September 2, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Limit autosaves? [https://github.com/VisTrails/VisTrails/pull/1126 #1126]

=== August 26, 2015 ===
'''Updates'''
* [TE] Added Job support to Parameter Explorations (Requested by Colin), and Mashups
** specify job ids, need to specify different ids for parameter explorations since they have the same version id
** how to deal with parameters passed in on command line
* [General] provenance: should be creating a new version when we execute workflow with changed parameters?
** currently, custom_params annotation stores this in provenance currently
** [RR] API doesn't record provenance if passing in parameters: http://git.io/vsAA5
'''Items to Discuss'''

=== August 19, 2015 ===
'''Updates'''
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [TE] Working on Job Monitor documentation

'''Items to Discuss'''
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [TE] Stop testing VisTrails 2.0?

=== August 12, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Build broken on Travis; because of IPython 4 released today? ([https://travis-ci.org/VisTrails/VisTrails/builds/75279795 build 992]; [https://github.com/VisTrails/VisTrails/issues/1123 #1123])

=== August 5, 2015 ===
'''Updates'''
* [TE] Fixes to Jobs
** Could not delete jobs
** Could not run job in group
** Job not reset when calling ModuleSuspended
** Added deleting job from context menu
* [RR] Writing documentation for everything [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

'''Items to Discuss'''

=== July 29, 2015 ===
'''Updates'''
* RR still looking into new interpreter thing
** Goal is to take out scheduling logic from Module so it can be split in multiple processes, and so that smarter strategies can be added in time
** This means some work on packages
** Spreadsheet can live in kernel process? Still some UI stuff that will take work (changing configuration, persistent archive's viewer, ...)
* [TE] Problems running examples [https://github.com/VisTrails/VisTrails/pull/1111 #1111]
** Testing of more examples requires additional packages on the test machines.
** Fixed faulty line-ending in PythonSource:s failing on Python 2.6.
** Test suite now testing SUDSWebServices (If web service is down, test suite will fail)
** preferences.py test failed reloading 'dialogs' package, switched to using 'URL'.

'''Items to Discuss'''

=== July 22, 2015 ===
'''Updates'''
* [TE] mailing lists back online
* [TE] Working on [https://github.com/VisTrails/VisTrails/issues/1107 #1107]
* [RR] Working on ReproZip package

'''Items to Discuss'''
* [RR] MongoDB package [https://github.com/VisTrails/VisTrails/pull/1106 #1106]
* [RR] Example for tej docs? [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

=== July 15, 2015 ===
'''Updates'''
* 2.2.2 released

'''Items to Discuss'''
* RR is considering executing everything in an IPython kernel (i.e. separate Python interpreter, like the one spawned for a notebook)
** It's a separate process that we can restart without restarting the app/gui
** We can isolate the execution environment (e.g. for the server)
** We can run the whole thing remotely (if your data is elsewhere, just run VisTrails locally and the pipeline elsewhere)
** Pipeline execution no longer makes the interface hang, it just makes the kernel hang (but that's fine)
** We can use notebooks as modules (probably way nicer than the PythonSource module)
** We can run multiple kernels so long as the ports carry things that are serializable
*** meaning we can put the multithreaded-interpreter without all the hacky parts it has now
*** we can run IPython kernels in all the languages IPython supports, [https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages currently 46]

=== July 8, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Buildbot github hook not working after IP address change
* [TE] No reference to VistrailsApplication ([https://github.com/VisTrails/VisTrails/issues/1103 #1103])
** [RR] Added PR [https://github.com/VisTrails/VisTrails/pull/1104 #1104]
* [TE] Reopening VT file after saving with bundled subworkflow won't offer subworkflow upgrade ([https://github.com/VisTrails/VisTrails/issues/1102 #1102])
** allow manual delete to fix right now
** fix this on top of the use-uuid branch
* [TE] Release VisTrails 2.2.1? ([https://github.com/VisTrails/VisTrails/blob/v2.2/CHANGELOG CHANGELOG])
** [https://github.com/VisTrails/VisTrails/pull/1093 output-modules-use-global-dir]
** [https://github.com/VisTrails/VisTrails/milestones/version%202.2 Current issues for 2.2]

=== July 1, 2015 ===
'''Updates'''
* [TE] PROV fixed
* [TE] Working on subworkflow issues
* [RR] Considering reworking the controller (log vs exception problem, retained upgrades causing interferences) and also the interpreter (IPython?)

'''Items to Discuss'''

=== June 24, 2015 ===
'''Updates'''

'''Items to Discuss'''
* UV-CDAT
* [TE] Can a cyclic workflow be valid? ([https://github.com/VisTrails/VisTrails/issues/1097 #1097])
** focus on disabling the ability to create cyclic pipelines because more things break than just this with a cyclic pipeline
* [RR] Relative paths ([https://github.com/VisTrails/VisTrails/pull/1057 #1057])
** This interacts with the new bundle; how do handle packing files inside the VT bundle?

=== June 17, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] current_version and reusing existing upgrades are broken ([https://github.com/VisTrails/VisTrails/issues/1095 ticket #1095])
** Could be that export to PROV is using an unflushed upgrade pipeline?
** current_version would then be correct.
** It may work to flush the actions before exporting?

=== June 10, 2015 ===
'''Updates'''
* DAT: fixed VTK issue on Linux and Mac
* Still crashes on Windows. Need help! Reminder: this works in the VisTrails spreadsheet (QCellPresenter), although no widget get changed there during a drag
** Is it a VTK bug?
** Is it simply impossible to change widgets during the drag, should we do it a different way?
** Did I miss something that is done in VisTrails but somehow not in DAT?
** Low prio, UV-CDAT doesn't run on Windows anyway

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 Updated pull request])
* Single instance code and batch mode

=== June 3, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 pr])
** Requires fixes to command line parameters, Output modules, and batch mode
** How to test this
** Updated missing/outdated flags
** Fixed view issues when generating graphs
* [TE] batch mode
** SpreadsheetOutput not enabled in batch mode. Should we check is_running_gui instead?
** Other instance setting flags from caller
** Is graphsAsPdf replacing spreadsheetDumpPdf?
** graphsAsPdf true by Default?
** Batch mode executing by default (Not needed when generating graphs)
** Re-added workflowInfo as withWorkflowInfo for writing graph and xml workflow
** [DK] batch mode should be outputting to files or stdout, shouldn't always trigger SpreadsheetMode
** execute flag, maybe make execution the default and allow a "--no-execute" if you only want to capture graphs, for example

=== May 27, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] API question
** http://lists.vistrails.org/pipermail/vistrails-users/2015-May/000357.html
* Status of DAT
** Can add VCS plot to DAT but need to work on configuration windows
** Documentation for graphics templates for UV-CDAT/vcs?
* Qt support?

=== May 20, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Reviving the DAT, integrating scripting & porting UV-CDAT!
** On [https://github.com/VisTrails/DAT GitHub] ([https://github.com/VisTrails/DAT/issues issues])
** Merging 2 years of development taking longer than expected, but getting there. The plan is to get the patches in VisTrails and never fork again, we never want to get in UV-CDAT's situation (and don't need to).
** VTK cell works fine on Linux but there was flickering on Mac & Windows before; still issues on Mac (Windows status unknown)
** Can get a VCS plot soon (but will need VTK cell fix)
** Integrate in UV-CDAT's build system (so we have cdms, VCS, ...) -> RR can do this, low priority
** How do we integrate scripting?
*** We want to be able to seamlessly make changes to a plot by changing Python code
*** Define new plots by entering Python code without writing modules/packages?
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 13, 2015 ===
'''Updates'''
* [RR] Test skipping whitelist ([https://github.com/VisTrails/VisTrails/pull/1069 #1069]) -- low priority
* [RR] Custom matplotlib modules can't be compatible with both 2.1 and 2.2 ([https://github.com/VisTrails/VisTrails/issues/1067 #1067]); should be fixed for ALPS ([https://github.com/VisTrails/VisTrails/issues/1070 #1070])

'''Items to Discuss'''
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 7, 2015 ===
'''Updates'''
* [RR] Export/import workflow to Python working!

'''Items to Discuss'''
* [Claudio] UV-CDAT
** The UV-CDAT project is the biggest user base of VisTrails
** VisTrails package management provides a lot of friction towards people plugging in their code
** Need to make it easy to integrate your random Python scripts in the system without having to deal with all the boilerplate, at least in the first step
** [RR] argues that modules are still good; UV-CDAT shouldn't move towards a purely script-based backend
** [RR] export/import with Python could reduce a lot of that friction by allowing 1) to edit workflow as Python 2) to open up boxes automatically if needed code doesn't match actual modules
** ...

=== April 29, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] <strike>Abstractions</strike> subworkflows status ([https://github.com/VisTrails/VisTrails/labels/subworkflows tickets])
* [RR] matplotlib compatibility (2.1 & 2.2), [https://github.com/VisTrails/VisTrails/issues/1067 #1067]
** RR to try and fix ALPS matplotlib modules

=== April 22, 2015 ===
'''Updates'''
* 2.2.0 has been released!
* Windows issue (via email from Ryan)
** issue with manifest file (may be a new file in VTK6?)
** Tommy has regenerated new Windows builds
* Binaries, pypi, and conda released
* [RR] Export as script
* Python sources using VTK need to switch to SetInputData (users should be aware of this)

=== April 15, 2015 ===
'''Updates'''
* Ready for 2.2.0 (apart from binary/deps issues)
** Missing some libs (scikit-learn, tej, tdparser, SQLAlchemy+connectors
** Windows: runvistrails.py is no longer used, so the PATH is wrong
** Windows: pip is broken, but it probably wouldn't work anyway because of permission issues (disable this?)
* Queries, upgrades and getPipeline() usage ([https://github.com/VisTrails/VisTrails/issues/1054 #1054])
** Getting a pipeline with getPipeline() is not safe: it might return an invalid pipeline
** This is used in many places throughout the code, like queries
** Upgrading would require going through the controller, but that creates new actions
* [TC] Avoid copying a module's output if it's used as input by exactly one downstream module ([https://github.com/VisTrails/VisTrails/issues/1060 #1060]) (useful for big numpy arrays you can update in-place)

=== April 8, 2015 ===
'''Updates'''
* [DK] Merged RR's changes for output modules (1012 and 1013)
** RR will merge remaining changes, then create v2.2 branch!

'''Items to Discuss'''
* BNL need numpy array to VTK image
** Looks like VTK has some helpers for this
** We will help if issues arise
** Will contribute back to VisTrails package
* Upgrade issue: [https://github.com/VisTrails/VisTrails/issues/1017 #1017]
** Automatic upgrades should happen between versions of provided upgrades
** Our existing upgrades work around this so it doesn't need to be 2.2.0
* Corner-case VTK modules
** No longer need VTKCell input port, so don't interfere with registry and API anymore
** Still work weirdly, people probably shouldn't use them
** But we have lots of clunky modules since we wrap the whole of VTK; some people might rely on this and know how to use them, let's keep them anyway
** Ready for 2.2.0

=== April 1, 2015 ===
'''Updates'''
* [RR] UV-CDAT: bugfixing for 2.2, long-term plans: implement scripting import/export in VisTrails, port to UV-CDAT
* Possibly, try to move to regular VisTrails to use new features

'''Items to Discuss'''
* 2.2 release: nothing much is pending anymore, release next week?
** [TE] vtkExporter classes [https://github.com/VisTrails/VisTrails/issues/1032 #1032]
** [RR] Hiding upgrades in version tree might make it (or might be 2.2.1 so we can test it out) [https://github.com/VisTrails/VisTrails/issues/949 #949]
** Output modules changes to go in
* add note to documentation about order of parameters in VTK
* add issue about exporter upgrades if not already there

=== March 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* 2.2 release
** Checklist on Github: https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist
** Review output modules
** RR has a couple more issues to fix
** Ready to go -- sign app package for OSX? [https://github.com/VisTrails/VisTrails/issues/984 #984] We need access to the Apple Membership team

=== March 18, 2015 ===
'''Updates'''
* [TE] VTK6 works

'''Items to Discuss'''
* [RR] Release v2.1.5 with backported tabledata?
** MTA example needs updated tabledata (for JoinTables)
** Google Maps package still not available
* [RR] Work torward v2.2.0?
** changes:
*** new persistence
*** API changes
*** output module changes (upgrades?), maintain cells but try to upgrade
*** not wrapping stuff
*** VTK6? yes
*** JobSubmission stuff?
*** relabeling for upgrades [https://github.com/VisTrails/VisTrails/issues/949 #949]
** makes sense, needs the tree view code to be updated, check selection
** See [https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist 2.2 checklist]
* Discussion of [https://github.com/VisTrails/VisTrails/issues/1016 #1016]
** plumbing between outputs and output modes, how to define a mode that works for many outputs without writing for each output?

=== March 11, 2015 ===
'''Updates'''
* [RR] persistent_archive done; merge? ([https://github.com/VisTrails/VisTrails/pull/755 #755])
** note about the focus events for widgets
** TE be aware of file_archive for future binaries that include persistent_archive
* [TE] [https://github.com/VisTrails/VisTrails/pull/998 New VTK package] finished

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails? (see last week; decision needed)
** RR email to JF about this
** yes; email sent to Github
* [RR] Switching order of output ports ([https://github.com/VisTrails/VisTrails/pull/1006 #1006])
** added port specs are sorted at a separate spot (Module.*_port_specs properties) than those in the registry (which are sorted in the registry), but those two lists are just combined without respect to sort keys
** need to determine whether the two lists should be merged or remain distinct
** should make sure that order of input ports and output ports makes parallel connections for things with same order
** DK suggests breaking backward compatibility here: workflows still run, can fix easily if a problem in an existing package.
* [RR] Question about output modes ([https://github.com/VisTrails/VisTrails/pull/1007 #1007]), how to integrate in API ([https://github.com/VisTrails/VisTrails/pull/24 #24])
** Should ImageFileMode be removed? ("image" is not a mode, "file" is)
** ImageOutput missing?
** Feel free to change how formats works
* [TE] Test suite segfaults on Fedora 17 virtualbox. Install newer version? (Support ended in 2013)

=== March 4, 2015 ===
'''Updates'''
* [TE] VTK wrapper
** Works on VTK 5.10
** Still need to test VTK 6
** New general wrappers for python functions and classes

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails?
** When [http://i.imgur.com/UTY2qfg.png filing a pull request] from UV-CDAT/VisTrails, VisTrails/VisTrails is selected by default
** People keep forgetting to change the default ([https://github.com/VisTrails/VisTrails/pull/956 #956] [https://github.com/VisTrails/VisTrails/pull/968 #968] [https://github.com/VisTrails/VisTrails/pull/999 #999] [https://github.com/VisTrails/VisTrails/pull/1000 #1000] [https://github.com/VisTrails/VisTrails/pull/1003 #1003] [https://github.com/VisTrails/VisTrails/pull/1004 #1004] [https://github.com/VisTrails/VisTrails/pull/1005 #1005])
** Only way to change that is to not have it marked as a fork of VisTrails/VisTrails
** Github staff [https://gist.github.com/remram44/b364c24ef1e462ce6e2f can make that change for us]; should we do it?
** Juliana: comments on this? visibility vs. convenience/annoyance for developers
* [RR] What about [https://github.com/VisTrails/VisTrails/issues/991 #991]?

=== February 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] vtkviewcell for infovis support, can we unify with VTKCell?
** need to test this
* [TE] vtk wrapping
** Mostly finished
** VTK 5.10 produce incorrect results with old wrapping
*** Old wrapper is based mostly on VTK 4
*** Most vtk_examples affected
*** [http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Replacement_of_SetInput]
*** should be able to upgrade from SetInput to SetInputData (need to drop GetOutput and replace with self ports)
*** can we change vtkInstance to just return self and not wrap things
** terminator example not working under 5.8?
* How does VTK wrapping fit into general wrapping framework?
* [RR] new persistence package

=== February 18, 2015 ===
'''Updates'''
* [RR] New VisTrails API and IPython integration ([https://github.com/VisTrails/VisTrails/pull/24 #24])

'''Items to Discuss'''
* [TE] VTK wrapping
** [https://gist.github.com/rexissimus/16b74693545b5e7c1035 Benchmarking vtk package]
*** Old: 24.7 seconds
*** New: 10.5 seconds (Except first time that adds 8 sec)
**** The parsing that calls is_abstract (that tries to instanciate all vtk classes) is now only run the first time.
**** get_items_from_sigstring takes 2 seconds, maybe we can use a lookup dict for already computed sigstrings?
** Now using a general python function wrapper
*** VTK classes are wrapped into python function that does not depend on vistrails
*** VTK functions can be executed without vistrails
*** The spec maps functions into vistrails modules, but can also describe wrapping
*** A general python function wrapper that supports
**** kwarg inputs
**** single, list, dict outputs
**** callback for progress reporting
**** temporary file generator for using FilePool
**** optional output generation
*** Creating specs:
***** Create spec by hand
***** Auto-create spec outline (TODO) and manually finish it
***** Dynamically create spec (VTK)
***** Implement documentation wrappers (Can use scikitlearn wrapper to wrap numpydoc) (TODO)
***** Classes as bad functions needs to be wrapped in new functions before they are wrapped. This is different for each package.
****** Classes is hard: Like VTK, and matplotlib. Scikit-learn does still not wrap classes
***** Spec diffing and patching could be done using code from matplotlib.
** Still needs upgrades from old VTK package
*** Is it possible to dynamically wrap functions, e.g, you see a SetFunc and just remove the 'Set' prefix. Or do you need to create a complete mapping?

=== February 11, 2015 ===
'''Updates'''
* Update from Friday's meeting
** discussed VisTrails internals
** discussed wrapping
*** xml discussion, hard to modify because tied to db code
*** TE has made it possible to add the schema-defined attributes to the intermediate representation
*** higher-level operations on the port specs
** make sure the simple case works
*** [JF] take a simple package with documentation and figure out what the base case for wrapping is

'''Items to Discuss'''
* [TE] VTK wrapping
** Dynamic loading works
** Reading XML is fast enough, but [https://gist.github.com/rexissimus/8272d3c776ccfa115d82 unserializing data is slow]
** Working on patterns for patching
** Matplotlib has many advanced patterns like argument ordering, nested arguments, alternateSpecs, output types.
*** Having all this in a general wrapper might confuse users?
** [RR] Delay module (except for identifiers) until you need it---e.g. don't deal with port specs, etc. until necessary
* Scripting Support [https://github.com/VisTrails/VisTrails/pull/950 #950]
** [RR] Issue with getting code from modules
** Design a simple solution
** [JF] Couldn't you use modules as black boxes without conversion, just to call into modules/subworkflows easily from e.g. IPython?
*** [RR] This is a job for the API, and a very separate use case. See [https://github.com/VisTrails/VisTrails/pull/24 #24]

=== February 4, 2015 ===
'''Updates'''

'''Items to Discuss'''
* Wrapping
** Format to use? Currently XML (like current matplotlib)
*** JSON and YAML have simple "to python dictionary" methods
*** But don't stream
*** YAML a lot easier for humans
** [DK] vtk-new-package also changes parameter names, creates enumerations
*** intermediate schema needs to be extensible
*** packages will want to store there specific infos for compute() method generation
*** also might have specs-altering info, like matplotlib's alternateSpec
** representation to code , registry already has schema for some aspects
** [RR] We might want to see if Module subclasses can be created lazily
*** no need to create all the classes just to register them in the registry and never actually use most of them
*** future effort
* [RR] Where should VisTrails packages live?
** tej installs as 'vistrailspkg.tej', TE installed it as 'userpackages.tej'
** Currently, standard packages are 'vistrails.packages.', user packages are 'userpackages.' and packages loaded through pkg_resources might be anything
** [RR] Use 'vistrailspkg.' everywhere?
** Long-term effort to simplify package distribution/installation (and have VisTrails get them automatically?)

=== January 28, 2015 ===
'''Updates'''
* T. Caswell to come visit on Fri 6 to discuss wrapping work

'''Items to Discuss'''
* [TE] New VTK wrapping
** Current code by DK seems a good deal faster
** Generates XML that can be patched/tweaked, generates Python code from it, VisTrails only loads generated Python code
** RR would rather have VisTrails load intermediate representation (= XML) directly, wants to make sure this is not slower
** The goal is to turn the intermediate step into something generic that would be used for every wrapped package (vtk, numpy, matplotlib, sklearn, java) instead of each having its own
** TC has its own code at [https://github.com/Nikea/VTTools/blob/master/vttools/wrap_lib.py github:VTTools] which parses numpy docstrings and generates modules, doesn't yet handle classes or persist anything
* Web crawler
** Right now, TE starts jobs for "start crawler", "stop crawler", "install classifier"
** RR would rather have the crawling be a job as far as VisTrails and tej are concerned
** The whole thing would be one pipeline: load examples, train classifier, start crawler [check for job, kill previous one, upload model, start processes], get snapshot, visualize
*** Need some support in tej and job submission system: long-running jobs, stop a job (wait for it to finish?), restart a job even though results are cached

=== January 21, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Unified wrapping method discussion [https://github.com/VisTrails/VisTrails/issues/991 #991]
** TE to work on reusable method with intermediate representation, starting with VTK
* [RR] Examples for scikit-learn: JF has an old example using Weka with parameter exploration (not currently in source tree)
** AM's examples are enough
* [AM] scikit-learn package is done, merge it in? [https://github.com/VisTrails/VisTrails/pull/955#issuecomment-70286788 #955]
** RR will merge
* [RR] What should copyright headers say? [https://github.com/VisTrails/VisTrails/pull/994#issuecomment-70173935 #994]
** Let's keep everything in there: Utah/Poly/NYU

=== January 14, 2015 ===
'''Updates'''
* [TE] Working on classifier
* [RR] Scripting integration, work in progress

'''Items to Discuss'''
* [RR] Unified wrapping method discussion ([https://github.com/VisTrails/VisTrails/issues/991 #991])
** Let's talk next week, [AM] and [DK] are not here

=== January 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* make sure that we address critical issues, questions, and pending review branches in a timely manner
* scripting support
** [RR] no issues if we want to just keep annotations in the generated code to allow the link back to a workflow
** [RR] can translate from workflow to script, working on script to workflow
** will work for parameter value changes, structural changes require changes to the annotations
** need to publish best practices here
** would be cool to do looping in scripts (easier interface than with workflows)
* notebook support (convert form notebook to workflow)
** RR will sync with FC on this
* Issue with console in built-from-scratch
** [TC] iPython rearranged some of the completion stuff in 2.2 and 2.3
** binary has old version of iPython -> 1.0.0, should we update?
* [TC] automated wrapping of numpy and scipy
** discovered a bunch of malformed documentation in numpy and scipy
** has github repo for vistrails tools
** example modules wrap a bunch of R stuff (not baked in, just how things are)
** will be pushing wrapping logic up
** port names forbidden (window and domain)
** have an import hook to get from yaml directly to VisTrails Modules
** should work for any python modules with well-formed numpy docstrings.
* [Action] should make it clear in documentation that Constant now means serializable not that the value doesn't change (e.g. List)
* [TC] might be interesting to try to build components of matplotlib and accumulate in figure (long-term project, but thinking about how this might work)
* [TE] build and build scripts
** completely automatic, buildbot
** need to set the build machines for the environment we want for the binary
** would virtualenv work here?
** [TC] anaconda can pin versions, potential path to test different configurations
** Q: upload nightly binary builds? A: makes sense, make sure they are well-labeled
* sourceforge stats: e.g. http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07
* package issues (see Remi's message)
* [TE] Scope of tej
** Support single ssh commands?
** Queue can be used as a remote machine (crawler is using queue.call*)
* SourceForge stats: http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07

== Older meetings ==
* [[Development/2014]]
* [[Development/2013]]
* [[Development/2012]]
* [[Development/2011]]
* [[Development/2010]]

Development

2016-06-15T14:54:16Z

Tommy: /* June 1, 2016 */

<div class="nonumtoc toclimit-1">
__TOC__
</div>

See also the [https://github.com/VisTrails/VisTrails/wiki/Development Github wiki]

== 2016 ==

=== June 15, 2016 ===

'''Updates'''
* [TE] Added depth logic to python script exporter ([https://github.com/VisTrails/VisTrails/commit/50f220e4f6abe5a7bb8689f73f456f43df2dbc12 full commit])
** Fully implements connection merging and list looping

'''Items to Discuss'''

* [TE] Making analogy work on upgraded workflows ([https://github.com/VisTrails/VisTrails/issues/1175 #1175])
** Analogy only works We need to use the non-upgraded action chain
** But pipelines need to be valid (matcher uses module portspecs)
** Tried to get upgrade remap from upgrade action, but this seems impossible
** Use module location instead?
*** Location should be identical for one-to-one module upgrades

=== June 1, 2016 ===

'''Updates'''
* VisTrails 2.2.4 announced (finally)
** 5 survey replies
** 47 downloads last week

'''Items to Discuss'''
* [TE] Export VTK as script (python-wrapper)
** to_python_script
*** needs the pipeline (or at least the connections)
**** Should not generate code for any possible VTK method (exporter detects which ports is used in the source)
**** VTK needs to know connection order
**** Adding functions directly to the script results in nicer code
** Add support for multiple input connections
** Add support for list looping

=== May 25, 2016 ===

'''Updates'''
* Mailing-list fixed
* Getting stats from the "server news" mechanism (via [https://github.com/remram44/apache-log-info parser])

'''Items to Discuss'''
* [RR] Alexis doing writeup on VisTrails, curious about interesting streaming use-cases (and potential future users)
* [TE] Union ports
** Show union ports in pipeline (DEMO)

=== May 18, 2016 ===

'''Items to Discuss'''
* [TE] mailing list still down - Julio working on it
* [TE] Improved union port
** New schema 1.0.5 adds portitem.union string attribute
** Works with pipeline view, parameter exploration view, and mashup view
** Should work well for matplotlib
** Use with VTK ports?
*** It uses [item_1,item_2] style ports usually with different tuple length.
* [TE] Remove emacs dependency from db generate [https://github.com/VisTrails/VisTrails/issues/1173 #1173]

=== May 11, 2016 ===

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]
** GUI-based solution [https://github.com/VisTrails/VisTrails/tree/union-port Branch union-port] Demo?
*** Shows single port for all ports with same sort_key
*** Select specific type when adding/showing
*** Only one type should be visible on the module at any time
*** Making tuple parameters union types is probably too complicated
*** Should work with alternate specs like matplotlib (if sort_key is defined correctly)

* [TE] Feature suggestion: Let connections connect to functions/parameters
** Show functions and parameters as ports and toggle port visibility directly for functions and parameters
** Use separate views for ports and functions (like before)
*** Allow rearranging of functions
** Pros:
*** Supports ordered connections. Create 2 functions, make them visible as ports, make connections to them.
**** We can also have, e.g., a line joining the ports on the module to indicate they are part of a list.
**** Makes List module simpler
*** Connect to parameter in tuple
*** Functions that are visible on the module can connect to an actual function, and not just to the first one it finds.
*** Can replace operation modules (in python-wrapper) in some cases for, e.g., numpy.
** Cons:
*** Interface more complicated and crowded
*** More difficult for users to grasp?
*** No immediate use case
*** Makes no union type for tuple parameters a bigger problem.

* [TE] Publish user survey?
** No response from vistrails release yet
** Not announced on vistrails-users yet.

=== May 4, 2016 ===
'''Updates'''
* VisTrails 2.2.4 released

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]

=== April 27, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Wrapping Bokeh
** New method type "operation"
*** Transforms Figure->Glyph->Output into Glyph->Figure->Output
**** Glyph sets function name and arguments as output
***** Not serializable, but should always be computed together with the subject of the operation.
**** Figure applies Glyph operation on itself
*** Useful for matplotlib?
**** matplotlib currently find actors by searching upstream?
**** But this is more difficult since matplotlib is not function-based.
** New "union" port type
*** Turns "x(float), x(list)" into "x (float, list)" and uses first set value
**** Uses only first value in tuple
**** Bokeh have many properties that support (list, string, Float)
*** Does not work with depth=1 types (e.g. Float of depth 1)
**** Turn Depth 1 types with known type into lists?

* [TE] New bugfix release
** Finalize survey

=== April 20, 2016 ===
'''Updates'''
* Merged upgrade fixes
** Now has infinite loop test
** loop test now correctly loops 5 times
*** remap_module used wrong (current) package version when creating ModuleDescriptor
* Fixed multi-step group upgrades (PR: [https://github.com/VisTrails/VisTrails/issues/1168 #1168])

'''Items to Discuss'''
* New bugfix release
** Merge usagestats
** Need to finalize survey

=== April 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Chaining upgrades done ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Replace "Upgrade" description annotation with "upgraded_from" annotation to identify which tags to hide?

* [TE] Iterating handle_invalid_pipeline ([https://github.com/VisTrails/VisTrails/pull/1165 #1165])
** Not based on [https://github.com/VisTrails/VisTrails/tree/chain-upgrades-loop chain-upgrades-loop]
** Cherry-pick test to preserve source?
** Need maxPipelineFixAttempts option?
*** The code is now smarter about recursion, so max attempts will "probably" never be reached.
** Need [https://github.com/VisTrails/VisTrails/commit/0ef0667426937eddb1d1c1e397f0657ffec039a9 debug messages]?
*** Would need to be moved into handle_invalid_pipeline

=== April 6, 2016 ===
'''Updates'''
* [TE] Query View improvements
** Done except for displaying "Version Info" and #1164
* [RR] Working on finishing new interpreter (finally!)

'''Items to Discuss'''
* [TE] Chaining upgrades ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Try latest upgrade first, then previous.
** If all fail, select latest upgrade?

=== March 30, 2016 ===
'''Updates'''

'''Items to Discuss'''

* [TE] Query View improvements
** Unified do_version_switch and get_upgrades as validate_version()
** Problems with query view using its own controller
*** Fixed module info not being displayed for query results
*** Still no version info for query results
*** Still an issue with version query view not being updated

=== March 23, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Usage reporting almost ready to go
** Need to record whether specific features are used: paramexpore, mashup, query
*** [DK] Record if LaTeX extension is used? But hard to distinguish from direct batch invocation
** How to record size of vistrail?
*** [DK] IdScope already walks over vistrail, use that
*** but total number of modules and versions doesn't give an idea of average size of individual pipelines

=== March 16, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Upgrades in Query Mode
** Now using code similar to do_version_switch
*** Uses handle_invalid_pipeline
*** Differences: Not using current_pipeline, flushes changes
*** New controller method get_pipeline optimized using cached pipelines (but not current_pipeline)
*** Integrate to avoid repeated code?
*** Use this for query mode?
* [TE] VisTrails 2.2.4 ready for release?
** tej package updated. Others?
* [JF] upgrades and the version tree
* [JF] provenance in Jupyter
* [DK] bundles: [https://github.com/VisTrails/VisTrails/pull/1092 #1092]

=== March 9, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixing search mode
** String query now matches all by default
*** This caused pipeline queries to never match
** String query can search: User/Notes/Tagname/Time/Module name
*** Should we search module names by default? (Disabled by default because it is expensive)
*** Fixed notes search
** '>' parameter queries in documentation but has been removed
** Fixed module matches for upgraded pipelines (By not upgrading pipeline)
*** Upgrades still a problem
*** Add "Upgrade all menu option?" (Or upgrade all on open when `hideUpgrades`)
*** [JF] Allow search on past tags

* [TE] Create new bugfix release
** Finish querying
** Path issue on windows

* [DK] Look into sqlalchemy and new bundle branches

=== March 2, 2016 ===
'''Updates'''
* [TE] Fixed cache bug with port specs
* [TE] VisTrails Next
** Most packages now work
** No qgis for Python 3

'''Items to Discuss'''
** Always dereference symlinks? [https://github.com/VisTrails/VisTrails/issues/1146 #1146]

=== February 23, 2016 ===
'''Updates'''
* [TE] Fixed PythonSource 100% CPU bug
* [TE] VisTrails Next
** Updated [http://opendap.co-ops.nos.noaa.gov/axis/webservices/wind/ NOAA Web Service] examples
*** Now uses REST service, tabledata, and Google Maps
*** Web Service replaced with DownloadFile

'''Items to Discuss'''
* [RR] Couple of fixes are in for API, and tej&reprounzip on the Mac binary. Also new release of tej, and working on anonymous usage reports.
** New 2.2 release soon?
* [RR] Anonymous usage reports
** Sends out info like number of modules & versions, packages used, Python & libs versions, execution time, specific features [https://github.com/VisTrails/VisTrails/pull/1154 #1154]
* [JF] Bring in noWorkflow to track variable dependencies, for the considered Jupyter integration?
* noWorkflow - provenance for python scripts
** Recent work on tracking dependencies
* Also integrates ReproZip with Jupyter
** [http://mybinder.org mybinder]
*** Use with ReproZip to automatically build Jupyter notebook interfaces
* Daves comments on Jupyter integration
** It is possible to identify cell order on the server side
** Not trivial to track order of cells on client side
* How does Galaxy workflows relate to VisTrails?
** Packaging in Galaxy is hard
** Galaxy for biomedical workflows, difficulty making it general
* Action items
** How difficult to track cell dependencies in Jupyter notebooks?
** Use noWorkflow to track cell dependencies?
** How difficult to modify mybinder to use ReproZip packages?

=== February 17, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixed Group memory usage
** Modules in groups are supposed to be freed when done executing
*** Prevented by logger that stored references to the modules (fixed, now using id(module))
*** Prevented by list iterator bug that stored list of modules on the 'self' port bug (fixed)
* [TE] VisTrails Next
** Removed deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** PythonSources will be upgraded
*** Fixes for Python < 3
*** fixes for VTK < 6
** TODOs
*** Remove RemoteQ
**** Port Hadoop to tej (Already have pbs)
*** Merge package wrapper
*** Finish SQLAlchemy branch
*** Finish new bundle branch
** [JF] Will contact Jeff and Matthias about moving to Python 3
* [JF] Query by Example is broken
* [JF] VisTrails Data Cleaning Project
** Use VisTrails to process and explore task-specific data while keeping provenance.
** Remi's Idea
*** Use VisTrails as the backend in a Jupyter notebook
*** Overcome problems with executing cells in random order
**** Interesting research topic, but little interest has yet been noted
*** Interesting to study how such a notebook would be used (Is there notebook usage data available?)
*** Impose restrictions to notebook cell boundaries
*** It will only work for functional operations
*** Can we fix, or detect, non-functional (mutating) operations?
*** Analyse code and data flow and see if it mutates data in unexpected ways?
*** Mutable operations can be created in many ways in Python
* Next meeting Tuesday 11:30

=== February 10, 2016 ===
'''Updates'''

'''Items to Discuss'''
* VisTrails Next
** Test suite passes
*** Python 3 less deterministic, module upgrade order random.
** [RR] updating packages: Reprounzip (pushed), tej, persistent_archive, ...
** All of our packages should run fine :)
** VTK thumbnail comparison works
*** Rendering bug on some systems
**** QVTKCell now inherits QGLWidget
*** Old thumbnails had wrong height due to spreadsheetwindow being too small
**** Fixed by regenerating thumbnails
*** Silenced deprecation messages when generating modules
*** Many new classes in VTK 7
** Remove deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** Will break existing PythonSources
**** Try to upgrade?
*** Old-style packages
**** Or only allow a new style, like __init__.py renamed to info.py? (merge with identifiers.py?)
***** Read info.py without importing package?
*** Fixes for Python < 3
*** Fixes for Qt < 5
*** fixes for VTK < 7
*** Remove self port?

=== February 3, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] [http://lists.vistrails.org/pipermail/vistrails-users/2016-January/000402.html Rendering a .pvd (ParaView) file?]

* VisTrails Next
** All tests but thumbnail comparison passes
** Still issues with gui and more packages needs to be tested
** PythonSource and MplSource upgraded with lib2to3
** Keep contrib packages? Update?
** [https://blog.kitware.com/vtk-7-0-0/ VTK 7 is released]
*** Supports Python 3
*** Will hopefully get into conda and others soon
*** Deprecates a bunch of modules

* [https://travis-ci.org/VisTrails/VisTrails/builds/106743348 Travis builder] for VisTrails Next
** Runs!
** Uses conda
*** Many levels of requirements
**** apt packages
**** conda packages
**** python packages in requirements.txt
**** python packages in setup.py
*** Can probably drop conda. Default builder does not have Qt5, but beta builder do!
*** But useful if we want to use conda in our own build process.
** Lots of errors I do not get locally?

* [http://goo.gl/forms/Z4HBrwaBWL User Survey]
** Have you used any alternatives to vistrails?
*** Relevant? More options?
** How often do you use any of these particular features in VisTrails?
*** Add/Remove alternatives?
** How important would you rank the following potential improvements to VisTrails?
*** Add alternatives?

=== January 27, 2016 ===
'''Updates'''
* New interpreter
** Working prototype soon
** Looping not completely done (and port combination mode: pairwise/cartesian...)
** Need to integrate with VisTrails
*** Compatibility with existing modules
*** Use log controller
*** Want to cache at multiple levels (whole stream/single element of stream)
*** Non-runtime attributes of modules (cache check, automatic conversion check, constant from/to string)

'''Items to Discuss'''
* User Survey

* ZMQ failing on windows (vistrails-users)

* [TE] [https://github.com/VisTrails/VisTrails/pull/1143 Python 3 branch]
** Testsuite almost passes
*** Failing are unicode filenames, some users guide examples, and thumbnail comparisons.
** Fixed issues
*** Signatures are now bytes (convert to string to show in widget)
*** Cannot compare different types, e.g., (None < 1)
**** PortSpec.depth and min/maxConn could be None. (Backport!)
**** cell.row could be None
*** Lots of unicode/bytes fixes to serializations
**** We have encryption implementations in the code! (keychain)
*** Lots of small fixes to package method differences
** Current issues
*** logging widget empty?
*** version tree signals messed up
*** provenance view legend icons black
*** Text do not fit in some widgets
*** VTK thumbnail comparison fails
**** VTK Cells have some faces in wrong direction?
**** Because running in VM?
** Installing on Ubuntu LTS/Latest Mint
*** Install latest matplotlib from pip
*** Install VTK 7.0.0rc2 from source
*** No QtWebEngine binary (controversial) (Must install sip/PyQt5/Qt5 from source)

=== January 20, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Backporting features from Python 3 + PyQt5 + Qt5
** Merged unicode with master ([https://github.com/VisTrails/VisTrails/tree/unicode unicode])
*** One unicode test failing
*** Problem saving to xml
** Used [http://python-future.org/ python-future] to run futurize stage 1 to update legacy (pre 2.6) code ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized unicode-futurized])
*** Updates print to functions 'from __future__ import print_function'
*** Updates exception calls to use 'as'
*** removes most usages of 'long' (mostly used unnecessarily)
**** Only needed for 32-bit support
*** Fixes relative imports (from __future__ import absolute_import)
** Fixing code that is deprecated in Qt 4.8 and removed in Qt 5 ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized-qt5 unicode-futurized-qt5])
*** Updated all signals to new-style
* If we go 2 to 3, this could break packages
** means we should schedule any package format changes for the same time
** e.g., imports should be unrelated to code path (function to load module from package identifier?) (take them out of vistrails.* [https://github.com/VisTrails/VisTrails/pull/1002 #1002])
** any structural changes (e.g. the __init__ versus init thing) (RR thinks it makes sense, though having both named "init" is unfortunate)
** putting package identifier as xml?
*** Python not so bad, plus some stuff in there is Python code (checking dependencies)
** version the APIs?
*** RR planning on versioning vistrails_module.Module, no point versioning the whole package?
* file formats on 2 to 3:
** no real translation/upgrade, but non-ascii values that work on 3 won't load in 2

=== January 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://gist.github.com/rexissimus/dfd27e466427529c385c Porting to Python 3 / PyQt5]
** Basic GUI and execution works
** Minimal work to support 2to3
** Hard to support both PyQt4 and PyQt5

=== January 6, 2016 ===
'''Updates'''
'''Items to Discuss'''
* Updating VisTrails dependencies
** Successfully built [https://gist.github.com/rexissimus/f1a1aada7de1c00a57c7 Win7-64/Python3/PyQt5/Qt5/WebEngine/VTK7]
*** VTK 7 is the first supporting Python 3 but is only in release candidate phase.
**** Next version of VTK 6 is rumored to support Python 3
**** There is a development branch of VTK 6 supporting Python 3
*** Can travis build this?
**** We can skip tests for WebEngine and VTK if needed
** Python 3 [https://python3wos.appspot.com/ showstoppers]
*** No MySQL-python (sqlalchemy supports mysql through other drivers)
*** No suds (there are active forks but we could also drop support?)
* Options for python2/3 support:
** Interpreter could be python2/python3 based on packages
** six layer works but not the easiest to maintain (e.g. in reprozip)
* Drop support for win-64
* Update copyright headers to 2016

== 2015 ==

=== December 30, 2015 ===
'''Updates'''
* Bokeh package finished
** Can output to Browser/IPython/Spreadsheet (Limited functionality in spreadsheet)
'''Items to Discuss'''
* Updating VisTrails dependencies
** Bokeh needs QWebEngine (Chromium) in Qt5 which requires PyQt5
*** Many plotting libraries only work in browsers
*** But Chromium may be a big and controversial dependency
*** Or create a browser version of the spreadsheet?
** Some users have requested Python 3
** Not backwards compatible?
** Target for VisTrails 3.0 with new interpreter?

=== December 16, 2015 ===
'''Updates'''
'''Items to Discuss'''
* Users list question
* [TE] Wrapping Bokeh
** Added bokeh property parser
*** complements numpydoc parser
*** Not all attributes are available, partially because I am using a pre-release version.
** Wrapped modules
*** bokeh.plotting finished (Backwards like matplotlib: Create plot then draw on it)
*** bokeh.charts mostly done (Missing arguments)
** QWebView mostly works (but no zooming or buttons)
*** It would be better to use external browser or QWebEngineView
** Added improvements to wrapper
*** Generalized port translations (Color/Path to native types)
*** Can use multiple docstring/property parsers simultaneously

=== December 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Looking into wrapper
** Will port TensorFlow
** Doing a pass on the wrapper code & doc
*** UX improvements
** Factorize high-level docstring parsers into core.wrapper? (sphinx, numpy, google)
** Problem with name vs module_name (fails sklearn tests because class_by_name() is broken)
** Looking into compressing specs, lazy registration of modules

=== December 2, 2015 ===
'''Updates'''
* [TE] Package wrapping
** Wrapped most of numpy/scipy using __all__
** Added class attribute and method access for classes (Can add to class or to separate inspector module)
** TODO: Document wrapping procedure

'''Items to Discuss'''

=== November 25, 2015 ===
'''Updates'''
* [RR] New interpreter is coming along
** Everything is a stream
** Task system, eventually work-stealing parallelism
** Streams no longer advance in lock-step
*** Allows for constructions like filter, join, sorted-merge
** depth>1 still to be tested, no current plan to allow this through the module interface
*** Through looping though, can do streams of streams

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapped most numpy functions (no polynomials)
** and half of scipy classes and functions
** Added functions manually from documentation (no parseable lists?)
** Focusing on data flow constructs (no property/method access for classes)
*** Using spec diff (empty for now) and dynamic parser (stores spec in .vistrails/)
** Python class/function wrapper now stable
** Add google doc parser?
*** Is there a parser available?

=== November 18, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Numpy class wrapping works
*** Basic type is List, since most types are array_likes.
*** TODO: More classes and functions
*** Some operations are in-place and some aren't, and docstring not super clear
*** [RR] It seems only methods mutate, and most have a numpy.xx function equivalent; just manually go through the methods and remove the mutating ones?
** Class wrapper is modular
*** Docstring parser and type string parser can be customized
*** Classes can have optional attribute/method ports
**** Inspectors and attribute/method modules can be created separately
** Use PythonCalc as an example
*** Can be re-implemented as a function with a parseable docstring
*** [RR] PythonCalc is just an example, and it might actually make sense to get rid of it, or do a proper math package with scalar operations (as separate modules, no combobox)
** [RR] TensorFlow to use wrapping as well
*** Very simple (only types 'tensor' & 'variable')

=== November 11, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapping numpy's classes using numpydoc (ndarray)
*** Wrapping constructor arguments, attribute getters/setters as module ports
**** Then how to access attributes afterwards?
***** Use input value port to class modules?
*** Wrap methods as modules? E.g., `ndarray.shape`.
*** Function wrapping is almost a subset of class wrapping
**** May be able to use the same parsing/execution methods
** VTK's non-getter/setter methods could be wrapped as modules
*** We could then remove extra logic in interpreter for keeping function order
** Bokeh uses autogenerated docstrings
*** We may be able to read the specification directly

* [RR] [https://github.com/VisTrails/VisTrails/pull/1138 TensorFlow package]
** Basic setup working, can execute the Mandelbrot example
** Will autogenerate the operations

=== November 4, 2015 ===
'''Updates'''
* [RR] Interpreter work requires a fix for [https://github.com/VisTrails/VisTrails/issues/1137 DB issue #1137]
* [DK] Kitware's Resonant [http://www.kitware.com/source/home/post/173]
** [https://github.com/girder/girder Girder]: data management system
** [https://github.com/Kitware/romanesco Romanesco]: execution engine, uses [http://www.celeryproject.org/ Celery] for task management
** Resonant Flow: web app for editing and executing workflows

'''Items to Discuss'''
* [TE] Added OSX Lion (10.7) VM on build machine using vagrant (seems ok with license?)
** New builds works on Lion
** Change the minimum requirement to 10.7?
* [TE] Package wrapping
* Added upgrade suggestions using 2 spec versions ([http://pastebin.com/30XUU8Gp example])
** using name edit distance to find matches
** Could use something better like port similarity for modules, and type similarity for ports
** Should write python upgrade code?
** Added spec to sklearn package
*** Can now diff spec versions and keep the spec static
*** There will be problems with downgrades and package versions

=== October 29, 2015 ===
'''Updates'''
* [TE] nightly-build-mac fixed (Needed to approve xcode license)

'''Items to Discuss'''
* [TE] matplotlib wrapper
** ported to general spec
** Diff can be used on general spec
*** Only needed minor changes
*** Fixed indexing bug that corrupted specs
*** Can now move diff tools to core/wrapper
** Add new plots?
*** New plots in mpl 1.3: eventplot
*** New plots in mpl 1.4: angle_spectrum, magnitude_spectrum, phase_spectrum', violinplot
*** No new plots in mpl 1.5 (from looking at boilerplate.py)

=== October 21, 2015 ===
'''Updates'''
* [RR] Alexis has arrived, will be working with [RR] on a more efficient interpreter

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package]
** Supporting multiple package versions
*** Check which version can be loaded [https://github.com/VisTrails/VisTrails/pull/1135 #1135]
*** We cannot show version requirements in the list of packages because old packages are loaded when importing the codepath
** Visual diff does not work well, but we can use the spec differ to see differences.
** Unifying vtk and matplotlib wrapping specs (WIP)
*** And porting matplotlibs spec differ to work on the general spec
*** Spec differ can then be used on vtk and other packages in the future
*** Will enable automatic upgrade generation
* [RR] Rework interpreter
** restore abstraction between interpreter/module code
** build looping, streaming, caching into the interpreter
** rework cache
** look into parallelism once basic functionality is there

=== October 14, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package] (adding numpydoc parser)

=== October 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/tree/fix-matplotlib-parser New matplotlib parser] (adding numpydoc parser)
** Added numpydoc attribute parser for plots.
*** TODO: Need better port spec reconciliation with call signature parser.
*** We can create a general numpydoc parser, but attribute types are unique to matplotlib.
** Needs package versioning
*** New spec will not support matplotlib < v1.4 due to changed path to axes classes.
*** Load spec version corresponding to installed matplotlib version?
*** Need version downgrades?

=== September 30, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Updating Matplotlib parser
** Matplotlib docstring parser fails on numpy docstrings
** I have [https://github.com/VisTrails/VisTrails/commit/eae8b0c16260810587e47c41cab53552cbb3cf0a added basic numpydoc parsing]
*** Only used by a few docstrings so far
*** Parsing uses many sources (class tables, signatures, ACCEPTS, method docstrings, definition parsing).
** Caswell said they were thinking about moving to traitlets, but this is not ready yet

=== September 23, 2015 ===
'''Updates'''
* [TE] VisTrails 2.2.3 released
** Also have pushed to PyPI, binstar, etc.
** Sourceforge vs. GitHub
*** should be able to host releases on GitHub
*** nightly binaries pushed to sf each night
*** old binaries?
* [TE] Re-wrapping MatPlotlib
** Keep static generation - Docstrings are brittle beween matplotlib versions
** Keep generating the executable classes - but create functions, not vistrails Modules
*** Why is there so much patching?
** Re-implemented Alternate PortSpec for InputPortSpec
*** It will now inherit specs from parent (No need to reimplement)
** Module upgrades?

'''Items to Discuss'''

=== September 16, 2015 ===
'''Updates'''
* [TE] Job Monitor tests and documentation done
** OK to leave document package in packages directory?

'''Items to Discuss'''
* [TE] Library wrapping: How to do code patching? [https://docs.google.com/drawings/d/1Sh3eOXot6v2y880jHKQrqXqAwr-0aoqYligg3z8G8MY/edit?usp=sharing Wrapping diagram]
** Insert code into module template (Old VTK code)
** Patch the library that is called (New VTK code)
** Somehow store code in spec and apply when executed?
*** Executed code needs at a minimum access to inputs, outputs, current class
*** Use standard input/output dict and obj reference that the code operates on?
*** Can this be done while keeping the execution abstract?

* Do new release now?

=== September 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* New release?
** [RR] wants reprounzip
** tej changes & doc
** job monitor & jobmixin fixes
** mongodb
** reprounzip
** warning: MplFigure type is int
** tabledata: add Reshape, DictoToTable & ListToTable, fix ListToTable with numpy arrays
** PythonSource can have same name for an input & output
** don't show spreadsheet at exit

=== September 2, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Limit autosaves? [https://github.com/VisTrails/VisTrails/pull/1126 #1126]

=== August 26, 2015 ===
'''Updates'''
* [TE] Added Job support to Parameter Explorations (Requested by Colin), and Mashups
** specify job ids, need to specify different ids for parameter explorations since they have the same version id
** how to deal with parameters passed in on command line
* [General] provenance: should be creating a new version when we execute workflow with changed parameters?
** currently, custom_params annotation stores this in provenance currently
** [RR] API doesn't record provenance if passing in parameters: http://git.io/vsAA5
'''Items to Discuss'''

=== August 19, 2015 ===
'''Updates'''
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [TE] Working on Job Monitor documentation

'''Items to Discuss'''
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [TE] Stop testing VisTrails 2.0?

=== August 12, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Build broken on Travis; because of IPython 4 released today? ([https://travis-ci.org/VisTrails/VisTrails/builds/75279795 build 992]; [https://github.com/VisTrails/VisTrails/issues/1123 #1123])

=== August 5, 2015 ===
'''Updates'''
* [TE] Fixes to Jobs
** Could not delete jobs
** Could not run job in group
** Job not reset when calling ModuleSuspended
** Added deleting job from context menu
* [RR] Writing documentation for everything [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

'''Items to Discuss'''

=== July 29, 2015 ===
'''Updates'''
* RR still looking into new interpreter thing
** Goal is to take out scheduling logic from Module so it can be split in multiple processes, and so that smarter strategies can be added in time
** This means some work on packages
** Spreadsheet can live in kernel process? Still some UI stuff that will take work (changing configuration, persistent archive's viewer, ...)
* [TE] Problems running examples [https://github.com/VisTrails/VisTrails/pull/1111 #1111]
** Testing of more examples requires additional packages on the test machines.
** Fixed faulty line-ending in PythonSource:s failing on Python 2.6.
** Test suite now testing SUDSWebServices (If web service is down, test suite will fail)
** preferences.py test failed reloading 'dialogs' package, switched to using 'URL'.

'''Items to Discuss'''

=== July 22, 2015 ===
'''Updates'''
* [TE] mailing lists back online
* [TE] Working on [https://github.com/VisTrails/VisTrails/issues/1107 #1107]
* [RR] Working on ReproZip package

'''Items to Discuss'''
* [RR] MongoDB package [https://github.com/VisTrails/VisTrails/pull/1106 #1106]
* [RR] Example for tej docs? [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

=== July 15, 2015 ===
'''Updates'''
* 2.2.2 released

'''Items to Discuss'''
* RR is considering executing everything in an IPython kernel (i.e. separate Python interpreter, like the one spawned for a notebook)
** It's a separate process that we can restart without restarting the app/gui
** We can isolate the execution environment (e.g. for the server)
** We can run the whole thing remotely (if your data is elsewhere, just run VisTrails locally and the pipeline elsewhere)
** Pipeline execution no longer makes the interface hang, it just makes the kernel hang (but that's fine)
** We can use notebooks as modules (probably way nicer than the PythonSource module)
** We can run multiple kernels so long as the ports carry things that are serializable
*** meaning we can put the multithreaded-interpreter without all the hacky parts it has now
*** we can run IPython kernels in all the languages IPython supports, [https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages currently 46]

=== July 8, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Buildbot github hook not working after IP address change
* [TE] No reference to VistrailsApplication ([https://github.com/VisTrails/VisTrails/issues/1103 #1103])
** [RR] Added PR [https://github.com/VisTrails/VisTrails/pull/1104 #1104]
* [TE] Reopening VT file after saving with bundled subworkflow won't offer subworkflow upgrade ([https://github.com/VisTrails/VisTrails/issues/1102 #1102])
** allow manual delete to fix right now
** fix this on top of the use-uuid branch
* [TE] Release VisTrails 2.2.1? ([https://github.com/VisTrails/VisTrails/blob/v2.2/CHANGELOG CHANGELOG])
** [https://github.com/VisTrails/VisTrails/pull/1093 output-modules-use-global-dir]
** [https://github.com/VisTrails/VisTrails/milestones/version%202.2 Current issues for 2.2]

=== July 1, 2015 ===
'''Updates'''
* [TE] PROV fixed
* [TE] Working on subworkflow issues
* [RR] Considering reworking the controller (log vs exception problem, retained upgrades causing interferences) and also the interpreter (IPython?)

'''Items to Discuss'''

=== June 24, 2015 ===
'''Updates'''

'''Items to Discuss'''
* UV-CDAT
* [TE] Can a cyclic workflow be valid? ([https://github.com/VisTrails/VisTrails/issues/1097 #1097])
** focus on disabling the ability to create cyclic pipelines because more things break than just this with a cyclic pipeline
* [RR] Relative paths ([https://github.com/VisTrails/VisTrails/pull/1057 #1057])
** This interacts with the new bundle; how do handle packing files inside the VT bundle?

=== June 17, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] current_version and reusing existing upgrades are broken ([https://github.com/VisTrails/VisTrails/issues/1095 ticket #1095])
** Could be that export to PROV is using an unflushed upgrade pipeline?
** current_version would then be correct.
** It may work to flush the actions before exporting?

=== June 10, 2015 ===
'''Updates'''
* DAT: fixed VTK issue on Linux and Mac
* Still crashes on Windows. Need help! Reminder: this works in the VisTrails spreadsheet (QCellPresenter), although no widget get changed there during a drag
** Is it a VTK bug?
** Is it simply impossible to change widgets during the drag, should we do it a different way?
** Did I miss something that is done in VisTrails but somehow not in DAT?
** Low prio, UV-CDAT doesn't run on Windows anyway

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 Updated pull request])
* Single instance code and batch mode

=== June 3, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 pr])
** Requires fixes to command line parameters, Output modules, and batch mode
** How to test this
** Updated missing/outdated flags
** Fixed view issues when generating graphs
* [TE] batch mode
** SpreadsheetOutput not enabled in batch mode. Should we check is_running_gui instead?
** Other instance setting flags from caller
** Is graphsAsPdf replacing spreadsheetDumpPdf?
** graphsAsPdf true by Default?
** Batch mode executing by default (Not needed when generating graphs)
** Re-added workflowInfo as withWorkflowInfo for writing graph and xml workflow
** [DK] batch mode should be outputting to files or stdout, shouldn't always trigger SpreadsheetMode
** execute flag, maybe make execution the default and allow a "--no-execute" if you only want to capture graphs, for example

=== May 27, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] API question
** http://lists.vistrails.org/pipermail/vistrails-users/2015-May/000357.html
* Status of DAT
** Can add VCS plot to DAT but need to work on configuration windows
** Documentation for graphics templates for UV-CDAT/vcs?
* Qt support?

=== May 20, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Reviving the DAT, integrating scripting & porting UV-CDAT!
** On [https://github.com/VisTrails/DAT GitHub] ([https://github.com/VisTrails/DAT/issues issues])
** Merging 2 years of development taking longer than expected, but getting there. The plan is to get the patches in VisTrails and never fork again, we never want to get in UV-CDAT's situation (and don't need to).
** VTK cell works fine on Linux but there was flickering on Mac & Windows before; still issues on Mac (Windows status unknown)
** Can get a VCS plot soon (but will need VTK cell fix)
** Integrate in UV-CDAT's build system (so we have cdms, VCS, ...) -> RR can do this, low priority
** How do we integrate scripting?
*** We want to be able to seamlessly make changes to a plot by changing Python code
*** Define new plots by entering Python code without writing modules/packages?
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 13, 2015 ===
'''Updates'''
* [RR] Test skipping whitelist ([https://github.com/VisTrails/VisTrails/pull/1069 #1069]) -- low priority
* [RR] Custom matplotlib modules can't be compatible with both 2.1 and 2.2 ([https://github.com/VisTrails/VisTrails/issues/1067 #1067]); should be fixed for ALPS ([https://github.com/VisTrails/VisTrails/issues/1070 #1070])

'''Items to Discuss'''
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 7, 2015 ===
'''Updates'''
* [RR] Export/import workflow to Python working!

'''Items to Discuss'''
* [Claudio] UV-CDAT
** The UV-CDAT project is the biggest user base of VisTrails
** VisTrails package management provides a lot of friction towards people plugging in their code
** Need to make it easy to integrate your random Python scripts in the system without having to deal with all the boilerplate, at least in the first step
** [RR] argues that modules are still good; UV-CDAT shouldn't move towards a purely script-based backend
** [RR] export/import with Python could reduce a lot of that friction by allowing 1) to edit workflow as Python 2) to open up boxes automatically if needed code doesn't match actual modules
** ...

=== April 29, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] <strike>Abstractions</strike> subworkflows status ([https://github.com/VisTrails/VisTrails/labels/subworkflows tickets])
* [RR] matplotlib compatibility (2.1 & 2.2), [https://github.com/VisTrails/VisTrails/issues/1067 #1067]
** RR to try and fix ALPS matplotlib modules

=== April 22, 2015 ===
'''Updates'''
* 2.2.0 has been released!
* Windows issue (via email from Ryan)
** issue with manifest file (may be a new file in VTK6?)
** Tommy has regenerated new Windows builds
* Binaries, pypi, and conda released
* [RR] Export as script
* Python sources using VTK need to switch to SetInputData (users should be aware of this)

=== April 15, 2015 ===
'''Updates'''
* Ready for 2.2.0 (apart from binary/deps issues)
** Missing some libs (scikit-learn, tej, tdparser, SQLAlchemy+connectors
** Windows: runvistrails.py is no longer used, so the PATH is wrong
** Windows: pip is broken, but it probably wouldn't work anyway because of permission issues (disable this?)
* Queries, upgrades and getPipeline() usage ([https://github.com/VisTrails/VisTrails/issues/1054 #1054])
** Getting a pipeline with getPipeline() is not safe: it might return an invalid pipeline
** This is used in many places throughout the code, like queries
** Upgrading would require going through the controller, but that creates new actions
* [TC] Avoid copying a module's output if it's used as input by exactly one downstream module ([https://github.com/VisTrails/VisTrails/issues/1060 #1060]) (useful for big numpy arrays you can update in-place)

=== April 8, 2015 ===
'''Updates'''
* [DK] Merged RR's changes for output modules (1012 and 1013)
** RR will merge remaining changes, then create v2.2 branch!

'''Items to Discuss'''
* BNL need numpy array to VTK image
** Looks like VTK has some helpers for this
** We will help if issues arise
** Will contribute back to VisTrails package
* Upgrade issue: [https://github.com/VisTrails/VisTrails/issues/1017 #1017]
** Automatic upgrades should happen between versions of provided upgrades
** Our existing upgrades work around this so it doesn't need to be 2.2.0
* Corner-case VTK modules
** No longer need VTKCell input port, so don't interfere with registry and API anymore
** Still work weirdly, people probably shouldn't use them
** But we have lots of clunky modules since we wrap the whole of VTK; some people might rely on this and know how to use them, let's keep them anyway
** Ready for 2.2.0

=== April 1, 2015 ===
'''Updates'''
* [RR] UV-CDAT: bugfixing for 2.2, long-term plans: implement scripting import/export in VisTrails, port to UV-CDAT
* Possibly, try to move to regular VisTrails to use new features

'''Items to Discuss'''
* 2.2 release: nothing much is pending anymore, release next week?
** [TE] vtkExporter classes [https://github.com/VisTrails/VisTrails/issues/1032 #1032]
** [RR] Hiding upgrades in version tree might make it (or might be 2.2.1 so we can test it out) [https://github.com/VisTrails/VisTrails/issues/949 #949]
** Output modules changes to go in
* add note to documentation about order of parameters in VTK
* add issue about exporter upgrades if not already there

=== March 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* 2.2 release
** Checklist on Github: https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist
** Review output modules
** RR has a couple more issues to fix
** Ready to go -- sign app package for OSX? [https://github.com/VisTrails/VisTrails/issues/984 #984] We need access to the Apple Membership team

=== March 18, 2015 ===
'''Updates'''
* [TE] VTK6 works

'''Items to Discuss'''
* [RR] Release v2.1.5 with backported tabledata?
** MTA example needs updated tabledata (for JoinTables)
** Google Maps package still not available
* [RR] Work torward v2.2.0?
** changes:
*** new persistence
*** API changes
*** output module changes (upgrades?), maintain cells but try to upgrade
*** not wrapping stuff
*** VTK6? yes
*** JobSubmission stuff?
*** relabeling for upgrades [https://github.com/VisTrails/VisTrails/issues/949 #949]
** makes sense, needs the tree view code to be updated, check selection
** See [https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist 2.2 checklist]
* Discussion of [https://github.com/VisTrails/VisTrails/issues/1016 #1016]
** plumbing between outputs and output modes, how to define a mode that works for many outputs without writing for each output?

=== March 11, 2015 ===
'''Updates'''
* [RR] persistent_archive done; merge? ([https://github.com/VisTrails/VisTrails/pull/755 #755])
** note about the focus events for widgets
** TE be aware of file_archive for future binaries that include persistent_archive
* [TE] [https://github.com/VisTrails/VisTrails/pull/998 New VTK package] finished

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails? (see last week; decision needed)
** RR email to JF about this
** yes; email sent to Github
* [RR] Switching order of output ports ([https://github.com/VisTrails/VisTrails/pull/1006 #1006])
** added port specs are sorted at a separate spot (Module.*_port_specs properties) than those in the registry (which are sorted in the registry), but those two lists are just combined without respect to sort keys
** need to determine whether the two lists should be merged or remain distinct
** should make sure that order of input ports and output ports makes parallel connections for things with same order
** DK suggests breaking backward compatibility here: workflows still run, can fix easily if a problem in an existing package.
* [RR] Question about output modes ([https://github.com/VisTrails/VisTrails/pull/1007 #1007]), how to integrate in API ([https://github.com/VisTrails/VisTrails/pull/24 #24])
** Should ImageFileMode be removed? ("image" is not a mode, "file" is)
** ImageOutput missing?
** Feel free to change how formats works
* [TE] Test suite segfaults on Fedora 17 virtualbox. Install newer version? (Support ended in 2013)

=== March 4, 2015 ===
'''Updates'''
* [TE] VTK wrapper
** Works on VTK 5.10
** Still need to test VTK 6
** New general wrappers for python functions and classes

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails?
** When [http://i.imgur.com/UTY2qfg.png filing a pull request] from UV-CDAT/VisTrails, VisTrails/VisTrails is selected by default
** People keep forgetting to change the default ([https://github.com/VisTrails/VisTrails/pull/956 #956] [https://github.com/VisTrails/VisTrails/pull/968 #968] [https://github.com/VisTrails/VisTrails/pull/999 #999] [https://github.com/VisTrails/VisTrails/pull/1000 #1000] [https://github.com/VisTrails/VisTrails/pull/1003 #1003] [https://github.com/VisTrails/VisTrails/pull/1004 #1004] [https://github.com/VisTrails/VisTrails/pull/1005 #1005])
** Only way to change that is to not have it marked as a fork of VisTrails/VisTrails
** Github staff [https://gist.github.com/remram44/b364c24ef1e462ce6e2f can make that change for us]; should we do it?
** Juliana: comments on this? visibility vs. convenience/annoyance for developers
* [RR] What about [https://github.com/VisTrails/VisTrails/issues/991 #991]?

=== February 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] vtkviewcell for infovis support, can we unify with VTKCell?
** need to test this
* [TE] vtk wrapping
** Mostly finished
** VTK 5.10 produce incorrect results with old wrapping
*** Old wrapper is based mostly on VTK 4
*** Most vtk_examples affected
*** [http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Replacement_of_SetInput]
*** should be able to upgrade from SetInput to SetInputData (need to drop GetOutput and replace with self ports)
*** can we change vtkInstance to just return self and not wrap things
** terminator example not working under 5.8?
* How does VTK wrapping fit into general wrapping framework?
* [RR] new persistence package

=== February 18, 2015 ===
'''Updates'''
* [RR] New VisTrails API and IPython integration ([https://github.com/VisTrails/VisTrails/pull/24 #24])

'''Items to Discuss'''
* [TE] VTK wrapping
** [https://gist.github.com/rexissimus/16b74693545b5e7c1035 Benchmarking vtk package]
*** Old: 24.7 seconds
*** New: 10.5 seconds (Except first time that adds 8 sec)
**** The parsing that calls is_abstract (that tries to instanciate all vtk classes) is now only run the first time.
**** get_items_from_sigstring takes 2 seconds, maybe we can use a lookup dict for already computed sigstrings?
** Now using a general python function wrapper
*** VTK classes are wrapped into python function that does not depend on vistrails
*** VTK functions can be executed without vistrails
*** The spec maps functions into vistrails modules, but can also describe wrapping
*** A general python function wrapper that supports
**** kwarg inputs
**** single, list, dict outputs
**** callback for progress reporting
**** temporary file generator for using FilePool
**** optional output generation
*** Creating specs:
***** Create spec by hand
***** Auto-create spec outline (TODO) and manually finish it
***** Dynamically create spec (VTK)
***** Implement documentation wrappers (Can use scikitlearn wrapper to wrap numpydoc) (TODO)
***** Classes as bad functions needs to be wrapped in new functions before they are wrapped. This is different for each package.
****** Classes is hard: Like VTK, and matplotlib. Scikit-learn does still not wrap classes
***** Spec diffing and patching could be done using code from matplotlib.
** Still needs upgrades from old VTK package
*** Is it possible to dynamically wrap functions, e.g, you see a SetFunc and just remove the 'Set' prefix. Or do you need to create a complete mapping?

=== February 11, 2015 ===
'''Updates'''
* Update from Friday's meeting
** discussed VisTrails internals
** discussed wrapping
*** xml discussion, hard to modify because tied to db code
*** TE has made it possible to add the schema-defined attributes to the intermediate representation
*** higher-level operations on the port specs
** make sure the simple case works
*** [JF] take a simple package with documentation and figure out what the base case for wrapping is

'''Items to Discuss'''
* [TE] VTK wrapping
** Dynamic loading works
** Reading XML is fast enough, but [https://gist.github.com/rexissimus/8272d3c776ccfa115d82 unserializing data is slow]
** Working on patterns for patching
** Matplotlib has many advanced patterns like argument ordering, nested arguments, alternateSpecs, output types.
*** Having all this in a general wrapper might confuse users?
** [RR] Delay module (except for identifiers) until you need it---e.g. don't deal with port specs, etc. until necessary
* Scripting Support [https://github.com/VisTrails/VisTrails/pull/950 #950]
** [RR] Issue with getting code from modules
** Design a simple solution
** [JF] Couldn't you use modules as black boxes without conversion, just to call into modules/subworkflows easily from e.g. IPython?
*** [RR] This is a job for the API, and a very separate use case. See [https://github.com/VisTrails/VisTrails/pull/24 #24]

=== February 4, 2015 ===
'''Updates'''

'''Items to Discuss'''
* Wrapping
** Format to use? Currently XML (like current matplotlib)
*** JSON and YAML have simple "to python dictionary" methods
*** But don't stream
*** YAML a lot easier for humans
** [DK] vtk-new-package also changes parameter names, creates enumerations
*** intermediate schema needs to be extensible
*** packages will want to store there specific infos for compute() method generation
*** also might have specs-altering info, like matplotlib's alternateSpec
** representation to code , registry already has schema for some aspects
** [RR] We might want to see if Module subclasses can be created lazily
*** no need to create all the classes just to register them in the registry and never actually use most of them
*** future effort
* [RR] Where should VisTrails packages live?
** tej installs as 'vistrailspkg.tej', TE installed it as 'userpackages.tej'
** Currently, standard packages are 'vistrails.packages.', user packages are 'userpackages.' and packages loaded through pkg_resources might be anything
** [RR] Use 'vistrailspkg.' everywhere?
** Long-term effort to simplify package distribution/installation (and have VisTrails get them automatically?)

=== January 28, 2015 ===
'''Updates'''
* T. Caswell to come visit on Fri 6 to discuss wrapping work

'''Items to Discuss'''
* [TE] New VTK wrapping
** Current code by DK seems a good deal faster
** Generates XML that can be patched/tweaked, generates Python code from it, VisTrails only loads generated Python code
** RR would rather have VisTrails load intermediate representation (= XML) directly, wants to make sure this is not slower
** The goal is to turn the intermediate step into something generic that would be used for every wrapped package (vtk, numpy, matplotlib, sklearn, java) instead of each having its own
** TC has its own code at [https://github.com/Nikea/VTTools/blob/master/vttools/wrap_lib.py github:VTTools] which parses numpy docstrings and generates modules, doesn't yet handle classes or persist anything
* Web crawler
** Right now, TE starts jobs for "start crawler", "stop crawler", "install classifier"
** RR would rather have the crawling be a job as far as VisTrails and tej are concerned
** The whole thing would be one pipeline: load examples, train classifier, start crawler [check for job, kill previous one, upload model, start processes], get snapshot, visualize
*** Need some support in tej and job submission system: long-running jobs, stop a job (wait for it to finish?), restart a job even though results are cached

=== January 21, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Unified wrapping method discussion [https://github.com/VisTrails/VisTrails/issues/991 #991]
** TE to work on reusable method with intermediate representation, starting with VTK
* [RR] Examples for scikit-learn: JF has an old example using Weka with parameter exploration (not currently in source tree)
** AM's examples are enough
* [AM] scikit-learn package is done, merge it in? [https://github.com/VisTrails/VisTrails/pull/955#issuecomment-70286788 #955]
** RR will merge
* [RR] What should copyright headers say? [https://github.com/VisTrails/VisTrails/pull/994#issuecomment-70173935 #994]
** Let's keep everything in there: Utah/Poly/NYU

=== January 14, 2015 ===
'''Updates'''
* [TE] Working on classifier
* [RR] Scripting integration, work in progress

'''Items to Discuss'''
* [RR] Unified wrapping method discussion ([https://github.com/VisTrails/VisTrails/issues/991 #991])
** Let's talk next week, [AM] and [DK] are not here

=== January 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* make sure that we address critical issues, questions, and pending review branches in a timely manner
* scripting support
** [RR] no issues if we want to just keep annotations in the generated code to allow the link back to a workflow
** [RR] can translate from workflow to script, working on script to workflow
** will work for parameter value changes, structural changes require changes to the annotations
** need to publish best practices here
** would be cool to do looping in scripts (easier interface than with workflows)
* notebook support (convert form notebook to workflow)
** RR will sync with FC on this
* Issue with console in built-from-scratch
** [TC] iPython rearranged some of the completion stuff in 2.2 and 2.3
** binary has old version of iPython -> 1.0.0, should we update?
* [TC] automated wrapping of numpy and scipy
** discovered a bunch of malformed documentation in numpy and scipy
** has github repo for vistrails tools
** example modules wrap a bunch of R stuff (not baked in, just how things are)
** will be pushing wrapping logic up
** port names forbidden (window and domain)
** have an import hook to get from yaml directly to VisTrails Modules
** should work for any python modules with well-formed numpy docstrings.
* [Action] should make it clear in documentation that Constant now means serializable not that the value doesn't change (e.g. List)
* [TC] might be interesting to try to build components of matplotlib and accumulate in figure (long-term project, but thinking about how this might work)
* [TE] build and build scripts
** completely automatic, buildbot
** need to set the build machines for the environment we want for the binary
** would virtualenv work here?
** [TC] anaconda can pin versions, potential path to test different configurations
** Q: upload nightly binary builds? A: makes sense, make sure they are well-labeled
* sourceforge stats: e.g. http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07
* package issues (see Remi's message)
* [TE] Scope of tej
** Support single ssh commands?
** Queue can be used as a remote machine (crawler is using queue.call*)
* SourceForge stats: http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07

== Older meetings ==
* [[Development/2014]]
* [[Development/2013]]
* [[Development/2012]]
* [[Development/2011]]
* [[Development/2010]]

Development

2016-06-01T15:00:40Z

Tommy: /* 2016 */

<div class="nonumtoc toclimit-1">
__TOC__
</div>

See also the [https://github.com/VisTrails/VisTrails/wiki/Development Github wiki]

== 2016 ==

=== June 1, 2016 ===

'''Updates'''
* VisTrails 2.2.4 announced (finally)
** 5 survey replies
** 47 downloads last week

'''Items to Discuss'''
* [TE] Export VTK as script (python-wrapper)
** to_python_script
*** needs the pipeline (or at least the connections)
**** Should not generate code for any possible VTK method (exporter detects which ports is used in the source)
**** VTK needs to know connection order
**** Adding functions directly to the script results in nicer code
** Add support for multiple input connections
** Add support for list looping

=== May 25, 2016 ===

'''Updates'''
* Mailing-list fixed
* Getting stats from the "server news" mechanism (via [https://github.com/remram44/apache-log-info parser])

'''Items to Discuss'''
* [RR] Alexis doing writeup on VisTrails, curious about interesting streaming use-cases (and potential future users)
* [TE] Union ports
** Show union ports in pipeline (DEMO)

=== May 18, 2016 ===

'''Items to Discuss'''
* [TE] mailing list still down - Julio working on it
* [TE] Improved union port
** New schema 1.0.5 adds portitem.union string attribute
** Works with pipeline view, parameter exploration view, and mashup view
** Should work well for matplotlib
** Use with VTK ports?
*** It uses [item_1,item_2] style ports usually with different tuple length.
* [TE] Remove emacs dependency from db generate [https://github.com/VisTrails/VisTrails/issues/1173 #1173]

=== May 11, 2016 ===

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]
** GUI-based solution [https://github.com/VisTrails/VisTrails/tree/union-port Branch union-port] Demo?
*** Shows single port for all ports with same sort_key
*** Select specific type when adding/showing
*** Only one type should be visible on the module at any time
*** Making tuple parameters union types is probably too complicated
*** Should work with alternate specs like matplotlib (if sort_key is defined correctly)

* [TE] Feature suggestion: Let connections connect to functions/parameters
** Show functions and parameters as ports and toggle port visibility directly for functions and parameters
** Use separate views for ports and functions (like before)
*** Allow rearranging of functions
** Pros:
*** Supports ordered connections. Create 2 functions, make them visible as ports, make connections to them.
**** We can also have, e.g., a line joining the ports on the module to indicate they are part of a list.
**** Makes List module simpler
*** Connect to parameter in tuple
*** Functions that are visible on the module can connect to an actual function, and not just to the first one it finds.
*** Can replace operation modules (in python-wrapper) in some cases for, e.g., numpy.
** Cons:
*** Interface more complicated and crowded
*** More difficult for users to grasp?
*** No immediate use case
*** Makes no union type for tuple parameters a bigger problem.

* [TE] Publish user survey?
** No response from vistrails release yet
** Not announced on vistrails-users yet.

=== May 4, 2016 ===
'''Updates'''
* VisTrails 2.2.4 released

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]

=== April 27, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Wrapping Bokeh
** New method type "operation"
*** Transforms Figure->Glyph->Output into Glyph->Figure->Output
**** Glyph sets function name and arguments as output
***** Not serializable, but should always be computed together with the subject of the operation.
**** Figure applies Glyph operation on itself
*** Useful for matplotlib?
**** matplotlib currently find actors by searching upstream?
**** But this is more difficult since matplotlib is not function-based.
** New "union" port type
*** Turns "x(float), x(list)" into "x (float, list)" and uses first set value
**** Uses only first value in tuple
**** Bokeh have many properties that support (list, string, Float)
*** Does not work with depth=1 types (e.g. Float of depth 1)
**** Turn Depth 1 types with known type into lists?

* [TE] New bugfix release
** Finalize survey

=== April 20, 2016 ===
'''Updates'''
* Merged upgrade fixes
** Now has infinite loop test
** loop test now correctly loops 5 times
*** remap_module used wrong (current) package version when creating ModuleDescriptor
* Fixed multi-step group upgrades (PR: [https://github.com/VisTrails/VisTrails/issues/1168 #1168])

'''Items to Discuss'''
* New bugfix release
** Merge usagestats
** Need to finalize survey

=== April 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Chaining upgrades done ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Replace "Upgrade" description annotation with "upgraded_from" annotation to identify which tags to hide?

* [TE] Iterating handle_invalid_pipeline ([https://github.com/VisTrails/VisTrails/pull/1165 #1165])
** Not based on [https://github.com/VisTrails/VisTrails/tree/chain-upgrades-loop chain-upgrades-loop]
** Cherry-pick test to preserve source?
** Need maxPipelineFixAttempts option?
*** The code is now smarter about recursion, so max attempts will "probably" never be reached.
** Need [https://github.com/VisTrails/VisTrails/commit/0ef0667426937eddb1d1c1e397f0657ffec039a9 debug messages]?
*** Would need to be moved into handle_invalid_pipeline

=== April 6, 2016 ===
'''Updates'''
* [TE] Query View improvements
** Done except for displaying "Version Info" and #1164
* [RR] Working on finishing new interpreter (finally!)

'''Items to Discuss'''
* [TE] Chaining upgrades ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Try latest upgrade first, then previous.
** If all fail, select latest upgrade?

=== March 30, 2016 ===
'''Updates'''

'''Items to Discuss'''

* [TE] Query View improvements
** Unified do_version_switch and get_upgrades as validate_version()
** Problems with query view using its own controller
*** Fixed module info not being displayed for query results
*** Still no version info for query results
*** Still an issue with version query view not being updated

=== March 23, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Usage reporting almost ready to go
** Need to record whether specific features are used: paramexpore, mashup, query
*** [DK] Record if LaTeX extension is used? But hard to distinguish from direct batch invocation
** How to record size of vistrail?
*** [DK] IdScope already walks over vistrail, use that
*** but total number of modules and versions doesn't give an idea of average size of individual pipelines

=== March 16, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Upgrades in Query Mode
** Now using code similar to do_version_switch
*** Uses handle_invalid_pipeline
*** Differences: Not using current_pipeline, flushes changes
*** New controller method get_pipeline optimized using cached pipelines (but not current_pipeline)
*** Integrate to avoid repeated code?
*** Use this for query mode?
* [TE] VisTrails 2.2.4 ready for release?
** tej package updated. Others?
* [JF] upgrades and the version tree
* [JF] provenance in Jupyter
* [DK] bundles: [https://github.com/VisTrails/VisTrails/pull/1092 #1092]

=== March 9, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixing search mode
** String query now matches all by default
*** This caused pipeline queries to never match
** String query can search: User/Notes/Tagname/Time/Module name
*** Should we search module names by default? (Disabled by default because it is expensive)
*** Fixed notes search
** '>' parameter queries in documentation but has been removed
** Fixed module matches for upgraded pipelines (By not upgrading pipeline)
*** Upgrades still a problem
*** Add "Upgrade all menu option?" (Or upgrade all on open when `hideUpgrades`)
*** [JF] Allow search on past tags

* [TE] Create new bugfix release
** Finish querying
** Path issue on windows

* [DK] Look into sqlalchemy and new bundle branches

=== March 2, 2016 ===
'''Updates'''
* [TE] Fixed cache bug with port specs
* [TE] VisTrails Next
** Most packages now work
** No qgis for Python 3

'''Items to Discuss'''
** Always dereference symlinks? [https://github.com/VisTrails/VisTrails/issues/1146 #1146]

=== February 23, 2016 ===
'''Updates'''
* [TE] Fixed PythonSource 100% CPU bug
* [TE] VisTrails Next
** Updated [http://opendap.co-ops.nos.noaa.gov/axis/webservices/wind/ NOAA Web Service] examples
*** Now uses REST service, tabledata, and Google Maps
*** Web Service replaced with DownloadFile

'''Items to Discuss'''
* [RR] Couple of fixes are in for API, and tej&reprounzip on the Mac binary. Also new release of tej, and working on anonymous usage reports.
** New 2.2 release soon?
* [RR] Anonymous usage reports
** Sends out info like number of modules & versions, packages used, Python & libs versions, execution time, specific features [https://github.com/VisTrails/VisTrails/pull/1154 #1154]
* [JF] Bring in noWorkflow to track variable dependencies, for the considered Jupyter integration?
* noWorkflow - provenance for python scripts
** Recent work on tracking dependencies
* Also integrates ReproZip with Jupyter
** [http://mybinder.org mybinder]
*** Use with ReproZip to automatically build Jupyter notebook interfaces
* Daves comments on Jupyter integration
** It is possible to identify cell order on the server side
** Not trivial to track order of cells on client side
* How does Galaxy workflows relate to VisTrails?
** Packaging in Galaxy is hard
** Galaxy for biomedical workflows, difficulty making it general
* Action items
** How difficult to track cell dependencies in Jupyter notebooks?
** Use noWorkflow to track cell dependencies?
** How difficult to modify mybinder to use ReproZip packages?

=== February 17, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixed Group memory usage
** Modules in groups are supposed to be freed when done executing
*** Prevented by logger that stored references to the modules (fixed, now using id(module))
*** Prevented by list iterator bug that stored list of modules on the 'self' port bug (fixed)
* [TE] VisTrails Next
** Removed deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** PythonSources will be upgraded
*** Fixes for Python < 3
*** fixes for VTK < 6
** TODOs
*** Remove RemoteQ
**** Port Hadoop to tej (Already have pbs)
*** Merge package wrapper
*** Finish SQLAlchemy branch
*** Finish new bundle branch
** [JF] Will contact Jeff and Matthias about moving to Python 3
* [JF] Query by Example is broken
* [JF] VisTrails Data Cleaning Project
** Use VisTrails to process and explore task-specific data while keeping provenance.
** Remi's Idea
*** Use VisTrails as the backend in a Jupyter notebook
*** Overcome problems with executing cells in random order
**** Interesting research topic, but little interest has yet been noted
*** Interesting to study how such a notebook would be used (Is there notebook usage data available?)
*** Impose restrictions to notebook cell boundaries
*** It will only work for functional operations
*** Can we fix, or detect, non-functional (mutating) operations?
*** Analyse code and data flow and see if it mutates data in unexpected ways?
*** Mutable operations can be created in many ways in Python
* Next meeting Tuesday 11:30

=== February 10, 2016 ===
'''Updates'''

'''Items to Discuss'''
* VisTrails Next
** Test suite passes
*** Python 3 less deterministic, module upgrade order random.
** [RR] updating packages: Reprounzip (pushed), tej, persistent_archive, ...
** All of our packages should run fine :)
** VTK thumbnail comparison works
*** Rendering bug on some systems
**** QVTKCell now inherits QGLWidget
*** Old thumbnails had wrong height due to spreadsheetwindow being too small
**** Fixed by regenerating thumbnails
*** Silenced deprecation messages when generating modules
*** Many new classes in VTK 7
** Remove deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** Will break existing PythonSources
**** Try to upgrade?
*** Old-style packages
**** Or only allow a new style, like __init__.py renamed to info.py? (merge with identifiers.py?)
***** Read info.py without importing package?
*** Fixes for Python < 3
*** Fixes for Qt < 5
*** fixes for VTK < 7
*** Remove self port?

=== February 3, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] [http://lists.vistrails.org/pipermail/vistrails-users/2016-January/000402.html Rendering a .pvd (ParaView) file?]

* VisTrails Next
** All tests but thumbnail comparison passes
** Still issues with gui and more packages needs to be tested
** PythonSource and MplSource upgraded with lib2to3
** Keep contrib packages? Update?
** [https://blog.kitware.com/vtk-7-0-0/ VTK 7 is released]
*** Supports Python 3
*** Will hopefully get into conda and others soon
*** Deprecates a bunch of modules

* [https://travis-ci.org/VisTrails/VisTrails/builds/106743348 Travis builder] for VisTrails Next
** Runs!
** Uses conda
*** Many levels of requirements
**** apt packages
**** conda packages
**** python packages in requirements.txt
**** python packages in setup.py
*** Can probably drop conda. Default builder does not have Qt5, but beta builder do!
*** But useful if we want to use conda in our own build process.
** Lots of errors I do not get locally?

* [http://goo.gl/forms/Z4HBrwaBWL User Survey]
** Have you used any alternatives to vistrails?
*** Relevant? More options?
** How often do you use any of these particular features in VisTrails?
*** Add/Remove alternatives?
** How important would you rank the following potential improvements to VisTrails?
*** Add alternatives?

=== January 27, 2016 ===
'''Updates'''
* New interpreter
** Working prototype soon
** Looping not completely done (and port combination mode: pairwise/cartesian...)
** Need to integrate with VisTrails
*** Compatibility with existing modules
*** Use log controller
*** Want to cache at multiple levels (whole stream/single element of stream)
*** Non-runtime attributes of modules (cache check, automatic conversion check, constant from/to string)

'''Items to Discuss'''
* User Survey

* ZMQ failing on windows (vistrails-users)

* [TE] [https://github.com/VisTrails/VisTrails/pull/1143 Python 3 branch]
** Testsuite almost passes
*** Failing are unicode filenames, some users guide examples, and thumbnail comparisons.
** Fixed issues
*** Signatures are now bytes (convert to string to show in widget)
*** Cannot compare different types, e.g., (None < 1)
**** PortSpec.depth and min/maxConn could be None. (Backport!)
**** cell.row could be None
*** Lots of unicode/bytes fixes to serializations
**** We have encryption implementations in the code! (keychain)
*** Lots of small fixes to package method differences
** Current issues
*** logging widget empty?
*** version tree signals messed up
*** provenance view legend icons black
*** Text do not fit in some widgets
*** VTK thumbnail comparison fails
**** VTK Cells have some faces in wrong direction?
**** Because running in VM?
** Installing on Ubuntu LTS/Latest Mint
*** Install latest matplotlib from pip
*** Install VTK 7.0.0rc2 from source
*** No QtWebEngine binary (controversial) (Must install sip/PyQt5/Qt5 from source)

=== January 20, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Backporting features from Python 3 + PyQt5 + Qt5
** Merged unicode with master ([https://github.com/VisTrails/VisTrails/tree/unicode unicode])
*** One unicode test failing
*** Problem saving to xml
** Used [http://python-future.org/ python-future] to run futurize stage 1 to update legacy (pre 2.6) code ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized unicode-futurized])
*** Updates print to functions 'from __future__ import print_function'
*** Updates exception calls to use 'as'
*** removes most usages of 'long' (mostly used unnecessarily)
**** Only needed for 32-bit support
*** Fixes relative imports (from __future__ import absolute_import)
** Fixing code that is deprecated in Qt 4.8 and removed in Qt 5 ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized-qt5 unicode-futurized-qt5])
*** Updated all signals to new-style
* If we go 2 to 3, this could break packages
** means we should schedule any package format changes for the same time
** e.g., imports should be unrelated to code path (function to load module from package identifier?) (take them out of vistrails.* [https://github.com/VisTrails/VisTrails/pull/1002 #1002])
** any structural changes (e.g. the __init__ versus init thing) (RR thinks it makes sense, though having both named "init" is unfortunate)
** putting package identifier as xml?
*** Python not so bad, plus some stuff in there is Python code (checking dependencies)
** version the APIs?
*** RR planning on versioning vistrails_module.Module, no point versioning the whole package?
* file formats on 2 to 3:
** no real translation/upgrade, but non-ascii values that work on 3 won't load in 2

=== January 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://gist.github.com/rexissimus/dfd27e466427529c385c Porting to Python 3 / PyQt5]
** Basic GUI and execution works
** Minimal work to support 2to3
** Hard to support both PyQt4 and PyQt5

=== January 6, 2016 ===
'''Updates'''
'''Items to Discuss'''
* Updating VisTrails dependencies
** Successfully built [https://gist.github.com/rexissimus/f1a1aada7de1c00a57c7 Win7-64/Python3/PyQt5/Qt5/WebEngine/VTK7]
*** VTK 7 is the first supporting Python 3 but is only in release candidate phase.
**** Next version of VTK 6 is rumored to support Python 3
**** There is a development branch of VTK 6 supporting Python 3
*** Can travis build this?
**** We can skip tests for WebEngine and VTK if needed
** Python 3 [https://python3wos.appspot.com/ showstoppers]
*** No MySQL-python (sqlalchemy supports mysql through other drivers)
*** No suds (there are active forks but we could also drop support?)
* Options for python2/3 support:
** Interpreter could be python2/python3 based on packages
** six layer works but not the easiest to maintain (e.g. in reprozip)
* Drop support for win-64
* Update copyright headers to 2016

== 2015 ==

=== December 30, 2015 ===
'''Updates'''
* Bokeh package finished
** Can output to Browser/IPython/Spreadsheet (Limited functionality in spreadsheet)
'''Items to Discuss'''
* Updating VisTrails dependencies
** Bokeh needs QWebEngine (Chromium) in Qt5 which requires PyQt5
*** Many plotting libraries only work in browsers
*** But Chromium may be a big and controversial dependency
*** Or create a browser version of the spreadsheet?
** Some users have requested Python 3
** Not backwards compatible?
** Target for VisTrails 3.0 with new interpreter?

=== December 16, 2015 ===
'''Updates'''
'''Items to Discuss'''
* Users list question
* [TE] Wrapping Bokeh
** Added bokeh property parser
*** complements numpydoc parser
*** Not all attributes are available, partially because I am using a pre-release version.
** Wrapped modules
*** bokeh.plotting finished (Backwards like matplotlib: Create plot then draw on it)
*** bokeh.charts mostly done (Missing arguments)
** QWebView mostly works (but no zooming or buttons)
*** It would be better to use external browser or QWebEngineView
** Added improvements to wrapper
*** Generalized port translations (Color/Path to native types)
*** Can use multiple docstring/property parsers simultaneously

=== December 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Looking into wrapper
** Will port TensorFlow
** Doing a pass on the wrapper code & doc
*** UX improvements
** Factorize high-level docstring parsers into core.wrapper? (sphinx, numpy, google)
** Problem with name vs module_name (fails sklearn tests because class_by_name() is broken)
** Looking into compressing specs, lazy registration of modules

=== December 2, 2015 ===
'''Updates'''
* [TE] Package wrapping
** Wrapped most of numpy/scipy using __all__
** Added class attribute and method access for classes (Can add to class or to separate inspector module)
** TODO: Document wrapping procedure

'''Items to Discuss'''

=== November 25, 2015 ===
'''Updates'''
* [RR] New interpreter is coming along
** Everything is a stream
** Task system, eventually work-stealing parallelism
** Streams no longer advance in lock-step
*** Allows for constructions like filter, join, sorted-merge
** depth>1 still to be tested, no current plan to allow this through the module interface
*** Through looping though, can do streams of streams

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapped most numpy functions (no polynomials)
** and half of scipy classes and functions
** Added functions manually from documentation (no parseable lists?)
** Focusing on data flow constructs (no property/method access for classes)
*** Using spec diff (empty for now) and dynamic parser (stores spec in .vistrails/)
** Python class/function wrapper now stable
** Add google doc parser?
*** Is there a parser available?

=== November 18, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Numpy class wrapping works
*** Basic type is List, since most types are array_likes.
*** TODO: More classes and functions
*** Some operations are in-place and some aren't, and docstring not super clear
*** [RR] It seems only methods mutate, and most have a numpy.xx function equivalent; just manually go through the methods and remove the mutating ones?
** Class wrapper is modular
*** Docstring parser and type string parser can be customized
*** Classes can have optional attribute/method ports
**** Inspectors and attribute/method modules can be created separately
** Use PythonCalc as an example
*** Can be re-implemented as a function with a parseable docstring
*** [RR] PythonCalc is just an example, and it might actually make sense to get rid of it, or do a proper math package with scalar operations (as separate modules, no combobox)
** [RR] TensorFlow to use wrapping as well
*** Very simple (only types 'tensor' & 'variable')

=== November 11, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapping numpy's classes using numpydoc (ndarray)
*** Wrapping constructor arguments, attribute getters/setters as module ports
**** Then how to access attributes afterwards?
***** Use input value port to class modules?
*** Wrap methods as modules? E.g., `ndarray.shape`.
*** Function wrapping is almost a subset of class wrapping
**** May be able to use the same parsing/execution methods
** VTK's non-getter/setter methods could be wrapped as modules
*** We could then remove extra logic in interpreter for keeping function order
** Bokeh uses autogenerated docstrings
*** We may be able to read the specification directly

* [RR] [https://github.com/VisTrails/VisTrails/pull/1138 TensorFlow package]
** Basic setup working, can execute the Mandelbrot example
** Will autogenerate the operations

=== November 4, 2015 ===
'''Updates'''
* [RR] Interpreter work requires a fix for [https://github.com/VisTrails/VisTrails/issues/1137 DB issue #1137]
* [DK] Kitware's Resonant [http://www.kitware.com/source/home/post/173]
** [https://github.com/girder/girder Girder]: data management system
** [https://github.com/Kitware/romanesco Romanesco]: execution engine, uses [http://www.celeryproject.org/ Celery] for task management
** Resonant Flow: web app for editing and executing workflows

'''Items to Discuss'''
* [TE] Added OSX Lion (10.7) VM on build machine using vagrant (seems ok with license?)
** New builds works on Lion
** Change the minimum requirement to 10.7?
* [TE] Package wrapping
* Added upgrade suggestions using 2 spec versions ([http://pastebin.com/30XUU8Gp example])
** using name edit distance to find matches
** Could use something better like port similarity for modules, and type similarity for ports
** Should write python upgrade code?
** Added spec to sklearn package
*** Can now diff spec versions and keep the spec static
*** There will be problems with downgrades and package versions

=== October 29, 2015 ===
'''Updates'''
* [TE] nightly-build-mac fixed (Needed to approve xcode license)

'''Items to Discuss'''
* [TE] matplotlib wrapper
** ported to general spec
** Diff can be used on general spec
*** Only needed minor changes
*** Fixed indexing bug that corrupted specs
*** Can now move diff tools to core/wrapper
** Add new plots?
*** New plots in mpl 1.3: eventplot
*** New plots in mpl 1.4: angle_spectrum, magnitude_spectrum, phase_spectrum', violinplot
*** No new plots in mpl 1.5 (from looking at boilerplate.py)

=== October 21, 2015 ===
'''Updates'''
* [RR] Alexis has arrived, will be working with [RR] on a more efficient interpreter

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package]
** Supporting multiple package versions
*** Check which version can be loaded [https://github.com/VisTrails/VisTrails/pull/1135 #1135]
*** We cannot show version requirements in the list of packages because old packages are loaded when importing the codepath
** Visual diff does not work well, but we can use the spec differ to see differences.
** Unifying vtk and matplotlib wrapping specs (WIP)
*** And porting matplotlibs spec differ to work on the general spec
*** Spec differ can then be used on vtk and other packages in the future
*** Will enable automatic upgrade generation
* [RR] Rework interpreter
** restore abstraction between interpreter/module code
** build looping, streaming, caching into the interpreter
** rework cache
** look into parallelism once basic functionality is there

=== October 14, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package] (adding numpydoc parser)

=== October 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/tree/fix-matplotlib-parser New matplotlib parser] (adding numpydoc parser)
** Added numpydoc attribute parser for plots.
*** TODO: Need better port spec reconciliation with call signature parser.
*** We can create a general numpydoc parser, but attribute types are unique to matplotlib.
** Needs package versioning
*** New spec will not support matplotlib < v1.4 due to changed path to axes classes.
*** Load spec version corresponding to installed matplotlib version?
*** Need version downgrades?

=== September 30, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Updating Matplotlib parser
** Matplotlib docstring parser fails on numpy docstrings
** I have [https://github.com/VisTrails/VisTrails/commit/eae8b0c16260810587e47c41cab53552cbb3cf0a added basic numpydoc parsing]
*** Only used by a few docstrings so far
*** Parsing uses many sources (class tables, signatures, ACCEPTS, method docstrings, definition parsing).
** Caswell said they were thinking about moving to traitlets, but this is not ready yet

=== September 23, 2015 ===
'''Updates'''
* [TE] VisTrails 2.2.3 released
** Also have pushed to PyPI, binstar, etc.
** Sourceforge vs. GitHub
*** should be able to host releases on GitHub
*** nightly binaries pushed to sf each night
*** old binaries?
* [TE] Re-wrapping MatPlotlib
** Keep static generation - Docstrings are brittle beween matplotlib versions
** Keep generating the executable classes - but create functions, not vistrails Modules
*** Why is there so much patching?
** Re-implemented Alternate PortSpec for InputPortSpec
*** It will now inherit specs from parent (No need to reimplement)
** Module upgrades?

'''Items to Discuss'''

=== September 16, 2015 ===
'''Updates'''
* [TE] Job Monitor tests and documentation done
** OK to leave document package in packages directory?

'''Items to Discuss'''
* [TE] Library wrapping: How to do code patching? [https://docs.google.com/drawings/d/1Sh3eOXot6v2y880jHKQrqXqAwr-0aoqYligg3z8G8MY/edit?usp=sharing Wrapping diagram]
** Insert code into module template (Old VTK code)
** Patch the library that is called (New VTK code)
** Somehow store code in spec and apply when executed?
*** Executed code needs at a minimum access to inputs, outputs, current class
*** Use standard input/output dict and obj reference that the code operates on?
*** Can this be done while keeping the execution abstract?

* Do new release now?

=== September 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* New release?
** [RR] wants reprounzip
** tej changes & doc
** job monitor & jobmixin fixes
** mongodb
** reprounzip
** warning: MplFigure type is int
** tabledata: add Reshape, DictoToTable & ListToTable, fix ListToTable with numpy arrays
** PythonSource can have same name for an input & output
** don't show spreadsheet at exit

=== September 2, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Limit autosaves? [https://github.com/VisTrails/VisTrails/pull/1126 #1126]

=== August 26, 2015 ===
'''Updates'''
* [TE] Added Job support to Parameter Explorations (Requested by Colin), and Mashups
** specify job ids, need to specify different ids for parameter explorations since they have the same version id
** how to deal with parameters passed in on command line
* [General] provenance: should be creating a new version when we execute workflow with changed parameters?
** currently, custom_params annotation stores this in provenance currently
** [RR] API doesn't record provenance if passing in parameters: http://git.io/vsAA5
'''Items to Discuss'''

=== August 19, 2015 ===
'''Updates'''
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [TE] Working on Job Monitor documentation

'''Items to Discuss'''
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [TE] Stop testing VisTrails 2.0?

=== August 12, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Build broken on Travis; because of IPython 4 released today? ([https://travis-ci.org/VisTrails/VisTrails/builds/75279795 build 992]; [https://github.com/VisTrails/VisTrails/issues/1123 #1123])

=== August 5, 2015 ===
'''Updates'''
* [TE] Fixes to Jobs
** Could not delete jobs
** Could not run job in group
** Job not reset when calling ModuleSuspended
** Added deleting job from context menu
* [RR] Writing documentation for everything [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

'''Items to Discuss'''

=== July 29, 2015 ===
'''Updates'''
* RR still looking into new interpreter thing
** Goal is to take out scheduling logic from Module so it can be split in multiple processes, and so that smarter strategies can be added in time
** This means some work on packages
** Spreadsheet can live in kernel process? Still some UI stuff that will take work (changing configuration, persistent archive's viewer, ...)
* [TE] Problems running examples [https://github.com/VisTrails/VisTrails/pull/1111 #1111]
** Testing of more examples requires additional packages on the test machines.
** Fixed faulty line-ending in PythonSource:s failing on Python 2.6.
** Test suite now testing SUDSWebServices (If web service is down, test suite will fail)
** preferences.py test failed reloading 'dialogs' package, switched to using 'URL'.

'''Items to Discuss'''

=== July 22, 2015 ===
'''Updates'''
* [TE] mailing lists back online
* [TE] Working on [https://github.com/VisTrails/VisTrails/issues/1107 #1107]
* [RR] Working on ReproZip package

'''Items to Discuss'''
* [RR] MongoDB package [https://github.com/VisTrails/VisTrails/pull/1106 #1106]
* [RR] Example for tej docs? [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

=== July 15, 2015 ===
'''Updates'''
* 2.2.2 released

'''Items to Discuss'''
* RR is considering executing everything in an IPython kernel (i.e. separate Python interpreter, like the one spawned for a notebook)
** It's a separate process that we can restart without restarting the app/gui
** We can isolate the execution environment (e.g. for the server)
** We can run the whole thing remotely (if your data is elsewhere, just run VisTrails locally and the pipeline elsewhere)
** Pipeline execution no longer makes the interface hang, it just makes the kernel hang (but that's fine)
** We can use notebooks as modules (probably way nicer than the PythonSource module)
** We can run multiple kernels so long as the ports carry things that are serializable
*** meaning we can put the multithreaded-interpreter without all the hacky parts it has now
*** we can run IPython kernels in all the languages IPython supports, [https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages currently 46]

=== July 8, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Buildbot github hook not working after IP address change
* [TE] No reference to VistrailsApplication ([https://github.com/VisTrails/VisTrails/issues/1103 #1103])
** [RR] Added PR [https://github.com/VisTrails/VisTrails/pull/1104 #1104]
* [TE] Reopening VT file after saving with bundled subworkflow won't offer subworkflow upgrade ([https://github.com/VisTrails/VisTrails/issues/1102 #1102])
** allow manual delete to fix right now
** fix this on top of the use-uuid branch
* [TE] Release VisTrails 2.2.1? ([https://github.com/VisTrails/VisTrails/blob/v2.2/CHANGELOG CHANGELOG])
** [https://github.com/VisTrails/VisTrails/pull/1093 output-modules-use-global-dir]
** [https://github.com/VisTrails/VisTrails/milestones/version%202.2 Current issues for 2.2]

=== July 1, 2015 ===
'''Updates'''
* [TE] PROV fixed
* [TE] Working on subworkflow issues
* [RR] Considering reworking the controller (log vs exception problem, retained upgrades causing interferences) and also the interpreter (IPython?)

'''Items to Discuss'''

=== June 24, 2015 ===
'''Updates'''

'''Items to Discuss'''
* UV-CDAT
* [TE] Can a cyclic workflow be valid? ([https://github.com/VisTrails/VisTrails/issues/1097 #1097])
** focus on disabling the ability to create cyclic pipelines because more things break than just this with a cyclic pipeline
* [RR] Relative paths ([https://github.com/VisTrails/VisTrails/pull/1057 #1057])
** This interacts with the new bundle; how do handle packing files inside the VT bundle?

=== June 17, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] current_version and reusing existing upgrades are broken ([https://github.com/VisTrails/VisTrails/issues/1095 ticket #1095])
** Could be that export to PROV is using an unflushed upgrade pipeline?
** current_version would then be correct.
** It may work to flush the actions before exporting?

=== June 10, 2015 ===
'''Updates'''
* DAT: fixed VTK issue on Linux and Mac
* Still crashes on Windows. Need help! Reminder: this works in the VisTrails spreadsheet (QCellPresenter), although no widget get changed there during a drag
** Is it a VTK bug?
** Is it simply impossible to change widgets during the drag, should we do it a different way?
** Did I miss something that is done in VisTrails but somehow not in DAT?
** Low prio, UV-CDAT doesn't run on Windows anyway

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 Updated pull request])
* Single instance code and batch mode

=== June 3, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 pr])
** Requires fixes to command line parameters, Output modules, and batch mode
** How to test this
** Updated missing/outdated flags
** Fixed view issues when generating graphs
* [TE] batch mode
** SpreadsheetOutput not enabled in batch mode. Should we check is_running_gui instead?
** Other instance setting flags from caller
** Is graphsAsPdf replacing spreadsheetDumpPdf?
** graphsAsPdf true by Default?
** Batch mode executing by default (Not needed when generating graphs)
** Re-added workflowInfo as withWorkflowInfo for writing graph and xml workflow
** [DK] batch mode should be outputting to files or stdout, shouldn't always trigger SpreadsheetMode
** execute flag, maybe make execution the default and allow a "--no-execute" if you only want to capture graphs, for example

=== May 27, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] API question
** http://lists.vistrails.org/pipermail/vistrails-users/2015-May/000357.html
* Status of DAT
** Can add VCS plot to DAT but need to work on configuration windows
** Documentation for graphics templates for UV-CDAT/vcs?
* Qt support?

=== May 20, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Reviving the DAT, integrating scripting & porting UV-CDAT!
** On [https://github.com/VisTrails/DAT GitHub] ([https://github.com/VisTrails/DAT/issues issues])
** Merging 2 years of development taking longer than expected, but getting there. The plan is to get the patches in VisTrails and never fork again, we never want to get in UV-CDAT's situation (and don't need to).
** VTK cell works fine on Linux but there was flickering on Mac & Windows before; still issues on Mac (Windows status unknown)
** Can get a VCS plot soon (but will need VTK cell fix)
** Integrate in UV-CDAT's build system (so we have cdms, VCS, ...) -> RR can do this, low priority
** How do we integrate scripting?
*** We want to be able to seamlessly make changes to a plot by changing Python code
*** Define new plots by entering Python code without writing modules/packages?
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 13, 2015 ===
'''Updates'''
* [RR] Test skipping whitelist ([https://github.com/VisTrails/VisTrails/pull/1069 #1069]) -- low priority
* [RR] Custom matplotlib modules can't be compatible with both 2.1 and 2.2 ([https://github.com/VisTrails/VisTrails/issues/1067 #1067]); should be fixed for ALPS ([https://github.com/VisTrails/VisTrails/issues/1070 #1070])

'''Items to Discuss'''
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 7, 2015 ===
'''Updates'''
* [RR] Export/import workflow to Python working!

'''Items to Discuss'''
* [Claudio] UV-CDAT
** The UV-CDAT project is the biggest user base of VisTrails
** VisTrails package management provides a lot of friction towards people plugging in their code
** Need to make it easy to integrate your random Python scripts in the system without having to deal with all the boilerplate, at least in the first step
** [RR] argues that modules are still good; UV-CDAT shouldn't move towards a purely script-based backend
** [RR] export/import with Python could reduce a lot of that friction by allowing 1) to edit workflow as Python 2) to open up boxes automatically if needed code doesn't match actual modules
** ...

=== April 29, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] <strike>Abstractions</strike> subworkflows status ([https://github.com/VisTrails/VisTrails/labels/subworkflows tickets])
* [RR] matplotlib compatibility (2.1 & 2.2), [https://github.com/VisTrails/VisTrails/issues/1067 #1067]
** RR to try and fix ALPS matplotlib modules

=== April 22, 2015 ===
'''Updates'''
* 2.2.0 has been released!
* Windows issue (via email from Ryan)
** issue with manifest file (may be a new file in VTK6?)
** Tommy has regenerated new Windows builds
* Binaries, pypi, and conda released
* [RR] Export as script
* Python sources using VTK need to switch to SetInputData (users should be aware of this)

=== April 15, 2015 ===
'''Updates'''
* Ready for 2.2.0 (apart from binary/deps issues)
** Missing some libs (scikit-learn, tej, tdparser, SQLAlchemy+connectors
** Windows: runvistrails.py is no longer used, so the PATH is wrong
** Windows: pip is broken, but it probably wouldn't work anyway because of permission issues (disable this?)
* Queries, upgrades and getPipeline() usage ([https://github.com/VisTrails/VisTrails/issues/1054 #1054])
** Getting a pipeline with getPipeline() is not safe: it might return an invalid pipeline
** This is used in many places throughout the code, like queries
** Upgrading would require going through the controller, but that creates new actions
* [TC] Avoid copying a module's output if it's used as input by exactly one downstream module ([https://github.com/VisTrails/VisTrails/issues/1060 #1060]) (useful for big numpy arrays you can update in-place)

=== April 8, 2015 ===
'''Updates'''
* [DK] Merged RR's changes for output modules (1012 and 1013)
** RR will merge remaining changes, then create v2.2 branch!

'''Items to Discuss'''
* BNL need numpy array to VTK image
** Looks like VTK has some helpers for this
** We will help if issues arise
** Will contribute back to VisTrails package
* Upgrade issue: [https://github.com/VisTrails/VisTrails/issues/1017 #1017]
** Automatic upgrades should happen between versions of provided upgrades
** Our existing upgrades work around this so it doesn't need to be 2.2.0
* Corner-case VTK modules
** No longer need VTKCell input port, so don't interfere with registry and API anymore
** Still work weirdly, people probably shouldn't use them
** But we have lots of clunky modules since we wrap the whole of VTK; some people might rely on this and know how to use them, let's keep them anyway
** Ready for 2.2.0

=== April 1, 2015 ===
'''Updates'''
* [RR] UV-CDAT: bugfixing for 2.2, long-term plans: implement scripting import/export in VisTrails, port to UV-CDAT
* Possibly, try to move to regular VisTrails to use new features

'''Items to Discuss'''
* 2.2 release: nothing much is pending anymore, release next week?
** [TE] vtkExporter classes [https://github.com/VisTrails/VisTrails/issues/1032 #1032]
** [RR] Hiding upgrades in version tree might make it (or might be 2.2.1 so we can test it out) [https://github.com/VisTrails/VisTrails/issues/949 #949]
** Output modules changes to go in
* add note to documentation about order of parameters in VTK
* add issue about exporter upgrades if not already there

=== March 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* 2.2 release
** Checklist on Github: https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist
** Review output modules
** RR has a couple more issues to fix
** Ready to go -- sign app package for OSX? [https://github.com/VisTrails/VisTrails/issues/984 #984] We need access to the Apple Membership team

=== March 18, 2015 ===
'''Updates'''
* [TE] VTK6 works

'''Items to Discuss'''
* [RR] Release v2.1.5 with backported tabledata?
** MTA example needs updated tabledata (for JoinTables)
** Google Maps package still not available
* [RR] Work torward v2.2.0?
** changes:
*** new persistence
*** API changes
*** output module changes (upgrades?), maintain cells but try to upgrade
*** not wrapping stuff
*** VTK6? yes
*** JobSubmission stuff?
*** relabeling for upgrades [https://github.com/VisTrails/VisTrails/issues/949 #949]
** makes sense, needs the tree view code to be updated, check selection
** See [https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist 2.2 checklist]
* Discussion of [https://github.com/VisTrails/VisTrails/issues/1016 #1016]
** plumbing between outputs and output modes, how to define a mode that works for many outputs without writing for each output?

=== March 11, 2015 ===
'''Updates'''
* [RR] persistent_archive done; merge? ([https://github.com/VisTrails/VisTrails/pull/755 #755])
** note about the focus events for widgets
** TE be aware of file_archive for future binaries that include persistent_archive
* [TE] [https://github.com/VisTrails/VisTrails/pull/998 New VTK package] finished

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails? (see last week; decision needed)
** RR email to JF about this
** yes; email sent to Github
* [RR] Switching order of output ports ([https://github.com/VisTrails/VisTrails/pull/1006 #1006])
** added port specs are sorted at a separate spot (Module.*_port_specs properties) than those in the registry (which are sorted in the registry), but those two lists are just combined without respect to sort keys
** need to determine whether the two lists should be merged or remain distinct
** should make sure that order of input ports and output ports makes parallel connections for things with same order
** DK suggests breaking backward compatibility here: workflows still run, can fix easily if a problem in an existing package.
* [RR] Question about output modes ([https://github.com/VisTrails/VisTrails/pull/1007 #1007]), how to integrate in API ([https://github.com/VisTrails/VisTrails/pull/24 #24])
** Should ImageFileMode be removed? ("image" is not a mode, "file" is)
** ImageOutput missing?
** Feel free to change how formats works
* [TE] Test suite segfaults on Fedora 17 virtualbox. Install newer version? (Support ended in 2013)

=== March 4, 2015 ===
'''Updates'''
* [TE] VTK wrapper
** Works on VTK 5.10
** Still need to test VTK 6
** New general wrappers for python functions and classes

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails?
** When [http://i.imgur.com/UTY2qfg.png filing a pull request] from UV-CDAT/VisTrails, VisTrails/VisTrails is selected by default
** People keep forgetting to change the default ([https://github.com/VisTrails/VisTrails/pull/956 #956] [https://github.com/VisTrails/VisTrails/pull/968 #968] [https://github.com/VisTrails/VisTrails/pull/999 #999] [https://github.com/VisTrails/VisTrails/pull/1000 #1000] [https://github.com/VisTrails/VisTrails/pull/1003 #1003] [https://github.com/VisTrails/VisTrails/pull/1004 #1004] [https://github.com/VisTrails/VisTrails/pull/1005 #1005])
** Only way to change that is to not have it marked as a fork of VisTrails/VisTrails
** Github staff [https://gist.github.com/remram44/b364c24ef1e462ce6e2f can make that change for us]; should we do it?
** Juliana: comments on this? visibility vs. convenience/annoyance for developers
* [RR] What about [https://github.com/VisTrails/VisTrails/issues/991 #991]?

=== February 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] vtkviewcell for infovis support, can we unify with VTKCell?
** need to test this
* [TE] vtk wrapping
** Mostly finished
** VTK 5.10 produce incorrect results with old wrapping
*** Old wrapper is based mostly on VTK 4
*** Most vtk_examples affected
*** [http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Replacement_of_SetInput]
*** should be able to upgrade from SetInput to SetInputData (need to drop GetOutput and replace with self ports)
*** can we change vtkInstance to just return self and not wrap things
** terminator example not working under 5.8?
* How does VTK wrapping fit into general wrapping framework?
* [RR] new persistence package

=== February 18, 2015 ===
'''Updates'''
* [RR] New VisTrails API and IPython integration ([https://github.com/VisTrails/VisTrails/pull/24 #24])

'''Items to Discuss'''
* [TE] VTK wrapping
** [https://gist.github.com/rexissimus/16b74693545b5e7c1035 Benchmarking vtk package]
*** Old: 24.7 seconds
*** New: 10.5 seconds (Except first time that adds 8 sec)
**** The parsing that calls is_abstract (that tries to instanciate all vtk classes) is now only run the first time.
**** get_items_from_sigstring takes 2 seconds, maybe we can use a lookup dict for already computed sigstrings?
** Now using a general python function wrapper
*** VTK classes are wrapped into python function that does not depend on vistrails
*** VTK functions can be executed without vistrails
*** The spec maps functions into vistrails modules, but can also describe wrapping
*** A general python function wrapper that supports
**** kwarg inputs
**** single, list, dict outputs
**** callback for progress reporting
**** temporary file generator for using FilePool
**** optional output generation
*** Creating specs:
***** Create spec by hand
***** Auto-create spec outline (TODO) and manually finish it
***** Dynamically create spec (VTK)
***** Implement documentation wrappers (Can use scikitlearn wrapper to wrap numpydoc) (TODO)
***** Classes as bad functions needs to be wrapped in new functions before they are wrapped. This is different for each package.
****** Classes is hard: Like VTK, and matplotlib. Scikit-learn does still not wrap classes
***** Spec diffing and patching could be done using code from matplotlib.
** Still needs upgrades from old VTK package
*** Is it possible to dynamically wrap functions, e.g, you see a SetFunc and just remove the 'Set' prefix. Or do you need to create a complete mapping?

=== February 11, 2015 ===
'''Updates'''
* Update from Friday's meeting
** discussed VisTrails internals
** discussed wrapping
*** xml discussion, hard to modify because tied to db code
*** TE has made it possible to add the schema-defined attributes to the intermediate representation
*** higher-level operations on the port specs
** make sure the simple case works
*** [JF] take a simple package with documentation and figure out what the base case for wrapping is

'''Items to Discuss'''
* [TE] VTK wrapping
** Dynamic loading works
** Reading XML is fast enough, but [https://gist.github.com/rexissimus/8272d3c776ccfa115d82 unserializing data is slow]
** Working on patterns for patching
** Matplotlib has many advanced patterns like argument ordering, nested arguments, alternateSpecs, output types.
*** Having all this in a general wrapper might confuse users?
** [RR] Delay module (except for identifiers) until you need it---e.g. don't deal with port specs, etc. until necessary
* Scripting Support [https://github.com/VisTrails/VisTrails/pull/950 #950]
** [RR] Issue with getting code from modules
** Design a simple solution
** [JF] Couldn't you use modules as black boxes without conversion, just to call into modules/subworkflows easily from e.g. IPython?
*** [RR] This is a job for the API, and a very separate use case. See [https://github.com/VisTrails/VisTrails/pull/24 #24]

=== February 4, 2015 ===
'''Updates'''

'''Items to Discuss'''
* Wrapping
** Format to use? Currently XML (like current matplotlib)
*** JSON and YAML have simple "to python dictionary" methods
*** But don't stream
*** YAML a lot easier for humans
** [DK] vtk-new-package also changes parameter names, creates enumerations
*** intermediate schema needs to be extensible
*** packages will want to store there specific infos for compute() method generation
*** also might have specs-altering info, like matplotlib's alternateSpec
** representation to code , registry already has schema for some aspects
** [RR] We might want to see if Module subclasses can be created lazily
*** no need to create all the classes just to register them in the registry and never actually use most of them
*** future effort
* [RR] Where should VisTrails packages live?
** tej installs as 'vistrailspkg.tej', TE installed it as 'userpackages.tej'
** Currently, standard packages are 'vistrails.packages.', user packages are 'userpackages.' and packages loaded through pkg_resources might be anything
** [RR] Use 'vistrailspkg.' everywhere?
** Long-term effort to simplify package distribution/installation (and have VisTrails get them automatically?)

=== January 28, 2015 ===
'''Updates'''
* T. Caswell to come visit on Fri 6 to discuss wrapping work

'''Items to Discuss'''
* [TE] New VTK wrapping
** Current code by DK seems a good deal faster
** Generates XML that can be patched/tweaked, generates Python code from it, VisTrails only loads generated Python code
** RR would rather have VisTrails load intermediate representation (= XML) directly, wants to make sure this is not slower
** The goal is to turn the intermediate step into something generic that would be used for every wrapped package (vtk, numpy, matplotlib, sklearn, java) instead of each having its own
** TC has its own code at [https://github.com/Nikea/VTTools/blob/master/vttools/wrap_lib.py github:VTTools] which parses numpy docstrings and generates modules, doesn't yet handle classes or persist anything
* Web crawler
** Right now, TE starts jobs for "start crawler", "stop crawler", "install classifier"
** RR would rather have the crawling be a job as far as VisTrails and tej are concerned
** The whole thing would be one pipeline: load examples, train classifier, start crawler [check for job, kill previous one, upload model, start processes], get snapshot, visualize
*** Need some support in tej and job submission system: long-running jobs, stop a job (wait for it to finish?), restart a job even though results are cached

=== January 21, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Unified wrapping method discussion [https://github.com/VisTrails/VisTrails/issues/991 #991]
** TE to work on reusable method with intermediate representation, starting with VTK
* [RR] Examples for scikit-learn: JF has an old example using Weka with parameter exploration (not currently in source tree)
** AM's examples are enough
* [AM] scikit-learn package is done, merge it in? [https://github.com/VisTrails/VisTrails/pull/955#issuecomment-70286788 #955]
** RR will merge
* [RR] What should copyright headers say? [https://github.com/VisTrails/VisTrails/pull/994#issuecomment-70173935 #994]
** Let's keep everything in there: Utah/Poly/NYU

=== January 14, 2015 ===
'''Updates'''
* [TE] Working on classifier
* [RR] Scripting integration, work in progress

'''Items to Discuss'''
* [RR] Unified wrapping method discussion ([https://github.com/VisTrails/VisTrails/issues/991 #991])
** Let's talk next week, [AM] and [DK] are not here

=== January 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* make sure that we address critical issues, questions, and pending review branches in a timely manner
* scripting support
** [RR] no issues if we want to just keep annotations in the generated code to allow the link back to a workflow
** [RR] can translate from workflow to script, working on script to workflow
** will work for parameter value changes, structural changes require changes to the annotations
** need to publish best practices here
** would be cool to do looping in scripts (easier interface than with workflows)
* notebook support (convert form notebook to workflow)
** RR will sync with FC on this
* Issue with console in built-from-scratch
** [TC] iPython rearranged some of the completion stuff in 2.2 and 2.3
** binary has old version of iPython -> 1.0.0, should we update?
* [TC] automated wrapping of numpy and scipy
** discovered a bunch of malformed documentation in numpy and scipy
** has github repo for vistrails tools
** example modules wrap a bunch of R stuff (not baked in, just how things are)
** will be pushing wrapping logic up
** port names forbidden (window and domain)
** have an import hook to get from yaml directly to VisTrails Modules
** should work for any python modules with well-formed numpy docstrings.
* [Action] should make it clear in documentation that Constant now means serializable not that the value doesn't change (e.g. List)
* [TC] might be interesting to try to build components of matplotlib and accumulate in figure (long-term project, but thinking about how this might work)
* [TE] build and build scripts
** completely automatic, buildbot
** need to set the build machines for the environment we want for the binary
** would virtualenv work here?
** [TC] anaconda can pin versions, potential path to test different configurations
** Q: upload nightly binary builds? A: makes sense, make sure they are well-labeled
* sourceforge stats: e.g. http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07
* package issues (see Remi's message)
* [TE] Scope of tej
** Support single ssh commands?
** Queue can be used as a remote machine (crawler is using queue.call*)
* SourceForge stats: http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07

== Older meetings ==
* [[Development/2014]]
* [[Development/2013]]
* [[Development/2012]]
* [[Development/2011]]
* [[Development/2010]]

Development

2016-05-25T14:54:10Z

Tommy: /* May 25, 2016 */

<div class="nonumtoc toclimit-1">
__TOC__
</div>

See also the [https://github.com/VisTrails/VisTrails/wiki/Development Github wiki]

== 2016 ==

=== May 25, 2016 ===

'''Updates'''
* Mailing-list fixed
* Getting stats from the "server news" mechanism (via [https://gist.github.com/remram44/7b955a0a2cfa9382f89702531d1fe6f8 parser])

'''Items to Discuss'''
* [RR] Alexis doing writeup on VisTrails, curious about interesting streaming use-cases (and potential future users)
* [TE] Union ports
** Show union ports in pipeline (DEMO)

=== May 18, 2016 ===

'''Items to Discuss'''
* [TE] mailing list still down - Julio working on it
* [TE] Improved union port
** New schema 1.0.5 adds portitem.union string attribute
** Works with pipeline view, parameter exploration view, and mashup view
** Should work well for matplotlib
** Use with VTK ports?
*** It uses [item_1,item_2] style ports usually with different tuple length.
* [TE] Remove emacs dependency from db generate [https://github.com/VisTrails/VisTrails/issues/1173 #1173]

=== May 11, 2016 ===

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]
** GUI-based solution [https://github.com/VisTrails/VisTrails/tree/union-port Branch union-port] Demo?
*** Shows single port for all ports with same sort_key
*** Select specific type when adding/showing
*** Only one type should be visible on the module at any time
*** Making tuple parameters union types is probably too complicated
*** Should work with alternate specs like matplotlib (if sort_key is defined correctly)

* [TE] Feature suggestion: Let connections connect to functions/parameters
** Show functions and parameters as ports and toggle port visibility directly for functions and parameters
** Use separate views for ports and functions (like before)
*** Allow rearranging of functions
** Pros:
*** Supports ordered connections. Create 2 functions, make them visible as ports, make connections to them.
**** We can also have, e.g., a line joining the ports on the module to indicate they are part of a list.
**** Makes List module simpler
*** Connect to parameter in tuple
*** Functions that are visible on the module can connect to an actual function, and not just to the first one it finds.
*** Can replace operation modules (in python-wrapper) in some cases for, e.g., numpy.
** Cons:
*** Interface more complicated and crowded
*** More difficult for users to grasp?
*** No immediate use case
*** Makes no union type for tuple parameters a bigger problem.

* [TE] Publish user survey?
** No response from vistrails release yet
** Not announced on vistrails-users yet.

=== May 4, 2016 ===
'''Updates'''
* VisTrails 2.2.4 released

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]

=== April 27, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Wrapping Bokeh
** New method type "operation"
*** Transforms Figure->Glyph->Output into Glyph->Figure->Output
**** Glyph sets function name and arguments as output
***** Not serializable, but should always be computed together with the subject of the operation.
**** Figure applies Glyph operation on itself
*** Useful for matplotlib?
**** matplotlib currently find actors by searching upstream?
**** But this is more difficult since matplotlib is not function-based.
** New "union" port type
*** Turns "x(float), x(list)" into "x (float, list)" and uses first set value
**** Uses only first value in tuple
**** Bokeh have many properties that support (list, string, Float)
*** Does not work with depth=1 types (e.g. Float of depth 1)
**** Turn Depth 1 types with known type into lists?

* [TE] New bugfix release
** Finalize survey

=== April 20, 2016 ===
'''Updates'''
* Merged upgrade fixes
** Now has infinite loop test
** loop test now correctly loops 5 times
*** remap_module used wrong (current) package version when creating ModuleDescriptor
* Fixed multi-step group upgrades (PR: [https://github.com/VisTrails/VisTrails/issues/1168 #1168])

'''Items to Discuss'''
* New bugfix release
** Merge usagestats
** Need to finalize survey

=== April 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Chaining upgrades done ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Replace "Upgrade" description annotation with "upgraded_from" annotation to identify which tags to hide?

* [TE] Iterating handle_invalid_pipeline ([https://github.com/VisTrails/VisTrails/pull/1165 #1165])
** Not based on [https://github.com/VisTrails/VisTrails/tree/chain-upgrades-loop chain-upgrades-loop]
** Cherry-pick test to preserve source?
** Need maxPipelineFixAttempts option?
*** The code is now smarter about recursion, so max attempts will "probably" never be reached.
** Need [https://github.com/VisTrails/VisTrails/commit/0ef0667426937eddb1d1c1e397f0657ffec039a9 debug messages]?
*** Would need to be moved into handle_invalid_pipeline

=== April 6, 2016 ===
'''Updates'''
* [TE] Query View improvements
** Done except for displaying "Version Info" and #1164
* [RR] Working on finishing new interpreter (finally!)

'''Items to Discuss'''
* [TE] Chaining upgrades ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Try latest upgrade first, then previous.
** If all fail, select latest upgrade?

=== March 30, 2016 ===
'''Updates'''

'''Items to Discuss'''

* [TE] Query View improvements
** Unified do_version_switch and get_upgrades as validate_version()
** Problems with query view using its own controller
*** Fixed module info not being displayed for query results
*** Still no version info for query results
*** Still an issue with version query view not being updated

=== March 23, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Usage reporting almost ready to go
** Need to record whether specific features are used: paramexpore, mashup, query
*** [DK] Record if LaTeX extension is used? But hard to distinguish from direct batch invocation
** How to record size of vistrail?
*** [DK] IdScope already walks over vistrail, use that
*** but total number of modules and versions doesn't give an idea of average size of individual pipelines

=== March 16, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Upgrades in Query Mode
** Now using code similar to do_version_switch
*** Uses handle_invalid_pipeline
*** Differences: Not using current_pipeline, flushes changes
*** New controller method get_pipeline optimized using cached pipelines (but not current_pipeline)
*** Integrate to avoid repeated code?
*** Use this for query mode?
* [TE] VisTrails 2.2.4 ready for release?
** tej package updated. Others?
* [JF] upgrades and the version tree
* [JF] provenance in Jupyter
* [DK] bundles: [https://github.com/VisTrails/VisTrails/pull/1092 #1092]

=== March 9, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixing search mode
** String query now matches all by default
*** This caused pipeline queries to never match
** String query can search: User/Notes/Tagname/Time/Module name
*** Should we search module names by default? (Disabled by default because it is expensive)
*** Fixed notes search
** '>' parameter queries in documentation but has been removed
** Fixed module matches for upgraded pipelines (By not upgrading pipeline)
*** Upgrades still a problem
*** Add "Upgrade all menu option?" (Or upgrade all on open when `hideUpgrades`)
*** [JF] Allow search on past tags

* [TE] Create new bugfix release
** Finish querying
** Path issue on windows

* [DK] Look into sqlalchemy and new bundle branches

=== March 2, 2016 ===
'''Updates'''
* [TE] Fixed cache bug with port specs
* [TE] VisTrails Next
** Most packages now work
** No qgis for Python 3

'''Items to Discuss'''
** Always dereference symlinks? [https://github.com/VisTrails/VisTrails/issues/1146 #1146]

=== February 23, 2016 ===
'''Updates'''
* [TE] Fixed PythonSource 100% CPU bug
* [TE] VisTrails Next
** Updated [http://opendap.co-ops.nos.noaa.gov/axis/webservices/wind/ NOAA Web Service] examples
*** Now uses REST service, tabledata, and Google Maps
*** Web Service replaced with DownloadFile

'''Items to Discuss'''
* [RR] Couple of fixes are in for API, and tej&reprounzip on the Mac binary. Also new release of tej, and working on anonymous usage reports.
** New 2.2 release soon?
* [RR] Anonymous usage reports
** Sends out info like number of modules & versions, packages used, Python & libs versions, execution time, specific features [https://github.com/VisTrails/VisTrails/pull/1154 #1154]
* [JF] Bring in noWorkflow to track variable dependencies, for the considered Jupyter integration?
* noWorkflow - provenance for python scripts
** Recent work on tracking dependencies
* Also integrates ReproZip with Jupyter
** [http://mybinder.org mybinder]
*** Use with ReproZip to automatically build Jupyter notebook interfaces
* Daves comments on Jupyter integration
** It is possible to identify cell order on the server side
** Not trivial to track order of cells on client side
* How does Galaxy workflows relate to VisTrails?
** Packaging in Galaxy is hard
** Galaxy for biomedical workflows, difficulty making it general
* Action items
** How difficult to track cell dependencies in Jupyter notebooks?
** Use noWorkflow to track cell dependencies?
** How difficult to modify mybinder to use ReproZip packages?

=== February 17, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixed Group memory usage
** Modules in groups are supposed to be freed when done executing
*** Prevented by logger that stored references to the modules (fixed, now using id(module))
*** Prevented by list iterator bug that stored list of modules on the 'self' port bug (fixed)
* [TE] VisTrails Next
** Removed deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** PythonSources will be upgraded
*** Fixes for Python < 3
*** fixes for VTK < 6
** TODOs
*** Remove RemoteQ
**** Port Hadoop to tej (Already have pbs)
*** Merge package wrapper
*** Finish SQLAlchemy branch
*** Finish new bundle branch
** [JF] Will contact Jeff and Matthias about moving to Python 3
* [JF] Query by Example is broken
* [JF] VisTrails Data Cleaning Project
** Use VisTrails to process and explore task-specific data while keeping provenance.
** Remi's Idea
*** Use VisTrails as the backend in a Jupyter notebook
*** Overcome problems with executing cells in random order
**** Interesting research topic, but little interest has yet been noted
*** Interesting to study how such a notebook would be used (Is there notebook usage data available?)
*** Impose restrictions to notebook cell boundaries
*** It will only work for functional operations
*** Can we fix, or detect, non-functional (mutating) operations?
*** Analyse code and data flow and see if it mutates data in unexpected ways?
*** Mutable operations can be created in many ways in Python
* Next meeting Tuesday 11:30

=== February 10, 2016 ===
'''Updates'''

'''Items to Discuss'''
* VisTrails Next
** Test suite passes
*** Python 3 less deterministic, module upgrade order random.
** [RR] updating packages: Reprounzip (pushed), tej, persistent_archive, ...
** All of our packages should run fine :)
** VTK thumbnail comparison works
*** Rendering bug on some systems
**** QVTKCell now inherits QGLWidget
*** Old thumbnails had wrong height due to spreadsheetwindow being too small
**** Fixed by regenerating thumbnails
*** Silenced deprecation messages when generating modules
*** Many new classes in VTK 7
** Remove deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** Will break existing PythonSources
**** Try to upgrade?
*** Old-style packages
**** Or only allow a new style, like __init__.py renamed to info.py? (merge with identifiers.py?)
***** Read info.py without importing package?
*** Fixes for Python < 3
*** Fixes for Qt < 5
*** fixes for VTK < 7
*** Remove self port?

=== February 3, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] [http://lists.vistrails.org/pipermail/vistrails-users/2016-January/000402.html Rendering a .pvd (ParaView) file?]

* VisTrails Next
** All tests but thumbnail comparison passes
** Still issues with gui and more packages needs to be tested
** PythonSource and MplSource upgraded with lib2to3
** Keep contrib packages? Update?
** [https://blog.kitware.com/vtk-7-0-0/ VTK 7 is released]
*** Supports Python 3
*** Will hopefully get into conda and others soon
*** Deprecates a bunch of modules

* [https://travis-ci.org/VisTrails/VisTrails/builds/106743348 Travis builder] for VisTrails Next
** Runs!
** Uses conda
*** Many levels of requirements
**** apt packages
**** conda packages
**** python packages in requirements.txt
**** python packages in setup.py
*** Can probably drop conda. Default builder does not have Qt5, but beta builder do!
*** But useful if we want to use conda in our own build process.
** Lots of errors I do not get locally?

* [http://goo.gl/forms/Z4HBrwaBWL User Survey]
** Have you used any alternatives to vistrails?
*** Relevant? More options?
** How often do you use any of these particular features in VisTrails?
*** Add/Remove alternatives?
** How important would you rank the following potential improvements to VisTrails?
*** Add alternatives?

=== January 27, 2016 ===
'''Updates'''
* New interpreter
** Working prototype soon
** Looping not completely done (and port combination mode: pairwise/cartesian...)
** Need to integrate with VisTrails
*** Compatibility with existing modules
*** Use log controller
*** Want to cache at multiple levels (whole stream/single element of stream)
*** Non-runtime attributes of modules (cache check, automatic conversion check, constant from/to string)

'''Items to Discuss'''
* User Survey

* ZMQ failing on windows (vistrails-users)

* [TE] [https://github.com/VisTrails/VisTrails/pull/1143 Python 3 branch]
** Testsuite almost passes
*** Failing are unicode filenames, some users guide examples, and thumbnail comparisons.
** Fixed issues
*** Signatures are now bytes (convert to string to show in widget)
*** Cannot compare different types, e.g., (None < 1)
**** PortSpec.depth and min/maxConn could be None. (Backport!)
**** cell.row could be None
*** Lots of unicode/bytes fixes to serializations
**** We have encryption implementations in the code! (keychain)
*** Lots of small fixes to package method differences
** Current issues
*** logging widget empty?
*** version tree signals messed up
*** provenance view legend icons black
*** Text do not fit in some widgets
*** VTK thumbnail comparison fails
**** VTK Cells have some faces in wrong direction?
**** Because running in VM?
** Installing on Ubuntu LTS/Latest Mint
*** Install latest matplotlib from pip
*** Install VTK 7.0.0rc2 from source
*** No QtWebEngine binary (controversial) (Must install sip/PyQt5/Qt5 from source)

=== January 20, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Backporting features from Python 3 + PyQt5 + Qt5
** Merged unicode with master ([https://github.com/VisTrails/VisTrails/tree/unicode unicode])
*** One unicode test failing
*** Problem saving to xml
** Used [http://python-future.org/ python-future] to run futurize stage 1 to update legacy (pre 2.6) code ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized unicode-futurized])
*** Updates print to functions 'from __future__ import print_function'
*** Updates exception calls to use 'as'
*** removes most usages of 'long' (mostly used unnecessarily)
**** Only needed for 32-bit support
*** Fixes relative imports (from __future__ import absolute_import)
** Fixing code that is deprecated in Qt 4.8 and removed in Qt 5 ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized-qt5 unicode-futurized-qt5])
*** Updated all signals to new-style
* If we go 2 to 3, this could break packages
** means we should schedule any package format changes for the same time
** e.g., imports should be unrelated to code path (function to load module from package identifier?) (take them out of vistrails.* [https://github.com/VisTrails/VisTrails/pull/1002 #1002])
** any structural changes (e.g. the __init__ versus init thing) (RR thinks it makes sense, though having both named "init" is unfortunate)
** putting package identifier as xml?
*** Python not so bad, plus some stuff in there is Python code (checking dependencies)
** version the APIs?
*** RR planning on versioning vistrails_module.Module, no point versioning the whole package?
* file formats on 2 to 3:
** no real translation/upgrade, but non-ascii values that work on 3 won't load in 2

=== January 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://gist.github.com/rexissimus/dfd27e466427529c385c Porting to Python 3 / PyQt5]
** Basic GUI and execution works
** Minimal work to support 2to3
** Hard to support both PyQt4 and PyQt5

=== January 6, 2016 ===
'''Updates'''
'''Items to Discuss'''
* Updating VisTrails dependencies
** Successfully built [https://gist.github.com/rexissimus/f1a1aada7de1c00a57c7 Win7-64/Python3/PyQt5/Qt5/WebEngine/VTK7]
*** VTK 7 is the first supporting Python 3 but is only in release candidate phase.
**** Next version of VTK 6 is rumored to support Python 3
**** There is a development branch of VTK 6 supporting Python 3
*** Can travis build this?
**** We can skip tests for WebEngine and VTK if needed
** Python 3 [https://python3wos.appspot.com/ showstoppers]
*** No MySQL-python (sqlalchemy supports mysql through other drivers)
*** No suds (there are active forks but we could also drop support?)
* Options for python2/3 support:
** Interpreter could be python2/python3 based on packages
** six layer works but not the easiest to maintain (e.g. in reprozip)
* Drop support for win-64
* Update copyright headers to 2016

== 2015 ==

=== December 30, 2015 ===
'''Updates'''
* Bokeh package finished
** Can output to Browser/IPython/Spreadsheet (Limited functionality in spreadsheet)
'''Items to Discuss'''
* Updating VisTrails dependencies
** Bokeh needs QWebEngine (Chromium) in Qt5 which requires PyQt5
*** Many plotting libraries only work in browsers
*** But Chromium may be a big and controversial dependency
*** Or create a browser version of the spreadsheet?
** Some users have requested Python 3
** Not backwards compatible?
** Target for VisTrails 3.0 with new interpreter?

=== December 16, 2015 ===
'''Updates'''
'''Items to Discuss'''
* Users list question
* [TE] Wrapping Bokeh
** Added bokeh property parser
*** complements numpydoc parser
*** Not all attributes are available, partially because I am using a pre-release version.
** Wrapped modules
*** bokeh.plotting finished (Backwards like matplotlib: Create plot then draw on it)
*** bokeh.charts mostly done (Missing arguments)
** QWebView mostly works (but no zooming or buttons)
*** It would be better to use external browser or QWebEngineView
** Added improvements to wrapper
*** Generalized port translations (Color/Path to native types)
*** Can use multiple docstring/property parsers simultaneously

=== December 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Looking into wrapper
** Will port TensorFlow
** Doing a pass on the wrapper code & doc
*** UX improvements
** Factorize high-level docstring parsers into core.wrapper? (sphinx, numpy, google)
** Problem with name vs module_name (fails sklearn tests because class_by_name() is broken)
** Looking into compressing specs, lazy registration of modules

=== December 2, 2015 ===
'''Updates'''
* [TE] Package wrapping
** Wrapped most of numpy/scipy using __all__
** Added class attribute and method access for classes (Can add to class or to separate inspector module)
** TODO: Document wrapping procedure

'''Items to Discuss'''

=== November 25, 2015 ===
'''Updates'''
* [RR] New interpreter is coming along
** Everything is a stream
** Task system, eventually work-stealing parallelism
** Streams no longer advance in lock-step
*** Allows for constructions like filter, join, sorted-merge
** depth>1 still to be tested, no current plan to allow this through the module interface
*** Through looping though, can do streams of streams

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapped most numpy functions (no polynomials)
** and half of scipy classes and functions
** Added functions manually from documentation (no parseable lists?)
** Focusing on data flow constructs (no property/method access for classes)
*** Using spec diff (empty for now) and dynamic parser (stores spec in .vistrails/)
** Python class/function wrapper now stable
** Add google doc parser?
*** Is there a parser available?

=== November 18, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Numpy class wrapping works
*** Basic type is List, since most types are array_likes.
*** TODO: More classes and functions
*** Some operations are in-place and some aren't, and docstring not super clear
*** [RR] It seems only methods mutate, and most have a numpy.xx function equivalent; just manually go through the methods and remove the mutating ones?
** Class wrapper is modular
*** Docstring parser and type string parser can be customized
*** Classes can have optional attribute/method ports
**** Inspectors and attribute/method modules can be created separately
** Use PythonCalc as an example
*** Can be re-implemented as a function with a parseable docstring
*** [RR] PythonCalc is just an example, and it might actually make sense to get rid of it, or do a proper math package with scalar operations (as separate modules, no combobox)
** [RR] TensorFlow to use wrapping as well
*** Very simple (only types 'tensor' & 'variable')

=== November 11, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapping numpy's classes using numpydoc (ndarray)
*** Wrapping constructor arguments, attribute getters/setters as module ports
**** Then how to access attributes afterwards?
***** Use input value port to class modules?
*** Wrap methods as modules? E.g., `ndarray.shape`.
*** Function wrapping is almost a subset of class wrapping
**** May be able to use the same parsing/execution methods
** VTK's non-getter/setter methods could be wrapped as modules
*** We could then remove extra logic in interpreter for keeping function order
** Bokeh uses autogenerated docstrings
*** We may be able to read the specification directly

* [RR] [https://github.com/VisTrails/VisTrails/pull/1138 TensorFlow package]
** Basic setup working, can execute the Mandelbrot example
** Will autogenerate the operations

=== November 4, 2015 ===
'''Updates'''
* [RR] Interpreter work requires a fix for [https://github.com/VisTrails/VisTrails/issues/1137 DB issue #1137]
* [DK] Kitware's Resonant [http://www.kitware.com/source/home/post/173]
** [https://github.com/girder/girder Girder]: data management system
** [https://github.com/Kitware/romanesco Romanesco]: execution engine, uses [http://www.celeryproject.org/ Celery] for task management
** Resonant Flow: web app for editing and executing workflows

'''Items to Discuss'''
* [TE] Added OSX Lion (10.7) VM on build machine using vagrant (seems ok with license?)
** New builds works on Lion
** Change the minimum requirement to 10.7?
* [TE] Package wrapping
* Added upgrade suggestions using 2 spec versions ([http://pastebin.com/30XUU8Gp example])
** using name edit distance to find matches
** Could use something better like port similarity for modules, and type similarity for ports
** Should write python upgrade code?
** Added spec to sklearn package
*** Can now diff spec versions and keep the spec static
*** There will be problems with downgrades and package versions

=== October 29, 2015 ===
'''Updates'''
* [TE] nightly-build-mac fixed (Needed to approve xcode license)

'''Items to Discuss'''
* [TE] matplotlib wrapper
** ported to general spec
** Diff can be used on general spec
*** Only needed minor changes
*** Fixed indexing bug that corrupted specs
*** Can now move diff tools to core/wrapper
** Add new plots?
*** New plots in mpl 1.3: eventplot
*** New plots in mpl 1.4: angle_spectrum, magnitude_spectrum, phase_spectrum', violinplot
*** No new plots in mpl 1.5 (from looking at boilerplate.py)

=== October 21, 2015 ===
'''Updates'''
* [RR] Alexis has arrived, will be working with [RR] on a more efficient interpreter

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package]
** Supporting multiple package versions
*** Check which version can be loaded [https://github.com/VisTrails/VisTrails/pull/1135 #1135]
*** We cannot show version requirements in the list of packages because old packages are loaded when importing the codepath
** Visual diff does not work well, but we can use the spec differ to see differences.
** Unifying vtk and matplotlib wrapping specs (WIP)
*** And porting matplotlibs spec differ to work on the general spec
*** Spec differ can then be used on vtk and other packages in the future
*** Will enable automatic upgrade generation
* [RR] Rework interpreter
** restore abstraction between interpreter/module code
** build looping, streaming, caching into the interpreter
** rework cache
** look into parallelism once basic functionality is there

=== October 14, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package] (adding numpydoc parser)

=== October 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/tree/fix-matplotlib-parser New matplotlib parser] (adding numpydoc parser)
** Added numpydoc attribute parser for plots.
*** TODO: Need better port spec reconciliation with call signature parser.
*** We can create a general numpydoc parser, but attribute types are unique to matplotlib.
** Needs package versioning
*** New spec will not support matplotlib < v1.4 due to changed path to axes classes.
*** Load spec version corresponding to installed matplotlib version?
*** Need version downgrades?

=== September 30, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Updating Matplotlib parser
** Matplotlib docstring parser fails on numpy docstrings
** I have [https://github.com/VisTrails/VisTrails/commit/eae8b0c16260810587e47c41cab53552cbb3cf0a added basic numpydoc parsing]
*** Only used by a few docstrings so far
*** Parsing uses many sources (class tables, signatures, ACCEPTS, method docstrings, definition parsing).
** Caswell said they were thinking about moving to traitlets, but this is not ready yet

=== September 23, 2015 ===
'''Updates'''
* [TE] VisTrails 2.2.3 released
** Also have pushed to PyPI, binstar, etc.
** Sourceforge vs. GitHub
*** should be able to host releases on GitHub
*** nightly binaries pushed to sf each night
*** old binaries?
* [TE] Re-wrapping MatPlotlib
** Keep static generation - Docstrings are brittle beween matplotlib versions
** Keep generating the executable classes - but create functions, not vistrails Modules
*** Why is there so much patching?
** Re-implemented Alternate PortSpec for InputPortSpec
*** It will now inherit specs from parent (No need to reimplement)
** Module upgrades?

'''Items to Discuss'''

=== September 16, 2015 ===
'''Updates'''
* [TE] Job Monitor tests and documentation done
** OK to leave document package in packages directory?

'''Items to Discuss'''
* [TE] Library wrapping: How to do code patching? [https://docs.google.com/drawings/d/1Sh3eOXot6v2y880jHKQrqXqAwr-0aoqYligg3z8G8MY/edit?usp=sharing Wrapping diagram]
** Insert code into module template (Old VTK code)
** Patch the library that is called (New VTK code)
** Somehow store code in spec and apply when executed?
*** Executed code needs at a minimum access to inputs, outputs, current class
*** Use standard input/output dict and obj reference that the code operates on?
*** Can this be done while keeping the execution abstract?

* Do new release now?

=== September 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* New release?
** [RR] wants reprounzip
** tej changes & doc
** job monitor & jobmixin fixes
** mongodb
** reprounzip
** warning: MplFigure type is int
** tabledata: add Reshape, DictoToTable & ListToTable, fix ListToTable with numpy arrays
** PythonSource can have same name for an input & output
** don't show spreadsheet at exit

=== September 2, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Limit autosaves? [https://github.com/VisTrails/VisTrails/pull/1126 #1126]

=== August 26, 2015 ===
'''Updates'''
* [TE] Added Job support to Parameter Explorations (Requested by Colin), and Mashups
** specify job ids, need to specify different ids for parameter explorations since they have the same version id
** how to deal with parameters passed in on command line
* [General] provenance: should be creating a new version when we execute workflow with changed parameters?
** currently, custom_params annotation stores this in provenance currently
** [RR] API doesn't record provenance if passing in parameters: http://git.io/vsAA5
'''Items to Discuss'''

=== August 19, 2015 ===
'''Updates'''
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [TE] Working on Job Monitor documentation

'''Items to Discuss'''
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [TE] Stop testing VisTrails 2.0?

=== August 12, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Build broken on Travis; because of IPython 4 released today? ([https://travis-ci.org/VisTrails/VisTrails/builds/75279795 build 992]; [https://github.com/VisTrails/VisTrails/issues/1123 #1123])

=== August 5, 2015 ===
'''Updates'''
* [TE] Fixes to Jobs
** Could not delete jobs
** Could not run job in group
** Job not reset when calling ModuleSuspended
** Added deleting job from context menu
* [RR] Writing documentation for everything [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

'''Items to Discuss'''

=== July 29, 2015 ===
'''Updates'''
* RR still looking into new interpreter thing
** Goal is to take out scheduling logic from Module so it can be split in multiple processes, and so that smarter strategies can be added in time
** This means some work on packages
** Spreadsheet can live in kernel process? Still some UI stuff that will take work (changing configuration, persistent archive's viewer, ...)
* [TE] Problems running examples [https://github.com/VisTrails/VisTrails/pull/1111 #1111]
** Testing of more examples requires additional packages on the test machines.
** Fixed faulty line-ending in PythonSource:s failing on Python 2.6.
** Test suite now testing SUDSWebServices (If web service is down, test suite will fail)
** preferences.py test failed reloading 'dialogs' package, switched to using 'URL'.

'''Items to Discuss'''

=== July 22, 2015 ===
'''Updates'''
* [TE] mailing lists back online
* [TE] Working on [https://github.com/VisTrails/VisTrails/issues/1107 #1107]
* [RR] Working on ReproZip package

'''Items to Discuss'''
* [RR] MongoDB package [https://github.com/VisTrails/VisTrails/pull/1106 #1106]
* [RR] Example for tej docs? [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

=== July 15, 2015 ===
'''Updates'''
* 2.2.2 released

'''Items to Discuss'''
* RR is considering executing everything in an IPython kernel (i.e. separate Python interpreter, like the one spawned for a notebook)
** It's a separate process that we can restart without restarting the app/gui
** We can isolate the execution environment (e.g. for the server)
** We can run the whole thing remotely (if your data is elsewhere, just run VisTrails locally and the pipeline elsewhere)
** Pipeline execution no longer makes the interface hang, it just makes the kernel hang (but that's fine)
** We can use notebooks as modules (probably way nicer than the PythonSource module)
** We can run multiple kernels so long as the ports carry things that are serializable
*** meaning we can put the multithreaded-interpreter without all the hacky parts it has now
*** we can run IPython kernels in all the languages IPython supports, [https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages currently 46]

=== July 8, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Buildbot github hook not working after IP address change
* [TE] No reference to VistrailsApplication ([https://github.com/VisTrails/VisTrails/issues/1103 #1103])
** [RR] Added PR [https://github.com/VisTrails/VisTrails/pull/1104 #1104]
* [TE] Reopening VT file after saving with bundled subworkflow won't offer subworkflow upgrade ([https://github.com/VisTrails/VisTrails/issues/1102 #1102])
** allow manual delete to fix right now
** fix this on top of the use-uuid branch
* [TE] Release VisTrails 2.2.1? ([https://github.com/VisTrails/VisTrails/blob/v2.2/CHANGELOG CHANGELOG])
** [https://github.com/VisTrails/VisTrails/pull/1093 output-modules-use-global-dir]
** [https://github.com/VisTrails/VisTrails/milestones/version%202.2 Current issues for 2.2]

=== July 1, 2015 ===
'''Updates'''
* [TE] PROV fixed
* [TE] Working on subworkflow issues
* [RR] Considering reworking the controller (log vs exception problem, retained upgrades causing interferences) and also the interpreter (IPython?)

'''Items to Discuss'''

=== June 24, 2015 ===
'''Updates'''

'''Items to Discuss'''
* UV-CDAT
* [TE] Can a cyclic workflow be valid? ([https://github.com/VisTrails/VisTrails/issues/1097 #1097])
** focus on disabling the ability to create cyclic pipelines because more things break than just this with a cyclic pipeline
* [RR] Relative paths ([https://github.com/VisTrails/VisTrails/pull/1057 #1057])
** This interacts with the new bundle; how do handle packing files inside the VT bundle?

=== June 17, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] current_version and reusing existing upgrades are broken ([https://github.com/VisTrails/VisTrails/issues/1095 ticket #1095])
** Could be that export to PROV is using an unflushed upgrade pipeline?
** current_version would then be correct.
** It may work to flush the actions before exporting?

=== June 10, 2015 ===
'''Updates'''
* DAT: fixed VTK issue on Linux and Mac
* Still crashes on Windows. Need help! Reminder: this works in the VisTrails spreadsheet (QCellPresenter), although no widget get changed there during a drag
** Is it a VTK bug?
** Is it simply impossible to change widgets during the drag, should we do it a different way?
** Did I miss something that is done in VisTrails but somehow not in DAT?
** Low prio, UV-CDAT doesn't run on Windows anyway

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 Updated pull request])
* Single instance code and batch mode

=== June 3, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 pr])
** Requires fixes to command line parameters, Output modules, and batch mode
** How to test this
** Updated missing/outdated flags
** Fixed view issues when generating graphs
* [TE] batch mode
** SpreadsheetOutput not enabled in batch mode. Should we check is_running_gui instead?
** Other instance setting flags from caller
** Is graphsAsPdf replacing spreadsheetDumpPdf?
** graphsAsPdf true by Default?
** Batch mode executing by default (Not needed when generating graphs)
** Re-added workflowInfo as withWorkflowInfo for writing graph and xml workflow
** [DK] batch mode should be outputting to files or stdout, shouldn't always trigger SpreadsheetMode
** execute flag, maybe make execution the default and allow a "--no-execute" if you only want to capture graphs, for example

=== May 27, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] API question
** http://lists.vistrails.org/pipermail/vistrails-users/2015-May/000357.html
* Status of DAT
** Can add VCS plot to DAT but need to work on configuration windows
** Documentation for graphics templates for UV-CDAT/vcs?
* Qt support?

=== May 20, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Reviving the DAT, integrating scripting & porting UV-CDAT!
** On [https://github.com/VisTrails/DAT GitHub] ([https://github.com/VisTrails/DAT/issues issues])
** Merging 2 years of development taking longer than expected, but getting there. The plan is to get the patches in VisTrails and never fork again, we never want to get in UV-CDAT's situation (and don't need to).
** VTK cell works fine on Linux but there was flickering on Mac & Windows before; still issues on Mac (Windows status unknown)
** Can get a VCS plot soon (but will need VTK cell fix)
** Integrate in UV-CDAT's build system (so we have cdms, VCS, ...) -> RR can do this, low priority
** How do we integrate scripting?
*** We want to be able to seamlessly make changes to a plot by changing Python code
*** Define new plots by entering Python code without writing modules/packages?
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 13, 2015 ===
'''Updates'''
* [RR] Test skipping whitelist ([https://github.com/VisTrails/VisTrails/pull/1069 #1069]) -- low priority
* [RR] Custom matplotlib modules can't be compatible with both 2.1 and 2.2 ([https://github.com/VisTrails/VisTrails/issues/1067 #1067]); should be fixed for ALPS ([https://github.com/VisTrails/VisTrails/issues/1070 #1070])

'''Items to Discuss'''
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 7, 2015 ===
'''Updates'''
* [RR] Export/import workflow to Python working!

'''Items to Discuss'''
* [Claudio] UV-CDAT
** The UV-CDAT project is the biggest user base of VisTrails
** VisTrails package management provides a lot of friction towards people plugging in their code
** Need to make it easy to integrate your random Python scripts in the system without having to deal with all the boilerplate, at least in the first step
** [RR] argues that modules are still good; UV-CDAT shouldn't move towards a purely script-based backend
** [RR] export/import with Python could reduce a lot of that friction by allowing 1) to edit workflow as Python 2) to open up boxes automatically if needed code doesn't match actual modules
** ...

=== April 29, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] <strike>Abstractions</strike> subworkflows status ([https://github.com/VisTrails/VisTrails/labels/subworkflows tickets])
* [RR] matplotlib compatibility (2.1 & 2.2), [https://github.com/VisTrails/VisTrails/issues/1067 #1067]
** RR to try and fix ALPS matplotlib modules

=== April 22, 2015 ===
'''Updates'''
* 2.2.0 has been released!
* Windows issue (via email from Ryan)
** issue with manifest file (may be a new file in VTK6?)
** Tommy has regenerated new Windows builds
* Binaries, pypi, and conda released
* [RR] Export as script
* Python sources using VTK need to switch to SetInputData (users should be aware of this)

=== April 15, 2015 ===
'''Updates'''
* Ready for 2.2.0 (apart from binary/deps issues)
** Missing some libs (scikit-learn, tej, tdparser, SQLAlchemy+connectors
** Windows: runvistrails.py is no longer used, so the PATH is wrong
** Windows: pip is broken, but it probably wouldn't work anyway because of permission issues (disable this?)
* Queries, upgrades and getPipeline() usage ([https://github.com/VisTrails/VisTrails/issues/1054 #1054])
** Getting a pipeline with getPipeline() is not safe: it might return an invalid pipeline
** This is used in many places throughout the code, like queries
** Upgrading would require going through the controller, but that creates new actions
* [TC] Avoid copying a module's output if it's used as input by exactly one downstream module ([https://github.com/VisTrails/VisTrails/issues/1060 #1060]) (useful for big numpy arrays you can update in-place)

=== April 8, 2015 ===
'''Updates'''
* [DK] Merged RR's changes for output modules (1012 and 1013)
** RR will merge remaining changes, then create v2.2 branch!

'''Items to Discuss'''
* BNL need numpy array to VTK image
** Looks like VTK has some helpers for this
** We will help if issues arise
** Will contribute back to VisTrails package
* Upgrade issue: [https://github.com/VisTrails/VisTrails/issues/1017 #1017]
** Automatic upgrades should happen between versions of provided upgrades
** Our existing upgrades work around this so it doesn't need to be 2.2.0
* Corner-case VTK modules
** No longer need VTKCell input port, so don't interfere with registry and API anymore
** Still work weirdly, people probably shouldn't use them
** But we have lots of clunky modules since we wrap the whole of VTK; some people might rely on this and know how to use them, let's keep them anyway
** Ready for 2.2.0

=== April 1, 2015 ===
'''Updates'''
* [RR] UV-CDAT: bugfixing for 2.2, long-term plans: implement scripting import/export in VisTrails, port to UV-CDAT
* Possibly, try to move to regular VisTrails to use new features

'''Items to Discuss'''
* 2.2 release: nothing much is pending anymore, release next week?
** [TE] vtkExporter classes [https://github.com/VisTrails/VisTrails/issues/1032 #1032]
** [RR] Hiding upgrades in version tree might make it (or might be 2.2.1 so we can test it out) [https://github.com/VisTrails/VisTrails/issues/949 #949]
** Output modules changes to go in
* add note to documentation about order of parameters in VTK
* add issue about exporter upgrades if not already there

=== March 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* 2.2 release
** Checklist on Github: https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist
** Review output modules
** RR has a couple more issues to fix
** Ready to go -- sign app package for OSX? [https://github.com/VisTrails/VisTrails/issues/984 #984] We need access to the Apple Membership team

=== March 18, 2015 ===
'''Updates'''
* [TE] VTK6 works

'''Items to Discuss'''
* [RR] Release v2.1.5 with backported tabledata?
** MTA example needs updated tabledata (for JoinTables)
** Google Maps package still not available
* [RR] Work torward v2.2.0?
** changes:
*** new persistence
*** API changes
*** output module changes (upgrades?), maintain cells but try to upgrade
*** not wrapping stuff
*** VTK6? yes
*** JobSubmission stuff?
*** relabeling for upgrades [https://github.com/VisTrails/VisTrails/issues/949 #949]
** makes sense, needs the tree view code to be updated, check selection
** See [https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist 2.2 checklist]
* Discussion of [https://github.com/VisTrails/VisTrails/issues/1016 #1016]
** plumbing between outputs and output modes, how to define a mode that works for many outputs without writing for each output?

=== March 11, 2015 ===
'''Updates'''
* [RR] persistent_archive done; merge? ([https://github.com/VisTrails/VisTrails/pull/755 #755])
** note about the focus events for widgets
** TE be aware of file_archive for future binaries that include persistent_archive
* [TE] [https://github.com/VisTrails/VisTrails/pull/998 New VTK package] finished

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails? (see last week; decision needed)
** RR email to JF about this
** yes; email sent to Github
* [RR] Switching order of output ports ([https://github.com/VisTrails/VisTrails/pull/1006 #1006])
** added port specs are sorted at a separate spot (Module.*_port_specs properties) than those in the registry (which are sorted in the registry), but those two lists are just combined without respect to sort keys
** need to determine whether the two lists should be merged or remain distinct
** should make sure that order of input ports and output ports makes parallel connections for things with same order
** DK suggests breaking backward compatibility here: workflows still run, can fix easily if a problem in an existing package.
* [RR] Question about output modes ([https://github.com/VisTrails/VisTrails/pull/1007 #1007]), how to integrate in API ([https://github.com/VisTrails/VisTrails/pull/24 #24])
** Should ImageFileMode be removed? ("image" is not a mode, "file" is)
** ImageOutput missing?
** Feel free to change how formats works
* [TE] Test suite segfaults on Fedora 17 virtualbox. Install newer version? (Support ended in 2013)

=== March 4, 2015 ===
'''Updates'''
* [TE] VTK wrapper
** Works on VTK 5.10
** Still need to test VTK 6
** New general wrappers for python functions and classes

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails?
** When [http://i.imgur.com/UTY2qfg.png filing a pull request] from UV-CDAT/VisTrails, VisTrails/VisTrails is selected by default
** People keep forgetting to change the default ([https://github.com/VisTrails/VisTrails/pull/956 #956] [https://github.com/VisTrails/VisTrails/pull/968 #968] [https://github.com/VisTrails/VisTrails/pull/999 #999] [https://github.com/VisTrails/VisTrails/pull/1000 #1000] [https://github.com/VisTrails/VisTrails/pull/1003 #1003] [https://github.com/VisTrails/VisTrails/pull/1004 #1004] [https://github.com/VisTrails/VisTrails/pull/1005 #1005])
** Only way to change that is to not have it marked as a fork of VisTrails/VisTrails
** Github staff [https://gist.github.com/remram44/b364c24ef1e462ce6e2f can make that change for us]; should we do it?
** Juliana: comments on this? visibility vs. convenience/annoyance for developers
* [RR] What about [https://github.com/VisTrails/VisTrails/issues/991 #991]?

=== February 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] vtkviewcell for infovis support, can we unify with VTKCell?
** need to test this
* [TE] vtk wrapping
** Mostly finished
** VTK 5.10 produce incorrect results with old wrapping
*** Old wrapper is based mostly on VTK 4
*** Most vtk_examples affected
*** [http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Replacement_of_SetInput]
*** should be able to upgrade from SetInput to SetInputData (need to drop GetOutput and replace with self ports)
*** can we change vtkInstance to just return self and not wrap things
** terminator example not working under 5.8?
* How does VTK wrapping fit into general wrapping framework?
* [RR] new persistence package

=== February 18, 2015 ===
'''Updates'''
* [RR] New VisTrails API and IPython integration ([https://github.com/VisTrails/VisTrails/pull/24 #24])

'''Items to Discuss'''
* [TE] VTK wrapping
** [https://gist.github.com/rexissimus/16b74693545b5e7c1035 Benchmarking vtk package]
*** Old: 24.7 seconds
*** New: 10.5 seconds (Except first time that adds 8 sec)
**** The parsing that calls is_abstract (that tries to instanciate all vtk classes) is now only run the first time.
**** get_items_from_sigstring takes 2 seconds, maybe we can use a lookup dict for already computed sigstrings?
** Now using a general python function wrapper
*** VTK classes are wrapped into python function that does not depend on vistrails
*** VTK functions can be executed without vistrails
*** The spec maps functions into vistrails modules, but can also describe wrapping
*** A general python function wrapper that supports
**** kwarg inputs
**** single, list, dict outputs
**** callback for progress reporting
**** temporary file generator for using FilePool
**** optional output generation
*** Creating specs:
***** Create spec by hand
***** Auto-create spec outline (TODO) and manually finish it
***** Dynamically create spec (VTK)
***** Implement documentation wrappers (Can use scikitlearn wrapper to wrap numpydoc) (TODO)
***** Classes as bad functions needs to be wrapped in new functions before they are wrapped. This is different for each package.
****** Classes is hard: Like VTK, and matplotlib. Scikit-learn does still not wrap classes
***** Spec diffing and patching could be done using code from matplotlib.
** Still needs upgrades from old VTK package
*** Is it possible to dynamically wrap functions, e.g, you see a SetFunc and just remove the 'Set' prefix. Or do you need to create a complete mapping?

=== February 11, 2015 ===
'''Updates'''
* Update from Friday's meeting
** discussed VisTrails internals
** discussed wrapping
*** xml discussion, hard to modify because tied to db code
*** TE has made it possible to add the schema-defined attributes to the intermediate representation
*** higher-level operations on the port specs
** make sure the simple case works
*** [JF] take a simple package with documentation and figure out what the base case for wrapping is

'''Items to Discuss'''
* [TE] VTK wrapping
** Dynamic loading works
** Reading XML is fast enough, but [https://gist.github.com/rexissimus/8272d3c776ccfa115d82 unserializing data is slow]
** Working on patterns for patching
** Matplotlib has many advanced patterns like argument ordering, nested arguments, alternateSpecs, output types.
*** Having all this in a general wrapper might confuse users?
** [RR] Delay module (except for identifiers) until you need it---e.g. don't deal with port specs, etc. until necessary
* Scripting Support [https://github.com/VisTrails/VisTrails/pull/950 #950]
** [RR] Issue with getting code from modules
** Design a simple solution
** [JF] Couldn't you use modules as black boxes without conversion, just to call into modules/subworkflows easily from e.g. IPython?
*** [RR] This is a job for the API, and a very separate use case. See [https://github.com/VisTrails/VisTrails/pull/24 #24]

=== February 4, 2015 ===
'''Updates'''

'''Items to Discuss'''
* Wrapping
** Format to use? Currently XML (like current matplotlib)
*** JSON and YAML have simple "to python dictionary" methods
*** But don't stream
*** YAML a lot easier for humans
** [DK] vtk-new-package also changes parameter names, creates enumerations
*** intermediate schema needs to be extensible
*** packages will want to store there specific infos for compute() method generation
*** also might have specs-altering info, like matplotlib's alternateSpec
** representation to code , registry already has schema for some aspects
** [RR] We might want to see if Module subclasses can be created lazily
*** no need to create all the classes just to register them in the registry and never actually use most of them
*** future effort
* [RR] Where should VisTrails packages live?
** tej installs as 'vistrailspkg.tej', TE installed it as 'userpackages.tej'
** Currently, standard packages are 'vistrails.packages.', user packages are 'userpackages.' and packages loaded through pkg_resources might be anything
** [RR] Use 'vistrailspkg.' everywhere?
** Long-term effort to simplify package distribution/installation (and have VisTrails get them automatically?)

=== January 28, 2015 ===
'''Updates'''
* T. Caswell to come visit on Fri 6 to discuss wrapping work

'''Items to Discuss'''
* [TE] New VTK wrapping
** Current code by DK seems a good deal faster
** Generates XML that can be patched/tweaked, generates Python code from it, VisTrails only loads generated Python code
** RR would rather have VisTrails load intermediate representation (= XML) directly, wants to make sure this is not slower
** The goal is to turn the intermediate step into something generic that would be used for every wrapped package (vtk, numpy, matplotlib, sklearn, java) instead of each having its own
** TC has its own code at [https://github.com/Nikea/VTTools/blob/master/vttools/wrap_lib.py github:VTTools] which parses numpy docstrings and generates modules, doesn't yet handle classes or persist anything
* Web crawler
** Right now, TE starts jobs for "start crawler", "stop crawler", "install classifier"
** RR would rather have the crawling be a job as far as VisTrails and tej are concerned
** The whole thing would be one pipeline: load examples, train classifier, start crawler [check for job, kill previous one, upload model, start processes], get snapshot, visualize
*** Need some support in tej and job submission system: long-running jobs, stop a job (wait for it to finish?), restart a job even though results are cached

=== January 21, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Unified wrapping method discussion [https://github.com/VisTrails/VisTrails/issues/991 #991]
** TE to work on reusable method with intermediate representation, starting with VTK
* [RR] Examples for scikit-learn: JF has an old example using Weka with parameter exploration (not currently in source tree)
** AM's examples are enough
* [AM] scikit-learn package is done, merge it in? [https://github.com/VisTrails/VisTrails/pull/955#issuecomment-70286788 #955]
** RR will merge
* [RR] What should copyright headers say? [https://github.com/VisTrails/VisTrails/pull/994#issuecomment-70173935 #994]
** Let's keep everything in there: Utah/Poly/NYU

=== January 14, 2015 ===
'''Updates'''
* [TE] Working on classifier
* [RR] Scripting integration, work in progress

'''Items to Discuss'''
* [RR] Unified wrapping method discussion ([https://github.com/VisTrails/VisTrails/issues/991 #991])
** Let's talk next week, [AM] and [DK] are not here

=== January 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* make sure that we address critical issues, questions, and pending review branches in a timely manner
* scripting support
** [RR] no issues if we want to just keep annotations in the generated code to allow the link back to a workflow
** [RR] can translate from workflow to script, working on script to workflow
** will work for parameter value changes, structural changes require changes to the annotations
** need to publish best practices here
** would be cool to do looping in scripts (easier interface than with workflows)
* notebook support (convert form notebook to workflow)
** RR will sync with FC on this
* Issue with console in built-from-scratch
** [TC] iPython rearranged some of the completion stuff in 2.2 and 2.3
** binary has old version of iPython -> 1.0.0, should we update?
* [TC] automated wrapping of numpy and scipy
** discovered a bunch of malformed documentation in numpy and scipy
** has github repo for vistrails tools
** example modules wrap a bunch of R stuff (not baked in, just how things are)
** will be pushing wrapping logic up
** port names forbidden (window and domain)
** have an import hook to get from yaml directly to VisTrails Modules
** should work for any python modules with well-formed numpy docstrings.
* [Action] should make it clear in documentation that Constant now means serializable not that the value doesn't change (e.g. List)
* [TC] might be interesting to try to build components of matplotlib and accumulate in figure (long-term project, but thinking about how this might work)
* [TE] build and build scripts
** completely automatic, buildbot
** need to set the build machines for the environment we want for the binary
** would virtualenv work here?
** [TC] anaconda can pin versions, potential path to test different configurations
** Q: upload nightly binary builds? A: makes sense, make sure they are well-labeled
* sourceforge stats: e.g. http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07
* package issues (see Remi's message)
* [TE] Scope of tej
** Support single ssh commands?
** Queue can be used as a remote machine (crawler is using queue.call*)
* SourceForge stats: http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07

== Older meetings ==
* [[Development/2014]]
* [[Development/2013]]
* [[Development/2012]]
* [[Development/2011]]
* [[Development/2010]]

Development

2016-05-18T15:00:04Z

Tommy: /* May 11, 2016 */

<div class="nonumtoc toclimit-1">
__TOC__
</div>

See also the [https://github.com/VisTrails/VisTrails/wiki/Development Github wiki]

== 2016 ==

=== May 18, 2016 ===

'''Items to Discuss'''
* [TE] mailing list still down - Julio working on it
* [TE] Improved union port
** New schema 1.0.5 adds portitem.union string attribute
** Works with pipeline view, parameter exploration view, and mashup view
** Should work well for matplotlib
** Use with VTK ports?
*** It uses [item_1,item_2] style ports usually with different tuple length.
* [TE] Remove emacs dependency from db generate [https://github.com/VisTrails/VisTrails/issues/1173 #1173]

=== May 11, 2016 ===

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]
** GUI-based solution [https://github.com/VisTrails/VisTrails/tree/union-port Branch union-port] Demo?
*** Shows single port for all ports with same sort_key
*** Select specific type when adding/showing
*** Only one type should be visible on the module at any time
*** Making tuple parameters union types is probably too complicated
*** Should work with alternate specs like matplotlib (if sort_key is defined correctly)

* [TE] Feature suggestion: Let connections connect to functions/parameters
** Show functions and parameters as ports and toggle port visibility directly for functions and parameters
** Use separate views for ports and functions (like before)
*** Allow rearranging of functions
** Pros:
*** Supports ordered connections. Create 2 functions, make them visible as ports, make connections to them.
**** We can also have, e.g., a line joining the ports on the module to indicate they are part of a list.
**** Makes List module simpler
*** Connect to parameter in tuple
*** Functions that are visible on the module can connect to an actual function, and not just to the first one it finds.
*** Can replace operation modules (in python-wrapper) in some cases for, e.g., numpy.
** Cons:
*** Interface more complicated and crowded
*** More difficult for users to grasp?
*** No immediate use case
*** Makes no union type for tuple parameters a bigger problem.

* [TE] Publish user survey?
** No response from vistrails release yet
** Not announced on vistrails-users yet.

=== May 4, 2016 ===
'''Updates'''
* VisTrails 2.2.4 released

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]

=== April 27, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Wrapping Bokeh
** New method type "operation"
*** Transforms Figure->Glyph->Output into Glyph->Figure->Output
**** Glyph sets function name and arguments as output
***** Not serializable, but should always be computed together with the subject of the operation.
**** Figure applies Glyph operation on itself
*** Useful for matplotlib?
**** matplotlib currently find actors by searching upstream?
**** But this is more difficult since matplotlib is not function-based.
** New "union" port type
*** Turns "x(float), x(list)" into "x (float, list)" and uses first set value
**** Uses only first value in tuple
**** Bokeh have many properties that support (list, string, Float)
*** Does not work with depth=1 types (e.g. Float of depth 1)
**** Turn Depth 1 types with known type into lists?

* [TE] New bugfix release
** Finalize survey

=== April 20, 2016 ===
'''Updates'''
* Merged upgrade fixes
** Now has infinite loop test
** loop test now correctly loops 5 times
*** remap_module used wrong (current) package version when creating ModuleDescriptor
* Fixed multi-step group upgrades (PR: [https://github.com/VisTrails/VisTrails/issues/1168 #1168])

'''Items to Discuss'''
* New bugfix release
** Merge usagestats
** Need to finalize survey

=== April 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Chaining upgrades done ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Replace "Upgrade" description annotation with "upgraded_from" annotation to identify which tags to hide?

* [TE] Iterating handle_invalid_pipeline ([https://github.com/VisTrails/VisTrails/pull/1165 #1165])
** Not based on [https://github.com/VisTrails/VisTrails/tree/chain-upgrades-loop chain-upgrades-loop]
** Cherry-pick test to preserve source?
** Need maxPipelineFixAttempts option?
*** The code is now smarter about recursion, so max attempts will "probably" never be reached.
** Need [https://github.com/VisTrails/VisTrails/commit/0ef0667426937eddb1d1c1e397f0657ffec039a9 debug messages]?
*** Would need to be moved into handle_invalid_pipeline

=== April 6, 2016 ===
'''Updates'''
* [TE] Query View improvements
** Done except for displaying "Version Info" and #1164
* [RR] Working on finishing new interpreter (finally!)

'''Items to Discuss'''
* [TE] Chaining upgrades ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Try latest upgrade first, then previous.
** If all fail, select latest upgrade?

=== March 30, 2016 ===
'''Updates'''

'''Items to Discuss'''

* [TE] Query View improvements
** Unified do_version_switch and get_upgrades as validate_version()
** Problems with query view using its own controller
*** Fixed module info not being displayed for query results
*** Still no version info for query results
*** Still an issue with version query view not being updated

=== March 23, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Usage reporting almost ready to go
** Need to record whether specific features are used: paramexpore, mashup, query
*** [DK] Record if LaTeX extension is used? But hard to distinguish from direct batch invocation
** How to record size of vistrail?
*** [DK] IdScope already walks over vistrail, use that
*** but total number of modules and versions doesn't give an idea of average size of individual pipelines

=== March 16, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Upgrades in Query Mode
** Now using code similar to do_version_switch
*** Uses handle_invalid_pipeline
*** Differences: Not using current_pipeline, flushes changes
*** New controller method get_pipeline optimized using cached pipelines (but not current_pipeline)
*** Integrate to avoid repeated code?
*** Use this for query mode?
* [TE] VisTrails 2.2.4 ready for release?
** tej package updated. Others?
* [JF] upgrades and the version tree
* [JF] provenance in Jupyter
* [DK] bundles: [https://github.com/VisTrails/VisTrails/pull/1092 #1092]

=== March 9, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixing search mode
** String query now matches all by default
*** This caused pipeline queries to never match
** String query can search: User/Notes/Tagname/Time/Module name
*** Should we search module names by default? (Disabled by default because it is expensive)
*** Fixed notes search
** '>' parameter queries in documentation but has been removed
** Fixed module matches for upgraded pipelines (By not upgrading pipeline)
*** Upgrades still a problem
*** Add "Upgrade all menu option?" (Or upgrade all on open when `hideUpgrades`)
*** [JF] Allow search on past tags

* [TE] Create new bugfix release
** Finish querying
** Path issue on windows

* [DK] Look into sqlalchemy and new bundle branches

=== March 2, 2016 ===
'''Updates'''
* [TE] Fixed cache bug with port specs
* [TE] VisTrails Next
** Most packages now work
** No qgis for Python 3

'''Items to Discuss'''
** Always dereference symlinks? [https://github.com/VisTrails/VisTrails/issues/1146 #1146]

=== February 23, 2016 ===
'''Updates'''
* [TE] Fixed PythonSource 100% CPU bug
* [TE] VisTrails Next
** Updated [http://opendap.co-ops.nos.noaa.gov/axis/webservices/wind/ NOAA Web Service] examples
*** Now uses REST service, tabledata, and Google Maps
*** Web Service replaced with DownloadFile

'''Items to Discuss'''
* [RR] Couple of fixes are in for API, and tej&reprounzip on the Mac binary. Also new release of tej, and working on anonymous usage reports.
** New 2.2 release soon?
* [RR] Anonymous usage reports
** Sends out info like number of modules & versions, packages used, Python & libs versions, execution time, specific features [https://github.com/VisTrails/VisTrails/pull/1154 #1154]
* [JF] Bring in noWorkflow to track variable dependencies, for the considered Jupyter integration?
* noWorkflow - provenance for python scripts
** Recent work on tracking dependencies
* Also integrates ReproZip with Jupyter
** [http://mybinder.org mybinder]
*** Use with ReproZip to automatically build Jupyter notebook interfaces
* Daves comments on Jupyter integration
** It is possible to identify cell order on the server side
** Not trivial to track order of cells on client side
* How does Galaxy workflows relate to VisTrails?
** Packaging in Galaxy is hard
** Galaxy for biomedical workflows, difficulty making it general
* Action items
** How difficult to track cell dependencies in Jupyter notebooks?
** Use noWorkflow to track cell dependencies?
** How difficult to modify mybinder to use ReproZip packages?

=== February 17, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixed Group memory usage
** Modules in groups are supposed to be freed when done executing
*** Prevented by logger that stored references to the modules (fixed, now using id(module))
*** Prevented by list iterator bug that stored list of modules on the 'self' port bug (fixed)
* [TE] VisTrails Next
** Removed deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** PythonSources will be upgraded
*** Fixes for Python < 3
*** fixes for VTK < 6
** TODOs
*** Remove RemoteQ
**** Port Hadoop to tej (Already have pbs)
*** Merge package wrapper
*** Finish SQLAlchemy branch
*** Finish new bundle branch
** [JF] Will contact Jeff and Matthias about moving to Python 3
* [JF] Query by Example is broken
* [JF] VisTrails Data Cleaning Project
** Use VisTrails to process and explore task-specific data while keeping provenance.
** Remi's Idea
*** Use VisTrails as the backend in a Jupyter notebook
*** Overcome problems with executing cells in random order
**** Interesting research topic, but little interest has yet been noted
*** Interesting to study how such a notebook would be used (Is there notebook usage data available?)
*** Impose restrictions to notebook cell boundaries
*** It will only work for functional operations
*** Can we fix, or detect, non-functional (mutating) operations?
*** Analyse code and data flow and see if it mutates data in unexpected ways?
*** Mutable operations can be created in many ways in Python
* Next meeting Tuesday 11:30

=== February 10, 2016 ===
'''Updates'''

'''Items to Discuss'''
* VisTrails Next
** Test suite passes
*** Python 3 less deterministic, module upgrade order random.
** [RR] updating packages: Reprounzip (pushed), tej, persistent_archive, ...
** All of our packages should run fine :)
** VTK thumbnail comparison works
*** Rendering bug on some systems
**** QVTKCell now inherits QGLWidget
*** Old thumbnails had wrong height due to spreadsheetwindow being too small
**** Fixed by regenerating thumbnails
*** Silenced deprecation messages when generating modules
*** Many new classes in VTK 7
** Remove deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** Will break existing PythonSources
**** Try to upgrade?
*** Old-style packages
**** Or only allow a new style, like __init__.py renamed to info.py? (merge with identifiers.py?)
***** Read info.py without importing package?
*** Fixes for Python < 3
*** Fixes for Qt < 5
*** fixes for VTK < 7
*** Remove self port?

=== February 3, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] [http://lists.vistrails.org/pipermail/vistrails-users/2016-January/000402.html Rendering a .pvd (ParaView) file?]

* VisTrails Next
** All tests but thumbnail comparison passes
** Still issues with gui and more packages needs to be tested
** PythonSource and MplSource upgraded with lib2to3
** Keep contrib packages? Update?
** [https://blog.kitware.com/vtk-7-0-0/ VTK 7 is released]
*** Supports Python 3
*** Will hopefully get into conda and others soon
*** Deprecates a bunch of modules

* [https://travis-ci.org/VisTrails/VisTrails/builds/106743348 Travis builder] for VisTrails Next
** Runs!
** Uses conda
*** Many levels of requirements
**** apt packages
**** conda packages
**** python packages in requirements.txt
**** python packages in setup.py
*** Can probably drop conda. Default builder does not have Qt5, but beta builder do!
*** But useful if we want to use conda in our own build process.
** Lots of errors I do not get locally?

* [http://goo.gl/forms/Z4HBrwaBWL User Survey]
** Have you used any alternatives to vistrails?
*** Relevant? More options?
** How often do you use any of these particular features in VisTrails?
*** Add/Remove alternatives?
** How important would you rank the following potential improvements to VisTrails?
*** Add alternatives?

=== January 27, 2016 ===
'''Updates'''
* New interpreter
** Working prototype soon
** Looping not completely done (and port combination mode: pairwise/cartesian...)
** Need to integrate with VisTrails
*** Compatibility with existing modules
*** Use log controller
*** Want to cache at multiple levels (whole stream/single element of stream)
*** Non-runtime attributes of modules (cache check, automatic conversion check, constant from/to string)

'''Items to Discuss'''
* User Survey

* ZMQ failing on windows (vistrails-users)

* [TE] [https://github.com/VisTrails/VisTrails/pull/1143 Python 3 branch]
** Testsuite almost passes
*** Failing are unicode filenames, some users guide examples, and thumbnail comparisons.
** Fixed issues
*** Signatures are now bytes (convert to string to show in widget)
*** Cannot compare different types, e.g., (None < 1)
**** PortSpec.depth and min/maxConn could be None. (Backport!)
**** cell.row could be None
*** Lots of unicode/bytes fixes to serializations
**** We have encryption implementations in the code! (keychain)
*** Lots of small fixes to package method differences
** Current issues
*** logging widget empty?
*** version tree signals messed up
*** provenance view legend icons black
*** Text do not fit in some widgets
*** VTK thumbnail comparison fails
**** VTK Cells have some faces in wrong direction?
**** Because running in VM?
** Installing on Ubuntu LTS/Latest Mint
*** Install latest matplotlib from pip
*** Install VTK 7.0.0rc2 from source
*** No QtWebEngine binary (controversial) (Must install sip/PyQt5/Qt5 from source)

=== January 20, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Backporting features from Python 3 + PyQt5 + Qt5
** Merged unicode with master ([https://github.com/VisTrails/VisTrails/tree/unicode unicode])
*** One unicode test failing
*** Problem saving to xml
** Used [http://python-future.org/ python-future] to run futurize stage 1 to update legacy (pre 2.6) code ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized unicode-futurized])
*** Updates print to functions 'from __future__ import print_function'
*** Updates exception calls to use 'as'
*** removes most usages of 'long' (mostly used unnecessarily)
**** Only needed for 32-bit support
*** Fixes relative imports (from __future__ import absolute_import)
** Fixing code that is deprecated in Qt 4.8 and removed in Qt 5 ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized-qt5 unicode-futurized-qt5])
*** Updated all signals to new-style
* If we go 2 to 3, this could break packages
** means we should schedule any package format changes for the same time
** e.g., imports should be unrelated to code path (function to load module from package identifier?) (take them out of vistrails.* [https://github.com/VisTrails/VisTrails/pull/1002 #1002])
** any structural changes (e.g. the __init__ versus init thing) (RR thinks it makes sense, though having both named "init" is unfortunate)
** putting package identifier as xml?
*** Python not so bad, plus some stuff in there is Python code (checking dependencies)
** version the APIs?
*** RR planning on versioning vistrails_module.Module, no point versioning the whole package?
* file formats on 2 to 3:
** no real translation/upgrade, but non-ascii values that work on 3 won't load in 2

=== January 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://gist.github.com/rexissimus/dfd27e466427529c385c Porting to Python 3 / PyQt5]
** Basic GUI and execution works
** Minimal work to support 2to3
** Hard to support both PyQt4 and PyQt5

=== January 6, 2016 ===
'''Updates'''
'''Items to Discuss'''
* Updating VisTrails dependencies
** Successfully built [https://gist.github.com/rexissimus/f1a1aada7de1c00a57c7 Win7-64/Python3/PyQt5/Qt5/WebEngine/VTK7]
*** VTK 7 is the first supporting Python 3 but is only in release candidate phase.
**** Next version of VTK 6 is rumored to support Python 3
**** There is a development branch of VTK 6 supporting Python 3
*** Can travis build this?
**** We can skip tests for WebEngine and VTK if needed
** Python 3 [https://python3wos.appspot.com/ showstoppers]
*** No MySQL-python (sqlalchemy supports mysql through other drivers)
*** No suds (there are active forks but we could also drop support?)
* Options for python2/3 support:
** Interpreter could be python2/python3 based on packages
** six layer works but not the easiest to maintain (e.g. in reprozip)
* Drop support for win-64
* Update copyright headers to 2016

== 2015 ==

=== December 30, 2015 ===
'''Updates'''
* Bokeh package finished
** Can output to Browser/IPython/Spreadsheet (Limited functionality in spreadsheet)
'''Items to Discuss'''
* Updating VisTrails dependencies
** Bokeh needs QWebEngine (Chromium) in Qt5 which requires PyQt5
*** Many plotting libraries only work in browsers
*** But Chromium may be a big and controversial dependency
*** Or create a browser version of the spreadsheet?
** Some users have requested Python 3
** Not backwards compatible?
** Target for VisTrails 3.0 with new interpreter?

=== December 16, 2015 ===
'''Updates'''
'''Items to Discuss'''
* Users list question
* [TE] Wrapping Bokeh
** Added bokeh property parser
*** complements numpydoc parser
*** Not all attributes are available, partially because I am using a pre-release version.
** Wrapped modules
*** bokeh.plotting finished (Backwards like matplotlib: Create plot then draw on it)
*** bokeh.charts mostly done (Missing arguments)
** QWebView mostly works (but no zooming or buttons)
*** It would be better to use external browser or QWebEngineView
** Added improvements to wrapper
*** Generalized port translations (Color/Path to native types)
*** Can use multiple docstring/property parsers simultaneously

=== December 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Looking into wrapper
** Will port TensorFlow
** Doing a pass on the wrapper code & doc
*** UX improvements
** Factorize high-level docstring parsers into core.wrapper? (sphinx, numpy, google)
** Problem with name vs module_name (fails sklearn tests because class_by_name() is broken)
** Looking into compressing specs, lazy registration of modules

=== December 2, 2015 ===
'''Updates'''
* [TE] Package wrapping
** Wrapped most of numpy/scipy using __all__
** Added class attribute and method access for classes (Can add to class or to separate inspector module)
** TODO: Document wrapping procedure

'''Items to Discuss'''

=== November 25, 2015 ===
'''Updates'''
* [RR] New interpreter is coming along
** Everything is a stream
** Task system, eventually work-stealing parallelism
** Streams no longer advance in lock-step
*** Allows for constructions like filter, join, sorted-merge
** depth>1 still to be tested, no current plan to allow this through the module interface
*** Through looping though, can do streams of streams

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapped most numpy functions (no polynomials)
** and half of scipy classes and functions
** Added functions manually from documentation (no parseable lists?)
** Focusing on data flow constructs (no property/method access for classes)
*** Using spec diff (empty for now) and dynamic parser (stores spec in .vistrails/)
** Python class/function wrapper now stable
** Add google doc parser?
*** Is there a parser available?

=== November 18, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Numpy class wrapping works
*** Basic type is List, since most types are array_likes.
*** TODO: More classes and functions
*** Some operations are in-place and some aren't, and docstring not super clear
*** [RR] It seems only methods mutate, and most have a numpy.xx function equivalent; just manually go through the methods and remove the mutating ones?
** Class wrapper is modular
*** Docstring parser and type string parser can be customized
*** Classes can have optional attribute/method ports
**** Inspectors and attribute/method modules can be created separately
** Use PythonCalc as an example
*** Can be re-implemented as a function with a parseable docstring
*** [RR] PythonCalc is just an example, and it might actually make sense to get rid of it, or do a proper math package with scalar operations (as separate modules, no combobox)
** [RR] TensorFlow to use wrapping as well
*** Very simple (only types 'tensor' & 'variable')

=== November 11, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapping numpy's classes using numpydoc (ndarray)
*** Wrapping constructor arguments, attribute getters/setters as module ports
**** Then how to access attributes afterwards?
***** Use input value port to class modules?
*** Wrap methods as modules? E.g., `ndarray.shape`.
*** Function wrapping is almost a subset of class wrapping
**** May be able to use the same parsing/execution methods
** VTK's non-getter/setter methods could be wrapped as modules
*** We could then remove extra logic in interpreter for keeping function order
** Bokeh uses autogenerated docstrings
*** We may be able to read the specification directly

* [RR] [https://github.com/VisTrails/VisTrails/pull/1138 TensorFlow package]
** Basic setup working, can execute the Mandelbrot example
** Will autogenerate the operations

=== November 4, 2015 ===
'''Updates'''
* [RR] Interpreter work requires a fix for [https://github.com/VisTrails/VisTrails/issues/1137 DB issue #1137]
* [DK] Kitware's Resonant [http://www.kitware.com/source/home/post/173]
** [https://github.com/girder/girder Girder]: data management system
** [https://github.com/Kitware/romanesco Romanesco]: execution engine, uses [http://www.celeryproject.org/ Celery] for task management
** Resonant Flow: web app for editing and executing workflows

'''Items to Discuss'''
* [TE] Added OSX Lion (10.7) VM on build machine using vagrant (seems ok with license?)
** New builds works on Lion
** Change the minimum requirement to 10.7?
* [TE] Package wrapping
* Added upgrade suggestions using 2 spec versions ([http://pastebin.com/30XUU8Gp example])
** using name edit distance to find matches
** Could use something better like port similarity for modules, and type similarity for ports
** Should write python upgrade code?
** Added spec to sklearn package
*** Can now diff spec versions and keep the spec static
*** There will be problems with downgrades and package versions

=== October 29, 2015 ===
'''Updates'''
* [TE] nightly-build-mac fixed (Needed to approve xcode license)

'''Items to Discuss'''
* [TE] matplotlib wrapper
** ported to general spec
** Diff can be used on general spec
*** Only needed minor changes
*** Fixed indexing bug that corrupted specs
*** Can now move diff tools to core/wrapper
** Add new plots?
*** New plots in mpl 1.3: eventplot
*** New plots in mpl 1.4: angle_spectrum, magnitude_spectrum, phase_spectrum', violinplot
*** No new plots in mpl 1.5 (from looking at boilerplate.py)

=== October 21, 2015 ===
'''Updates'''
* [RR] Alexis has arrived, will be working with [RR] on a more efficient interpreter

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package]
** Supporting multiple package versions
*** Check which version can be loaded [https://github.com/VisTrails/VisTrails/pull/1135 #1135]
*** We cannot show version requirements in the list of packages because old packages are loaded when importing the codepath
** Visual diff does not work well, but we can use the spec differ to see differences.
** Unifying vtk and matplotlib wrapping specs (WIP)
*** And porting matplotlibs spec differ to work on the general spec
*** Spec differ can then be used on vtk and other packages in the future
*** Will enable automatic upgrade generation
* [RR] Rework interpreter
** restore abstraction between interpreter/module code
** build looping, streaming, caching into the interpreter
** rework cache
** look into parallelism once basic functionality is there

=== October 14, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package] (adding numpydoc parser)

=== October 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/tree/fix-matplotlib-parser New matplotlib parser] (adding numpydoc parser)
** Added numpydoc attribute parser for plots.
*** TODO: Need better port spec reconciliation with call signature parser.
*** We can create a general numpydoc parser, but attribute types are unique to matplotlib.
** Needs package versioning
*** New spec will not support matplotlib < v1.4 due to changed path to axes classes.
*** Load spec version corresponding to installed matplotlib version?
*** Need version downgrades?

=== September 30, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Updating Matplotlib parser
** Matplotlib docstring parser fails on numpy docstrings
** I have [https://github.com/VisTrails/VisTrails/commit/eae8b0c16260810587e47c41cab53552cbb3cf0a added basic numpydoc parsing]
*** Only used by a few docstrings so far
*** Parsing uses many sources (class tables, signatures, ACCEPTS, method docstrings, definition parsing).
** Caswell said they were thinking about moving to traitlets, but this is not ready yet

=== September 23, 2015 ===
'''Updates'''
* [TE] VisTrails 2.2.3 released
** Also have pushed to PyPI, binstar, etc.
** Sourceforge vs. GitHub
*** should be able to host releases on GitHub
*** nightly binaries pushed to sf each night
*** old binaries?
* [TE] Re-wrapping MatPlotlib
** Keep static generation - Docstrings are brittle beween matplotlib versions
** Keep generating the executable classes - but create functions, not vistrails Modules
*** Why is there so much patching?
** Re-implemented Alternate PortSpec for InputPortSpec
*** It will now inherit specs from parent (No need to reimplement)
** Module upgrades?

'''Items to Discuss'''

=== September 16, 2015 ===
'''Updates'''
* [TE] Job Monitor tests and documentation done
** OK to leave document package in packages directory?

'''Items to Discuss'''
* [TE] Library wrapping: How to do code patching? [https://docs.google.com/drawings/d/1Sh3eOXot6v2y880jHKQrqXqAwr-0aoqYligg3z8G8MY/edit?usp=sharing Wrapping diagram]
** Insert code into module template (Old VTK code)
** Patch the library that is called (New VTK code)
** Somehow store code in spec and apply when executed?
*** Executed code needs at a minimum access to inputs, outputs, current class
*** Use standard input/output dict and obj reference that the code operates on?
*** Can this be done while keeping the execution abstract?

* Do new release now?

=== September 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* New release?
** [RR] wants reprounzip
** tej changes & doc
** job monitor & jobmixin fixes
** mongodb
** reprounzip
** warning: MplFigure type is int
** tabledata: add Reshape, DictoToTable & ListToTable, fix ListToTable with numpy arrays
** PythonSource can have same name for an input & output
** don't show spreadsheet at exit

=== September 2, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Limit autosaves? [https://github.com/VisTrails/VisTrails/pull/1126 #1126]

=== August 26, 2015 ===
'''Updates'''
* [TE] Added Job support to Parameter Explorations (Requested by Colin), and Mashups
** specify job ids, need to specify different ids for parameter explorations since they have the same version id
** how to deal with parameters passed in on command line
* [General] provenance: should be creating a new version when we execute workflow with changed parameters?
** currently, custom_params annotation stores this in provenance currently
** [RR] API doesn't record provenance if passing in parameters: http://git.io/vsAA5
'''Items to Discuss'''

=== August 19, 2015 ===
'''Updates'''
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [TE] Working on Job Monitor documentation

'''Items to Discuss'''
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [TE] Stop testing VisTrails 2.0?

=== August 12, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Build broken on Travis; because of IPython 4 released today? ([https://travis-ci.org/VisTrails/VisTrails/builds/75279795 build 992]; [https://github.com/VisTrails/VisTrails/issues/1123 #1123])

=== August 5, 2015 ===
'''Updates'''
* [TE] Fixes to Jobs
** Could not delete jobs
** Could not run job in group
** Job not reset when calling ModuleSuspended
** Added deleting job from context menu
* [RR] Writing documentation for everything [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

'''Items to Discuss'''

=== July 29, 2015 ===
'''Updates'''
* RR still looking into new interpreter thing
** Goal is to take out scheduling logic from Module so it can be split in multiple processes, and so that smarter strategies can be added in time
** This means some work on packages
** Spreadsheet can live in kernel process? Still some UI stuff that will take work (changing configuration, persistent archive's viewer, ...)
* [TE] Problems running examples [https://github.com/VisTrails/VisTrails/pull/1111 #1111]
** Testing of more examples requires additional packages on the test machines.
** Fixed faulty line-ending in PythonSource:s failing on Python 2.6.
** Test suite now testing SUDSWebServices (If web service is down, test suite will fail)
** preferences.py test failed reloading 'dialogs' package, switched to using 'URL'.

'''Items to Discuss'''

=== July 22, 2015 ===
'''Updates'''
* [TE] mailing lists back online
* [TE] Working on [https://github.com/VisTrails/VisTrails/issues/1107 #1107]
* [RR] Working on ReproZip package

'''Items to Discuss'''
* [RR] MongoDB package [https://github.com/VisTrails/VisTrails/pull/1106 #1106]
* [RR] Example for tej docs? [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

=== July 15, 2015 ===
'''Updates'''
* 2.2.2 released

'''Items to Discuss'''
* RR is considering executing everything in an IPython kernel (i.e. separate Python interpreter, like the one spawned for a notebook)
** It's a separate process that we can restart without restarting the app/gui
** We can isolate the execution environment (e.g. for the server)
** We can run the whole thing remotely (if your data is elsewhere, just run VisTrails locally and the pipeline elsewhere)
** Pipeline execution no longer makes the interface hang, it just makes the kernel hang (but that's fine)
** We can use notebooks as modules (probably way nicer than the PythonSource module)
** We can run multiple kernels so long as the ports carry things that are serializable
*** meaning we can put the multithreaded-interpreter without all the hacky parts it has now
*** we can run IPython kernels in all the languages IPython supports, [https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages currently 46]

=== July 8, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Buildbot github hook not working after IP address change
* [TE] No reference to VistrailsApplication ([https://github.com/VisTrails/VisTrails/issues/1103 #1103])
** [RR] Added PR [https://github.com/VisTrails/VisTrails/pull/1104 #1104]
* [TE] Reopening VT file after saving with bundled subworkflow won't offer subworkflow upgrade ([https://github.com/VisTrails/VisTrails/issues/1102 #1102])
** allow manual delete to fix right now
** fix this on top of the use-uuid branch
* [TE] Release VisTrails 2.2.1? ([https://github.com/VisTrails/VisTrails/blob/v2.2/CHANGELOG CHANGELOG])
** [https://github.com/VisTrails/VisTrails/pull/1093 output-modules-use-global-dir]
** [https://github.com/VisTrails/VisTrails/milestones/version%202.2 Current issues for 2.2]

=== July 1, 2015 ===
'''Updates'''
* [TE] PROV fixed
* [TE] Working on subworkflow issues
* [RR] Considering reworking the controller (log vs exception problem, retained upgrades causing interferences) and also the interpreter (IPython?)

'''Items to Discuss'''

=== June 24, 2015 ===
'''Updates'''

'''Items to Discuss'''
* UV-CDAT
* [TE] Can a cyclic workflow be valid? ([https://github.com/VisTrails/VisTrails/issues/1097 #1097])
** focus on disabling the ability to create cyclic pipelines because more things break than just this with a cyclic pipeline
* [RR] Relative paths ([https://github.com/VisTrails/VisTrails/pull/1057 #1057])
** This interacts with the new bundle; how do handle packing files inside the VT bundle?

=== June 17, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] current_version and reusing existing upgrades are broken ([https://github.com/VisTrails/VisTrails/issues/1095 ticket #1095])
** Could be that export to PROV is using an unflushed upgrade pipeline?
** current_version would then be correct.
** It may work to flush the actions before exporting?

=== June 10, 2015 ===
'''Updates'''
* DAT: fixed VTK issue on Linux and Mac
* Still crashes on Windows. Need help! Reminder: this works in the VisTrails spreadsheet (QCellPresenter), although no widget get changed there during a drag
** Is it a VTK bug?
** Is it simply impossible to change widgets during the drag, should we do it a different way?
** Did I miss something that is done in VisTrails but somehow not in DAT?
** Low prio, UV-CDAT doesn't run on Windows anyway

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 Updated pull request])
* Single instance code and batch mode

=== June 3, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 pr])
** Requires fixes to command line parameters, Output modules, and batch mode
** How to test this
** Updated missing/outdated flags
** Fixed view issues when generating graphs
* [TE] batch mode
** SpreadsheetOutput not enabled in batch mode. Should we check is_running_gui instead?
** Other instance setting flags from caller
** Is graphsAsPdf replacing spreadsheetDumpPdf?
** graphsAsPdf true by Default?
** Batch mode executing by default (Not needed when generating graphs)
** Re-added workflowInfo as withWorkflowInfo for writing graph and xml workflow
** [DK] batch mode should be outputting to files or stdout, shouldn't always trigger SpreadsheetMode
** execute flag, maybe make execution the default and allow a "--no-execute" if you only want to capture graphs, for example

=== May 27, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] API question
** http://lists.vistrails.org/pipermail/vistrails-users/2015-May/000357.html
* Status of DAT
** Can add VCS plot to DAT but need to work on configuration windows
** Documentation for graphics templates for UV-CDAT/vcs?
* Qt support?

=== May 20, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Reviving the DAT, integrating scripting & porting UV-CDAT!
** On [https://github.com/VisTrails/DAT GitHub] ([https://github.com/VisTrails/DAT/issues issues])
** Merging 2 years of development taking longer than expected, but getting there. The plan is to get the patches in VisTrails and never fork again, we never want to get in UV-CDAT's situation (and don't need to).
** VTK cell works fine on Linux but there was flickering on Mac & Windows before; still issues on Mac (Windows status unknown)
** Can get a VCS plot soon (but will need VTK cell fix)
** Integrate in UV-CDAT's build system (so we have cdms, VCS, ...) -> RR can do this, low priority
** How do we integrate scripting?
*** We want to be able to seamlessly make changes to a plot by changing Python code
*** Define new plots by entering Python code without writing modules/packages?
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 13, 2015 ===
'''Updates'''
* [RR] Test skipping whitelist ([https://github.com/VisTrails/VisTrails/pull/1069 #1069]) -- low priority
* [RR] Custom matplotlib modules can't be compatible with both 2.1 and 2.2 ([https://github.com/VisTrails/VisTrails/issues/1067 #1067]); should be fixed for ALPS ([https://github.com/VisTrails/VisTrails/issues/1070 #1070])

'''Items to Discuss'''
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 7, 2015 ===
'''Updates'''
* [RR] Export/import workflow to Python working!

'''Items to Discuss'''
* [Claudio] UV-CDAT
** The UV-CDAT project is the biggest user base of VisTrails
** VisTrails package management provides a lot of friction towards people plugging in their code
** Need to make it easy to integrate your random Python scripts in the system without having to deal with all the boilerplate, at least in the first step
** [RR] argues that modules are still good; UV-CDAT shouldn't move towards a purely script-based backend
** [RR] export/import with Python could reduce a lot of that friction by allowing 1) to edit workflow as Python 2) to open up boxes automatically if needed code doesn't match actual modules
** ...

=== April 29, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] <strike>Abstractions</strike> subworkflows status ([https://github.com/VisTrails/VisTrails/labels/subworkflows tickets])
* [RR] matplotlib compatibility (2.1 & 2.2), [https://github.com/VisTrails/VisTrails/issues/1067 #1067]
** RR to try and fix ALPS matplotlib modules

=== April 22, 2015 ===
'''Updates'''
* 2.2.0 has been released!
* Windows issue (via email from Ryan)
** issue with manifest file (may be a new file in VTK6?)
** Tommy has regenerated new Windows builds
* Binaries, pypi, and conda released
* [RR] Export as script
* Python sources using VTK need to switch to SetInputData (users should be aware of this)

=== April 15, 2015 ===
'''Updates'''
* Ready for 2.2.0 (apart from binary/deps issues)
** Missing some libs (scikit-learn, tej, tdparser, SQLAlchemy+connectors
** Windows: runvistrails.py is no longer used, so the PATH is wrong
** Windows: pip is broken, but it probably wouldn't work anyway because of permission issues (disable this?)
* Queries, upgrades and getPipeline() usage ([https://github.com/VisTrails/VisTrails/issues/1054 #1054])
** Getting a pipeline with getPipeline() is not safe: it might return an invalid pipeline
** This is used in many places throughout the code, like queries
** Upgrading would require going through the controller, but that creates new actions
* [TC] Avoid copying a module's output if it's used as input by exactly one downstream module ([https://github.com/VisTrails/VisTrails/issues/1060 #1060]) (useful for big numpy arrays you can update in-place)

=== April 8, 2015 ===
'''Updates'''
* [DK] Merged RR's changes for output modules (1012 and 1013)
** RR will merge remaining changes, then create v2.2 branch!

'''Items to Discuss'''
* BNL need numpy array to VTK image
** Looks like VTK has some helpers for this
** We will help if issues arise
** Will contribute back to VisTrails package
* Upgrade issue: [https://github.com/VisTrails/VisTrails/issues/1017 #1017]
** Automatic upgrades should happen between versions of provided upgrades
** Our existing upgrades work around this so it doesn't need to be 2.2.0
* Corner-case VTK modules
** No longer need VTKCell input port, so don't interfere with registry and API anymore
** Still work weirdly, people probably shouldn't use them
** But we have lots of clunky modules since we wrap the whole of VTK; some people might rely on this and know how to use them, let's keep them anyway
** Ready for 2.2.0

=== April 1, 2015 ===
'''Updates'''
* [RR] UV-CDAT: bugfixing for 2.2, long-term plans: implement scripting import/export in VisTrails, port to UV-CDAT
* Possibly, try to move to regular VisTrails to use new features

'''Items to Discuss'''
* 2.2 release: nothing much is pending anymore, release next week?
** [TE] vtkExporter classes [https://github.com/VisTrails/VisTrails/issues/1032 #1032]
** [RR] Hiding upgrades in version tree might make it (or might be 2.2.1 so we can test it out) [https://github.com/VisTrails/VisTrails/issues/949 #949]
** Output modules changes to go in
* add note to documentation about order of parameters in VTK
* add issue about exporter upgrades if not already there

=== March 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* 2.2 release
** Checklist on Github: https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist
** Review output modules
** RR has a couple more issues to fix
** Ready to go -- sign app package for OSX? [https://github.com/VisTrails/VisTrails/issues/984 #984] We need access to the Apple Membership team

=== March 18, 2015 ===
'''Updates'''
* [TE] VTK6 works

'''Items to Discuss'''
* [RR] Release v2.1.5 with backported tabledata?
** MTA example needs updated tabledata (for JoinTables)
** Google Maps package still not available
* [RR] Work torward v2.2.0?
** changes:
*** new persistence
*** API changes
*** output module changes (upgrades?), maintain cells but try to upgrade
*** not wrapping stuff
*** VTK6? yes
*** JobSubmission stuff?
*** relabeling for upgrades [https://github.com/VisTrails/VisTrails/issues/949 #949]
** makes sense, needs the tree view code to be updated, check selection
** See [https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist 2.2 checklist]
* Discussion of [https://github.com/VisTrails/VisTrails/issues/1016 #1016]
** plumbing between outputs and output modes, how to define a mode that works for many outputs without writing for each output?

=== March 11, 2015 ===
'''Updates'''
* [RR] persistent_archive done; merge? ([https://github.com/VisTrails/VisTrails/pull/755 #755])
** note about the focus events for widgets
** TE be aware of file_archive for future binaries that include persistent_archive
* [TE] [https://github.com/VisTrails/VisTrails/pull/998 New VTK package] finished

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails? (see last week; decision needed)
** RR email to JF about this
** yes; email sent to Github
* [RR] Switching order of output ports ([https://github.com/VisTrails/VisTrails/pull/1006 #1006])
** added port specs are sorted at a separate spot (Module.*_port_specs properties) than those in the registry (which are sorted in the registry), but those two lists are just combined without respect to sort keys
** need to determine whether the two lists should be merged or remain distinct
** should make sure that order of input ports and output ports makes parallel connections for things with same order
** DK suggests breaking backward compatibility here: workflows still run, can fix easily if a problem in an existing package.
* [RR] Question about output modes ([https://github.com/VisTrails/VisTrails/pull/1007 #1007]), how to integrate in API ([https://github.com/VisTrails/VisTrails/pull/24 #24])
** Should ImageFileMode be removed? ("image" is not a mode, "file" is)
** ImageOutput missing?
** Feel free to change how formats works
* [TE] Test suite segfaults on Fedora 17 virtualbox. Install newer version? (Support ended in 2013)

=== March 4, 2015 ===
'''Updates'''
* [TE] VTK wrapper
** Works on VTK 5.10
** Still need to test VTK 6
** New general wrappers for python functions and classes

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails?
** When [http://i.imgur.com/UTY2qfg.png filing a pull request] from UV-CDAT/VisTrails, VisTrails/VisTrails is selected by default
** People keep forgetting to change the default ([https://github.com/VisTrails/VisTrails/pull/956 #956] [https://github.com/VisTrails/VisTrails/pull/968 #968] [https://github.com/VisTrails/VisTrails/pull/999 #999] [https://github.com/VisTrails/VisTrails/pull/1000 #1000] [https://github.com/VisTrails/VisTrails/pull/1003 #1003] [https://github.com/VisTrails/VisTrails/pull/1004 #1004] [https://github.com/VisTrails/VisTrails/pull/1005 #1005])
** Only way to change that is to not have it marked as a fork of VisTrails/VisTrails
** Github staff [https://gist.github.com/remram44/b364c24ef1e462ce6e2f can make that change for us]; should we do it?
** Juliana: comments on this? visibility vs. convenience/annoyance for developers
* [RR] What about [https://github.com/VisTrails/VisTrails/issues/991 #991]?

=== February 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] vtkviewcell for infovis support, can we unify with VTKCell?
** need to test this
* [TE] vtk wrapping
** Mostly finished
** VTK 5.10 produce incorrect results with old wrapping
*** Old wrapper is based mostly on VTK 4
*** Most vtk_examples affected
*** [http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Replacement_of_SetInput]
*** should be able to upgrade from SetInput to SetInputData (need to drop GetOutput and replace with self ports)
*** can we change vtkInstance to just return self and not wrap things
** terminator example not working under 5.8?
* How does VTK wrapping fit into general wrapping framework?
* [RR] new persistence package

=== February 18, 2015 ===
'''Updates'''
* [RR] New VisTrails API and IPython integration ([https://github.com/VisTrails/VisTrails/pull/24 #24])

'''Items to Discuss'''
* [TE] VTK wrapping
** [https://gist.github.com/rexissimus/16b74693545b5e7c1035 Benchmarking vtk package]
*** Old: 24.7 seconds
*** New: 10.5 seconds (Except first time that adds 8 sec)
**** The parsing that calls is_abstract (that tries to instanciate all vtk classes) is now only run the first time.
**** get_items_from_sigstring takes 2 seconds, maybe we can use a lookup dict for already computed sigstrings?
** Now using a general python function wrapper
*** VTK classes are wrapped into python function that does not depend on vistrails
*** VTK functions can be executed without vistrails
*** The spec maps functions into vistrails modules, but can also describe wrapping
*** A general python function wrapper that supports
**** kwarg inputs
**** single, list, dict outputs
**** callback for progress reporting
**** temporary file generator for using FilePool
**** optional output generation
*** Creating specs:
***** Create spec by hand
***** Auto-create spec outline (TODO) and manually finish it
***** Dynamically create spec (VTK)
***** Implement documentation wrappers (Can use scikitlearn wrapper to wrap numpydoc) (TODO)
***** Classes as bad functions needs to be wrapped in new functions before they are wrapped. This is different for each package.
****** Classes is hard: Like VTK, and matplotlib. Scikit-learn does still not wrap classes
***** Spec diffing and patching could be done using code from matplotlib.
** Still needs upgrades from old VTK package
*** Is it possible to dynamically wrap functions, e.g, you see a SetFunc and just remove the 'Set' prefix. Or do you need to create a complete mapping?

=== February 11, 2015 ===
'''Updates'''
* Update from Friday's meeting
** discussed VisTrails internals
** discussed wrapping
*** xml discussion, hard to modify because tied to db code
*** TE has made it possible to add the schema-defined attributes to the intermediate representation
*** higher-level operations on the port specs
** make sure the simple case works
*** [JF] take a simple package with documentation and figure out what the base case for wrapping is

'''Items to Discuss'''
* [TE] VTK wrapping
** Dynamic loading works
** Reading XML is fast enough, but [https://gist.github.com/rexissimus/8272d3c776ccfa115d82 unserializing data is slow]
** Working on patterns for patching
** Matplotlib has many advanced patterns like argument ordering, nested arguments, alternateSpecs, output types.
*** Having all this in a general wrapper might confuse users?
** [RR] Delay module (except for identifiers) until you need it---e.g. don't deal with port specs, etc. until necessary
* Scripting Support [https://github.com/VisTrails/VisTrails/pull/950 #950]
** [RR] Issue with getting code from modules
** Design a simple solution
** [JF] Couldn't you use modules as black boxes without conversion, just to call into modules/subworkflows easily from e.g. IPython?
*** [RR] This is a job for the API, and a very separate use case. See [https://github.com/VisTrails/VisTrails/pull/24 #24]

=== February 4, 2015 ===
'''Updates'''

'''Items to Discuss'''
* Wrapping
** Format to use? Currently XML (like current matplotlib)
*** JSON and YAML have simple "to python dictionary" methods
*** But don't stream
*** YAML a lot easier for humans
** [DK] vtk-new-package also changes parameter names, creates enumerations
*** intermediate schema needs to be extensible
*** packages will want to store there specific infos for compute() method generation
*** also might have specs-altering info, like matplotlib's alternateSpec
** representation to code , registry already has schema for some aspects
** [RR] We might want to see if Module subclasses can be created lazily
*** no need to create all the classes just to register them in the registry and never actually use most of them
*** future effort
* [RR] Where should VisTrails packages live?
** tej installs as 'vistrailspkg.tej', TE installed it as 'userpackages.tej'
** Currently, standard packages are 'vistrails.packages.', user packages are 'userpackages.' and packages loaded through pkg_resources might be anything
** [RR] Use 'vistrailspkg.' everywhere?
** Long-term effort to simplify package distribution/installation (and have VisTrails get them automatically?)

=== January 28, 2015 ===
'''Updates'''
* T. Caswell to come visit on Fri 6 to discuss wrapping work

'''Items to Discuss'''
* [TE] New VTK wrapping
** Current code by DK seems a good deal faster
** Generates XML that can be patched/tweaked, generates Python code from it, VisTrails only loads generated Python code
** RR would rather have VisTrails load intermediate representation (= XML) directly, wants to make sure this is not slower
** The goal is to turn the intermediate step into something generic that would be used for every wrapped package (vtk, numpy, matplotlib, sklearn, java) instead of each having its own
** TC has its own code at [https://github.com/Nikea/VTTools/blob/master/vttools/wrap_lib.py github:VTTools] which parses numpy docstrings and generates modules, doesn't yet handle classes or persist anything
* Web crawler
** Right now, TE starts jobs for "start crawler", "stop crawler", "install classifier"
** RR would rather have the crawling be a job as far as VisTrails and tej are concerned
** The whole thing would be one pipeline: load examples, train classifier, start crawler [check for job, kill previous one, upload model, start processes], get snapshot, visualize
*** Need some support in tej and job submission system: long-running jobs, stop a job (wait for it to finish?), restart a job even though results are cached

=== January 21, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Unified wrapping method discussion [https://github.com/VisTrails/VisTrails/issues/991 #991]
** TE to work on reusable method with intermediate representation, starting with VTK
* [RR] Examples for scikit-learn: JF has an old example using Weka with parameter exploration (not currently in source tree)
** AM's examples are enough
* [AM] scikit-learn package is done, merge it in? [https://github.com/VisTrails/VisTrails/pull/955#issuecomment-70286788 #955]
** RR will merge
* [RR] What should copyright headers say? [https://github.com/VisTrails/VisTrails/pull/994#issuecomment-70173935 #994]
** Let's keep everything in there: Utah/Poly/NYU

=== January 14, 2015 ===
'''Updates'''
* [TE] Working on classifier
* [RR] Scripting integration, work in progress

'''Items to Discuss'''
* [RR] Unified wrapping method discussion ([https://github.com/VisTrails/VisTrails/issues/991 #991])
** Let's talk next week, [AM] and [DK] are not here

=== January 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* make sure that we address critical issues, questions, and pending review branches in a timely manner
* scripting support
** [RR] no issues if we want to just keep annotations in the generated code to allow the link back to a workflow
** [RR] can translate from workflow to script, working on script to workflow
** will work for parameter value changes, structural changes require changes to the annotations
** need to publish best practices here
** would be cool to do looping in scripts (easier interface than with workflows)
* notebook support (convert form notebook to workflow)
** RR will sync with FC on this
* Issue with console in built-from-scratch
** [TC] iPython rearranged some of the completion stuff in 2.2 and 2.3
** binary has old version of iPython -> 1.0.0, should we update?
* [TC] automated wrapping of numpy and scipy
** discovered a bunch of malformed documentation in numpy and scipy
** has github repo for vistrails tools
** example modules wrap a bunch of R stuff (not baked in, just how things are)
** will be pushing wrapping logic up
** port names forbidden (window and domain)
** have an import hook to get from yaml directly to VisTrails Modules
** should work for any python modules with well-formed numpy docstrings.
* [Action] should make it clear in documentation that Constant now means serializable not that the value doesn't change (e.g. List)
* [TC] might be interesting to try to build components of matplotlib and accumulate in figure (long-term project, but thinking about how this might work)
* [TE] build and build scripts
** completely automatic, buildbot
** need to set the build machines for the environment we want for the binary
** would virtualenv work here?
** [TC] anaconda can pin versions, potential path to test different configurations
** Q: upload nightly binary builds? A: makes sense, make sure they are well-labeled
* sourceforge stats: e.g. http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07
* package issues (see Remi's message)
* [TE] Scope of tej
** Support single ssh commands?
** Queue can be used as a remote machine (crawler is using queue.call*)
* SourceForge stats: http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07

== Older meetings ==
* [[Development/2014]]
* [[Development/2013]]
* [[Development/2012]]
* [[Development/2011]]
* [[Development/2010]]

Development

2016-05-11T14:51:12Z

Tommy: /* May 11, 2016 */

<div class="nonumtoc toclimit-1">
__TOC__
</div>

See also the [https://github.com/VisTrails/VisTrails/wiki/Development Github wiki]

== 2016 ==

=== May 11, 2016 ===

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]
** GUI-based solution [https://github.com/VisTrails/VisTrails/tree/union-port Branch union-port] Demo?
*** Shows single port for all ports with same sort_key
*** Select specific type when adding/showing
*** Only one type should be visible on the module at any time
*** Making tuple parameters union types is probably too complicated
*** Should work with alternate specs like matplotlib (if sort_key is defined correctly)

* [TE] Feature suggestion: Let connections connect to functions/parameters
** Show functions and parameters as ports and toggle port visibility directly for functions and parameters
** Use separate views for ports and functions (like before)
*** Allow rearranging of functions
** Pros:
*** Supports ordered connections. Create 2 functions, make them visible as ports, make connections to them.
**** We can also have, e.g., a line joining the ports on the module to indicate they are part of a list.
**** Makes List module simpler
*** Connect to parameter in tuple
*** Functions that are visible on the module can connect to an actual function, and not just to the first one it finds.
*** Can replace operation modules (in python-wrapper) in some cases for, e.g., numpy.
** Cons:
*** Interface more complicated and crowded
*** More difficult for users to grasp?
*** No immediate use case
*** Makes no union type for tuple parameters a bigger problem.

* [TE] Publish user survey?
** No response from vistrails release yet
** Not announced on vistrails-users yet.

=== May 4, 2016 ===
'''Updates'''
* VisTrails 2.2.4 released

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]

=== April 27, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Wrapping Bokeh
** New method type "operation"
*** Transforms Figure->Glyph->Output into Glyph->Figure->Output
**** Glyph sets function name and arguments as output
***** Not serializable, but should always be computed together with the subject of the operation.
**** Figure applies Glyph operation on itself
*** Useful for matplotlib?
**** matplotlib currently find actors by searching upstream?
**** But this is more difficult since matplotlib is not function-based.
** New "union" port type
*** Turns "x(float), x(list)" into "x (float, list)" and uses first set value
**** Uses only first value in tuple
**** Bokeh have many properties that support (list, string, Float)
*** Does not work with depth=1 types (e.g. Float of depth 1)
**** Turn Depth 1 types with known type into lists?

* [TE] New bugfix release
** Finalize survey

=== April 20, 2016 ===
'''Updates'''
* Merged upgrade fixes
** Now has infinite loop test
** loop test now correctly loops 5 times
*** remap_module used wrong (current) package version when creating ModuleDescriptor
* Fixed multi-step group upgrades (PR: [https://github.com/VisTrails/VisTrails/issues/1168 #1168])

'''Items to Discuss'''
* New bugfix release
** Merge usagestats
** Need to finalize survey

=== April 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Chaining upgrades done ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Replace "Upgrade" description annotation with "upgraded_from" annotation to identify which tags to hide?

* [TE] Iterating handle_invalid_pipeline ([https://github.com/VisTrails/VisTrails/pull/1165 #1165])
** Not based on [https://github.com/VisTrails/VisTrails/tree/chain-upgrades-loop chain-upgrades-loop]
** Cherry-pick test to preserve source?
** Need maxPipelineFixAttempts option?
*** The code is now smarter about recursion, so max attempts will "probably" never be reached.
** Need [https://github.com/VisTrails/VisTrails/commit/0ef0667426937eddb1d1c1e397f0657ffec039a9 debug messages]?
*** Would need to be moved into handle_invalid_pipeline

=== April 6, 2016 ===
'''Updates'''
* [TE] Query View improvements
** Done except for displaying "Version Info" and #1164
* [RR] Working on finishing new interpreter (finally!)

'''Items to Discuss'''
* [TE] Chaining upgrades ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Try latest upgrade first, then previous.
** If all fail, select latest upgrade?

=== March 30, 2016 ===
'''Updates'''

'''Items to Discuss'''

* [TE] Query View improvements
** Unified do_version_switch and get_upgrades as validate_version()
** Problems with query view using its own controller
*** Fixed module info not being displayed for query results
*** Still no version info for query results
*** Still an issue with version query view not being updated

=== March 23, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Usage reporting almost ready to go
** Need to record whether specific features are used: paramexpore, mashup, query
*** [DK] Record if LaTeX extension is used? But hard to distinguish from direct batch invocation
** How to record size of vistrail?
*** [DK] IdScope already walks over vistrail, use that
*** but total number of modules and versions doesn't give an idea of average size of individual pipelines

=== March 16, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Upgrades in Query Mode
** Now using code similar to do_version_switch
*** Uses handle_invalid_pipeline
*** Differences: Not using current_pipeline, flushes changes
*** New controller method get_pipeline optimized using cached pipelines (but not current_pipeline)
*** Integrate to avoid repeated code?
*** Use this for query mode?
* [TE] VisTrails 2.2.4 ready for release?
** tej package updated. Others?
* [JF] upgrades and the version tree
* [JF] provenance in Jupyter
* [DK] bundles: [https://github.com/VisTrails/VisTrails/pull/1092 #1092]

=== March 9, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixing search mode
** String query now matches all by default
*** This caused pipeline queries to never match
** String query can search: User/Notes/Tagname/Time/Module name
*** Should we search module names by default? (Disabled by default because it is expensive)
*** Fixed notes search
** '>' parameter queries in documentation but has been removed
** Fixed module matches for upgraded pipelines (By not upgrading pipeline)
*** Upgrades still a problem
*** Add "Upgrade all menu option?" (Or upgrade all on open when `hideUpgrades`)
*** [JF] Allow search on past tags

* [TE] Create new bugfix release
** Finish querying
** Path issue on windows

* [DK] Look into sqlalchemy and new bundle branches

=== March 2, 2016 ===
'''Updates'''
* [TE] Fixed cache bug with port specs
* [TE] VisTrails Next
** Most packages now work
** No qgis for Python 3

'''Items to Discuss'''
** Always dereference symlinks? [https://github.com/VisTrails/VisTrails/issues/1146 #1146]

=== February 23, 2016 ===
'''Updates'''
* [TE] Fixed PythonSource 100% CPU bug
* [TE] VisTrails Next
** Updated [http://opendap.co-ops.nos.noaa.gov/axis/webservices/wind/ NOAA Web Service] examples
*** Now uses REST service, tabledata, and Google Maps
*** Web Service replaced with DownloadFile

'''Items to Discuss'''
* [RR] Couple of fixes are in for API, and tej&reprounzip on the Mac binary. Also new release of tej, and working on anonymous usage reports.
** New 2.2 release soon?
* [RR] Anonymous usage reports
** Sends out info like number of modules & versions, packages used, Python & libs versions, execution time, specific features [https://github.com/VisTrails/VisTrails/pull/1154 #1154]
* [JF] Bring in noWorkflow to track variable dependencies, for the considered Jupyter integration?
* noWorkflow - provenance for python scripts
** Recent work on tracking dependencies
* Also integrates ReproZip with Jupyter
** [http://mybinder.org mybinder]
*** Use with ReproZip to automatically build Jupyter notebook interfaces
* Daves comments on Jupyter integration
** It is possible to identify cell order on the server side
** Not trivial to track order of cells on client side
* How does Galaxy workflows relate to VisTrails?
** Packaging in Galaxy is hard
** Galaxy for biomedical workflows, difficulty making it general
* Action items
** How difficult to track cell dependencies in Jupyter notebooks?
** Use noWorkflow to track cell dependencies?
** How difficult to modify mybinder to use ReproZip packages?

=== February 17, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixed Group memory usage
** Modules in groups are supposed to be freed when done executing
*** Prevented by logger that stored references to the modules (fixed, now using id(module))
*** Prevented by list iterator bug that stored list of modules on the 'self' port bug (fixed)
* [TE] VisTrails Next
** Removed deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** PythonSources will be upgraded
*** Fixes for Python < 3
*** fixes for VTK < 6
** TODOs
*** Remove RemoteQ
**** Port Hadoop to tej (Already have pbs)
*** Merge package wrapper
*** Finish SQLAlchemy branch
*** Finish new bundle branch
** [JF] Will contact Jeff and Matthias about moving to Python 3
* [JF] Query by Example is broken
* [JF] VisTrails Data Cleaning Project
** Use VisTrails to process and explore task-specific data while keeping provenance.
** Remi's Idea
*** Use VisTrails as the backend in a Jupyter notebook
*** Overcome problems with executing cells in random order
**** Interesting research topic, but little interest has yet been noted
*** Interesting to study how such a notebook would be used (Is there notebook usage data available?)
*** Impose restrictions to notebook cell boundaries
*** It will only work for functional operations
*** Can we fix, or detect, non-functional (mutating) operations?
*** Analyse code and data flow and see if it mutates data in unexpected ways?
*** Mutable operations can be created in many ways in Python
* Next meeting Tuesday 11:30

=== February 10, 2016 ===
'''Updates'''

'''Items to Discuss'''
* VisTrails Next
** Test suite passes
*** Python 3 less deterministic, module upgrade order random.
** [RR] updating packages: Reprounzip (pushed), tej, persistent_archive, ...
** All of our packages should run fine :)
** VTK thumbnail comparison works
*** Rendering bug on some systems
**** QVTKCell now inherits QGLWidget
*** Old thumbnails had wrong height due to spreadsheetwindow being too small
**** Fixed by regenerating thumbnails
*** Silenced deprecation messages when generating modules
*** Many new classes in VTK 7
** Remove deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** Will break existing PythonSources
**** Try to upgrade?
*** Old-style packages
**** Or only allow a new style, like __init__.py renamed to info.py? (merge with identifiers.py?)
***** Read info.py without importing package?
*** Fixes for Python < 3
*** Fixes for Qt < 5
*** fixes for VTK < 7
*** Remove self port?

=== February 3, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] [http://lists.vistrails.org/pipermail/vistrails-users/2016-January/000402.html Rendering a .pvd (ParaView) file?]

* VisTrails Next
** All tests but thumbnail comparison passes
** Still issues with gui and more packages needs to be tested
** PythonSource and MplSource upgraded with lib2to3
** Keep contrib packages? Update?
** [https://blog.kitware.com/vtk-7-0-0/ VTK 7 is released]
*** Supports Python 3
*** Will hopefully get into conda and others soon
*** Deprecates a bunch of modules

* [https://travis-ci.org/VisTrails/VisTrails/builds/106743348 Travis builder] for VisTrails Next
** Runs!
** Uses conda
*** Many levels of requirements
**** apt packages
**** conda packages
**** python packages in requirements.txt
**** python packages in setup.py
*** Can probably drop conda. Default builder does not have Qt5, but beta builder do!
*** But useful if we want to use conda in our own build process.
** Lots of errors I do not get locally?

* [http://goo.gl/forms/Z4HBrwaBWL User Survey]
** Have you used any alternatives to vistrails?
*** Relevant? More options?
** How often do you use any of these particular features in VisTrails?
*** Add/Remove alternatives?
** How important would you rank the following potential improvements to VisTrails?
*** Add alternatives?

=== January 27, 2016 ===
'''Updates'''
* New interpreter
** Working prototype soon
** Looping not completely done (and port combination mode: pairwise/cartesian...)
** Need to integrate with VisTrails
*** Compatibility with existing modules
*** Use log controller
*** Want to cache at multiple levels (whole stream/single element of stream)
*** Non-runtime attributes of modules (cache check, automatic conversion check, constant from/to string)

'''Items to Discuss'''
* User Survey

* ZMQ failing on windows (vistrails-users)

* [TE] [https://github.com/VisTrails/VisTrails/pull/1143 Python 3 branch]
** Testsuite almost passes
*** Failing are unicode filenames, some users guide examples, and thumbnail comparisons.
** Fixed issues
*** Signatures are now bytes (convert to string to show in widget)
*** Cannot compare different types, e.g., (None < 1)
**** PortSpec.depth and min/maxConn could be None. (Backport!)
**** cell.row could be None
*** Lots of unicode/bytes fixes to serializations
**** We have encryption implementations in the code! (keychain)
*** Lots of small fixes to package method differences
** Current issues
*** logging widget empty?
*** version tree signals messed up
*** provenance view legend icons black
*** Text do not fit in some widgets
*** VTK thumbnail comparison fails
**** VTK Cells have some faces in wrong direction?
**** Because running in VM?
** Installing on Ubuntu LTS/Latest Mint
*** Install latest matplotlib from pip
*** Install VTK 7.0.0rc2 from source
*** No QtWebEngine binary (controversial) (Must install sip/PyQt5/Qt5 from source)

=== January 20, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Backporting features from Python 3 + PyQt5 + Qt5
** Merged unicode with master ([https://github.com/VisTrails/VisTrails/tree/unicode unicode])
*** One unicode test failing
*** Problem saving to xml
** Used [http://python-future.org/ python-future] to run futurize stage 1 to update legacy (pre 2.6) code ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized unicode-futurized])
*** Updates print to functions 'from __future__ import print_function'
*** Updates exception calls to use 'as'
*** removes most usages of 'long' (mostly used unnecessarily)
**** Only needed for 32-bit support
*** Fixes relative imports (from __future__ import absolute_import)
** Fixing code that is deprecated in Qt 4.8 and removed in Qt 5 ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized-qt5 unicode-futurized-qt5])
*** Updated all signals to new-style
* If we go 2 to 3, this could break packages
** means we should schedule any package format changes for the same time
** e.g., imports should be unrelated to code path (function to load module from package identifier?) (take them out of vistrails.* [https://github.com/VisTrails/VisTrails/pull/1002 #1002])
** any structural changes (e.g. the __init__ versus init thing) (RR thinks it makes sense, though having both named "init" is unfortunate)
** putting package identifier as xml?
*** Python not so bad, plus some stuff in there is Python code (checking dependencies)
** version the APIs?
*** RR planning on versioning vistrails_module.Module, no point versioning the whole package?
* file formats on 2 to 3:
** no real translation/upgrade, but non-ascii values that work on 3 won't load in 2

=== January 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://gist.github.com/rexissimus/dfd27e466427529c385c Porting to Python 3 / PyQt5]
** Basic GUI and execution works
** Minimal work to support 2to3
** Hard to support both PyQt4 and PyQt5

=== January 6, 2016 ===
'''Updates'''
'''Items to Discuss'''
* Updating VisTrails dependencies
** Successfully built [https://gist.github.com/rexissimus/f1a1aada7de1c00a57c7 Win7-64/Python3/PyQt5/Qt5/WebEngine/VTK7]
*** VTK 7 is the first supporting Python 3 but is only in release candidate phase.
**** Next version of VTK 6 is rumored to support Python 3
**** There is a development branch of VTK 6 supporting Python 3
*** Can travis build this?
**** We can skip tests for WebEngine and VTK if needed
** Python 3 [https://python3wos.appspot.com/ showstoppers]
*** No MySQL-python (sqlalchemy supports mysql through other drivers)
*** No suds (there are active forks but we could also drop support?)
* Options for python2/3 support:
** Interpreter could be python2/python3 based on packages
** six layer works but not the easiest to maintain (e.g. in reprozip)
* Drop support for win-64
* Update copyright headers to 2016

== 2015 ==

=== December 30, 2015 ===
'''Updates'''
* Bokeh package finished
** Can output to Browser/IPython/Spreadsheet (Limited functionality in spreadsheet)
'''Items to Discuss'''
* Updating VisTrails dependencies
** Bokeh needs QWebEngine (Chromium) in Qt5 which requires PyQt5
*** Many plotting libraries only work in browsers
*** But Chromium may be a big and controversial dependency
*** Or create a browser version of the spreadsheet?
** Some users have requested Python 3
** Not backwards compatible?
** Target for VisTrails 3.0 with new interpreter?

=== December 16, 2015 ===
'''Updates'''
'''Items to Discuss'''
* Users list question
* [TE] Wrapping Bokeh
** Added bokeh property parser
*** complements numpydoc parser
*** Not all attributes are available, partially because I am using a pre-release version.
** Wrapped modules
*** bokeh.plotting finished (Backwards like matplotlib: Create plot then draw on it)
*** bokeh.charts mostly done (Missing arguments)
** QWebView mostly works (but no zooming or buttons)
*** It would be better to use external browser or QWebEngineView
** Added improvements to wrapper
*** Generalized port translations (Color/Path to native types)
*** Can use multiple docstring/property parsers simultaneously

=== December 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Looking into wrapper
** Will port TensorFlow
** Doing a pass on the wrapper code & doc
*** UX improvements
** Factorize high-level docstring parsers into core.wrapper? (sphinx, numpy, google)
** Problem with name vs module_name (fails sklearn tests because class_by_name() is broken)
** Looking into compressing specs, lazy registration of modules

=== December 2, 2015 ===
'''Updates'''
* [TE] Package wrapping
** Wrapped most of numpy/scipy using __all__
** Added class attribute and method access for classes (Can add to class or to separate inspector module)
** TODO: Document wrapping procedure

'''Items to Discuss'''

=== November 25, 2015 ===
'''Updates'''
* [RR] New interpreter is coming along
** Everything is a stream
** Task system, eventually work-stealing parallelism
** Streams no longer advance in lock-step
*** Allows for constructions like filter, join, sorted-merge
** depth>1 still to be tested, no current plan to allow this through the module interface
*** Through looping though, can do streams of streams

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapped most numpy functions (no polynomials)
** and half of scipy classes and functions
** Added functions manually from documentation (no parseable lists?)
** Focusing on data flow constructs (no property/method access for classes)
*** Using spec diff (empty for now) and dynamic parser (stores spec in .vistrails/)
** Python class/function wrapper now stable
** Add google doc parser?
*** Is there a parser available?

=== November 18, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Numpy class wrapping works
*** Basic type is List, since most types are array_likes.
*** TODO: More classes and functions
*** Some operations are in-place and some aren't, and docstring not super clear
*** [RR] It seems only methods mutate, and most have a numpy.xx function equivalent; just manually go through the methods and remove the mutating ones?
** Class wrapper is modular
*** Docstring parser and type string parser can be customized
*** Classes can have optional attribute/method ports
**** Inspectors and attribute/method modules can be created separately
** Use PythonCalc as an example
*** Can be re-implemented as a function with a parseable docstring
*** [RR] PythonCalc is just an example, and it might actually make sense to get rid of it, or do a proper math package with scalar operations (as separate modules, no combobox)
** [RR] TensorFlow to use wrapping as well
*** Very simple (only types 'tensor' & 'variable')

=== November 11, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapping numpy's classes using numpydoc (ndarray)
*** Wrapping constructor arguments, attribute getters/setters as module ports
**** Then how to access attributes afterwards?
***** Use input value port to class modules?
*** Wrap methods as modules? E.g., `ndarray.shape`.
*** Function wrapping is almost a subset of class wrapping
**** May be able to use the same parsing/execution methods
** VTK's non-getter/setter methods could be wrapped as modules
*** We could then remove extra logic in interpreter for keeping function order
** Bokeh uses autogenerated docstrings
*** We may be able to read the specification directly

* [RR] [https://github.com/VisTrails/VisTrails/pull/1138 TensorFlow package]
** Basic setup working, can execute the Mandelbrot example
** Will autogenerate the operations

=== November 4, 2015 ===
'''Updates'''
* [RR] Interpreter work requires a fix for [https://github.com/VisTrails/VisTrails/issues/1137 DB issue #1137]
* [DK] Kitware's Resonant [http://www.kitware.com/source/home/post/173]
** [https://github.com/girder/girder Girder]: data management system
** [https://github.com/Kitware/romanesco Romanesco]: execution engine, uses [http://www.celeryproject.org/ Celery] for task management
** Resonant Flow: web app for editing and executing workflows

'''Items to Discuss'''
* [TE] Added OSX Lion (10.7) VM on build machine using vagrant (seems ok with license?)
** New builds works on Lion
** Change the minimum requirement to 10.7?
* [TE] Package wrapping
* Added upgrade suggestions using 2 spec versions ([http://pastebin.com/30XUU8Gp example])
** using name edit distance to find matches
** Could use something better like port similarity for modules, and type similarity for ports
** Should write python upgrade code?
** Added spec to sklearn package
*** Can now diff spec versions and keep the spec static
*** There will be problems with downgrades and package versions

=== October 29, 2015 ===
'''Updates'''
* [TE] nightly-build-mac fixed (Needed to approve xcode license)

'''Items to Discuss'''
* [TE] matplotlib wrapper
** ported to general spec
** Diff can be used on general spec
*** Only needed minor changes
*** Fixed indexing bug that corrupted specs
*** Can now move diff tools to core/wrapper
** Add new plots?
*** New plots in mpl 1.3: eventplot
*** New plots in mpl 1.4: angle_spectrum, magnitude_spectrum, phase_spectrum', violinplot
*** No new plots in mpl 1.5 (from looking at boilerplate.py)

=== October 21, 2015 ===
'''Updates'''
* [RR] Alexis has arrived, will be working with [RR] on a more efficient interpreter

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package]
** Supporting multiple package versions
*** Check which version can be loaded [https://github.com/VisTrails/VisTrails/pull/1135 #1135]
*** We cannot show version requirements in the list of packages because old packages are loaded when importing the codepath
** Visual diff does not work well, but we can use the spec differ to see differences.
** Unifying vtk and matplotlib wrapping specs (WIP)
*** And porting matplotlibs spec differ to work on the general spec
*** Spec differ can then be used on vtk and other packages in the future
*** Will enable automatic upgrade generation
* [RR] Rework interpreter
** restore abstraction between interpreter/module code
** build looping, streaming, caching into the interpreter
** rework cache
** look into parallelism once basic functionality is there

=== October 14, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package] (adding numpydoc parser)

=== October 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/tree/fix-matplotlib-parser New matplotlib parser] (adding numpydoc parser)
** Added numpydoc attribute parser for plots.
*** TODO: Need better port spec reconciliation with call signature parser.
*** We can create a general numpydoc parser, but attribute types are unique to matplotlib.
** Needs package versioning
*** New spec will not support matplotlib < v1.4 due to changed path to axes classes.
*** Load spec version corresponding to installed matplotlib version?
*** Need version downgrades?

=== September 30, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Updating Matplotlib parser
** Matplotlib docstring parser fails on numpy docstrings
** I have [https://github.com/VisTrails/VisTrails/commit/eae8b0c16260810587e47c41cab53552cbb3cf0a added basic numpydoc parsing]
*** Only used by a few docstrings so far
*** Parsing uses many sources (class tables, signatures, ACCEPTS, method docstrings, definition parsing).
** Caswell said they were thinking about moving to traitlets, but this is not ready yet

=== September 23, 2015 ===
'''Updates'''
* [TE] VisTrails 2.2.3 released
** Also have pushed to PyPI, binstar, etc.
** Sourceforge vs. GitHub
*** should be able to host releases on GitHub
*** nightly binaries pushed to sf each night
*** old binaries?
* [TE] Re-wrapping MatPlotlib
** Keep static generation - Docstrings are brittle beween matplotlib versions
** Keep generating the executable classes - but create functions, not vistrails Modules
*** Why is there so much patching?
** Re-implemented Alternate PortSpec for InputPortSpec
*** It will now inherit specs from parent (No need to reimplement)
** Module upgrades?

'''Items to Discuss'''

=== September 16, 2015 ===
'''Updates'''
* [TE] Job Monitor tests and documentation done
** OK to leave document package in packages directory?

'''Items to Discuss'''
* [TE] Library wrapping: How to do code patching? [https://docs.google.com/drawings/d/1Sh3eOXot6v2y880jHKQrqXqAwr-0aoqYligg3z8G8MY/edit?usp=sharing Wrapping diagram]
** Insert code into module template (Old VTK code)
** Patch the library that is called (New VTK code)
** Somehow store code in spec and apply when executed?
*** Executed code needs at a minimum access to inputs, outputs, current class
*** Use standard input/output dict and obj reference that the code operates on?
*** Can this be done while keeping the execution abstract?

* Do new release now?

=== September 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* New release?
** [RR] wants reprounzip
** tej changes & doc
** job monitor & jobmixin fixes
** mongodb
** reprounzip
** warning: MplFigure type is int
** tabledata: add Reshape, DictoToTable & ListToTable, fix ListToTable with numpy arrays
** PythonSource can have same name for an input & output
** don't show spreadsheet at exit

=== September 2, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Limit autosaves? [https://github.com/VisTrails/VisTrails/pull/1126 #1126]

=== August 26, 2015 ===
'''Updates'''
* [TE] Added Job support to Parameter Explorations (Requested by Colin), and Mashups
** specify job ids, need to specify different ids for parameter explorations since they have the same version id
** how to deal with parameters passed in on command line
* [General] provenance: should be creating a new version when we execute workflow with changed parameters?
** currently, custom_params annotation stores this in provenance currently
** [RR] API doesn't record provenance if passing in parameters: http://git.io/vsAA5
'''Items to Discuss'''

=== August 19, 2015 ===
'''Updates'''
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [TE] Working on Job Monitor documentation

'''Items to Discuss'''
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [TE] Stop testing VisTrails 2.0?

=== August 12, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Build broken on Travis; because of IPython 4 released today? ([https://travis-ci.org/VisTrails/VisTrails/builds/75279795 build 992]; [https://github.com/VisTrails/VisTrails/issues/1123 #1123])

=== August 5, 2015 ===
'''Updates'''
* [TE] Fixes to Jobs
** Could not delete jobs
** Could not run job in group
** Job not reset when calling ModuleSuspended
** Added deleting job from context menu
* [RR] Writing documentation for everything [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

'''Items to Discuss'''

=== July 29, 2015 ===
'''Updates'''
* RR still looking into new interpreter thing
** Goal is to take out scheduling logic from Module so it can be split in multiple processes, and so that smarter strategies can be added in time
** This means some work on packages
** Spreadsheet can live in kernel process? Still some UI stuff that will take work (changing configuration, persistent archive's viewer, ...)
* [TE] Problems running examples [https://github.com/VisTrails/VisTrails/pull/1111 #1111]
** Testing of more examples requires additional packages on the test machines.
** Fixed faulty line-ending in PythonSource:s failing on Python 2.6.
** Test suite now testing SUDSWebServices (If web service is down, test suite will fail)
** preferences.py test failed reloading 'dialogs' package, switched to using 'URL'.

'''Items to Discuss'''

=== July 22, 2015 ===
'''Updates'''
* [TE] mailing lists back online
* [TE] Working on [https://github.com/VisTrails/VisTrails/issues/1107 #1107]
* [RR] Working on ReproZip package

'''Items to Discuss'''
* [RR] MongoDB package [https://github.com/VisTrails/VisTrails/pull/1106 #1106]
* [RR] Example for tej docs? [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

=== July 15, 2015 ===
'''Updates'''
* 2.2.2 released

'''Items to Discuss'''
* RR is considering executing everything in an IPython kernel (i.e. separate Python interpreter, like the one spawned for a notebook)
** It's a separate process that we can restart without restarting the app/gui
** We can isolate the execution environment (e.g. for the server)
** We can run the whole thing remotely (if your data is elsewhere, just run VisTrails locally and the pipeline elsewhere)
** Pipeline execution no longer makes the interface hang, it just makes the kernel hang (but that's fine)
** We can use notebooks as modules (probably way nicer than the PythonSource module)
** We can run multiple kernels so long as the ports carry things that are serializable
*** meaning we can put the multithreaded-interpreter without all the hacky parts it has now
*** we can run IPython kernels in all the languages IPython supports, [https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages currently 46]

=== July 8, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Buildbot github hook not working after IP address change
* [TE] No reference to VistrailsApplication ([https://github.com/VisTrails/VisTrails/issues/1103 #1103])
** [RR] Added PR [https://github.com/VisTrails/VisTrails/pull/1104 #1104]
* [TE] Reopening VT file after saving with bundled subworkflow won't offer subworkflow upgrade ([https://github.com/VisTrails/VisTrails/issues/1102 #1102])
** allow manual delete to fix right now
** fix this on top of the use-uuid branch
* [TE] Release VisTrails 2.2.1? ([https://github.com/VisTrails/VisTrails/blob/v2.2/CHANGELOG CHANGELOG])
** [https://github.com/VisTrails/VisTrails/pull/1093 output-modules-use-global-dir]
** [https://github.com/VisTrails/VisTrails/milestones/version%202.2 Current issues for 2.2]

=== July 1, 2015 ===
'''Updates'''
* [TE] PROV fixed
* [TE] Working on subworkflow issues
* [RR] Considering reworking the controller (log vs exception problem, retained upgrades causing interferences) and also the interpreter (IPython?)

'''Items to Discuss'''

=== June 24, 2015 ===
'''Updates'''

'''Items to Discuss'''
* UV-CDAT
* [TE] Can a cyclic workflow be valid? ([https://github.com/VisTrails/VisTrails/issues/1097 #1097])
** focus on disabling the ability to create cyclic pipelines because more things break than just this with a cyclic pipeline
* [RR] Relative paths ([https://github.com/VisTrails/VisTrails/pull/1057 #1057])
** This interacts with the new bundle; how do handle packing files inside the VT bundle?

=== June 17, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] current_version and reusing existing upgrades are broken ([https://github.com/VisTrails/VisTrails/issues/1095 ticket #1095])
** Could be that export to PROV is using an unflushed upgrade pipeline?
** current_version would then be correct.
** It may work to flush the actions before exporting?

=== June 10, 2015 ===
'''Updates'''
* DAT: fixed VTK issue on Linux and Mac
* Still crashes on Windows. Need help! Reminder: this works in the VisTrails spreadsheet (QCellPresenter), although no widget get changed there during a drag
** Is it a VTK bug?
** Is it simply impossible to change widgets during the drag, should we do it a different way?
** Did I miss something that is done in VisTrails but somehow not in DAT?
** Low prio, UV-CDAT doesn't run on Windows anyway

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 Updated pull request])
* Single instance code and batch mode

=== June 3, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 pr])
** Requires fixes to command line parameters, Output modules, and batch mode
** How to test this
** Updated missing/outdated flags
** Fixed view issues when generating graphs
* [TE] batch mode
** SpreadsheetOutput not enabled in batch mode. Should we check is_running_gui instead?
** Other instance setting flags from caller
** Is graphsAsPdf replacing spreadsheetDumpPdf?
** graphsAsPdf true by Default?
** Batch mode executing by default (Not needed when generating graphs)
** Re-added workflowInfo as withWorkflowInfo for writing graph and xml workflow
** [DK] batch mode should be outputting to files or stdout, shouldn't always trigger SpreadsheetMode
** execute flag, maybe make execution the default and allow a "--no-execute" if you only want to capture graphs, for example

=== May 27, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] API question
** http://lists.vistrails.org/pipermail/vistrails-users/2015-May/000357.html
* Status of DAT
** Can add VCS plot to DAT but need to work on configuration windows
** Documentation for graphics templates for UV-CDAT/vcs?
* Qt support?

=== May 20, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Reviving the DAT, integrating scripting & porting UV-CDAT!
** On [https://github.com/VisTrails/DAT GitHub] ([https://github.com/VisTrails/DAT/issues issues])
** Merging 2 years of development taking longer than expected, but getting there. The plan is to get the patches in VisTrails and never fork again, we never want to get in UV-CDAT's situation (and don't need to).
** VTK cell works fine on Linux but there was flickering on Mac & Windows before; still issues on Mac (Windows status unknown)
** Can get a VCS plot soon (but will need VTK cell fix)
** Integrate in UV-CDAT's build system (so we have cdms, VCS, ...) -> RR can do this, low priority
** How do we integrate scripting?
*** We want to be able to seamlessly make changes to a plot by changing Python code
*** Define new plots by entering Python code without writing modules/packages?
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 13, 2015 ===
'''Updates'''
* [RR] Test skipping whitelist ([https://github.com/VisTrails/VisTrails/pull/1069 #1069]) -- low priority
* [RR] Custom matplotlib modules can't be compatible with both 2.1 and 2.2 ([https://github.com/VisTrails/VisTrails/issues/1067 #1067]); should be fixed for ALPS ([https://github.com/VisTrails/VisTrails/issues/1070 #1070])

'''Items to Discuss'''
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 7, 2015 ===
'''Updates'''
* [RR] Export/import workflow to Python working!

'''Items to Discuss'''
* [Claudio] UV-CDAT
** The UV-CDAT project is the biggest user base of VisTrails
** VisTrails package management provides a lot of friction towards people plugging in their code
** Need to make it easy to integrate your random Python scripts in the system without having to deal with all the boilerplate, at least in the first step
** [RR] argues that modules are still good; UV-CDAT shouldn't move towards a purely script-based backend
** [RR] export/import with Python could reduce a lot of that friction by allowing 1) to edit workflow as Python 2) to open up boxes automatically if needed code doesn't match actual modules
** ...

=== April 29, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] <strike>Abstractions</strike> subworkflows status ([https://github.com/VisTrails/VisTrails/labels/subworkflows tickets])
* [RR] matplotlib compatibility (2.1 & 2.2), [https://github.com/VisTrails/VisTrails/issues/1067 #1067]
** RR to try and fix ALPS matplotlib modules

=== April 22, 2015 ===
'''Updates'''
* 2.2.0 has been released!
* Windows issue (via email from Ryan)
** issue with manifest file (may be a new file in VTK6?)
** Tommy has regenerated new Windows builds
* Binaries, pypi, and conda released
* [RR] Export as script
* Python sources using VTK need to switch to SetInputData (users should be aware of this)

=== April 15, 2015 ===
'''Updates'''
* Ready for 2.2.0 (apart from binary/deps issues)
** Missing some libs (scikit-learn, tej, tdparser, SQLAlchemy+connectors
** Windows: runvistrails.py is no longer used, so the PATH is wrong
** Windows: pip is broken, but it probably wouldn't work anyway because of permission issues (disable this?)
* Queries, upgrades and getPipeline() usage ([https://github.com/VisTrails/VisTrails/issues/1054 #1054])
** Getting a pipeline with getPipeline() is not safe: it might return an invalid pipeline
** This is used in many places throughout the code, like queries
** Upgrading would require going through the controller, but that creates new actions
* [TC] Avoid copying a module's output if it's used as input by exactly one downstream module ([https://github.com/VisTrails/VisTrails/issues/1060 #1060]) (useful for big numpy arrays you can update in-place)

=== April 8, 2015 ===
'''Updates'''
* [DK] Merged RR's changes for output modules (1012 and 1013)
** RR will merge remaining changes, then create v2.2 branch!

'''Items to Discuss'''
* BNL need numpy array to VTK image
** Looks like VTK has some helpers for this
** We will help if issues arise
** Will contribute back to VisTrails package
* Upgrade issue: [https://github.com/VisTrails/VisTrails/issues/1017 #1017]
** Automatic upgrades should happen between versions of provided upgrades
** Our existing upgrades work around this so it doesn't need to be 2.2.0
* Corner-case VTK modules
** No longer need VTKCell input port, so don't interfere with registry and API anymore
** Still work weirdly, people probably shouldn't use them
** But we have lots of clunky modules since we wrap the whole of VTK; some people might rely on this and know how to use them, let's keep them anyway
** Ready for 2.2.0

=== April 1, 2015 ===
'''Updates'''
* [RR] UV-CDAT: bugfixing for 2.2, long-term plans: implement scripting import/export in VisTrails, port to UV-CDAT
* Possibly, try to move to regular VisTrails to use new features

'''Items to Discuss'''
* 2.2 release: nothing much is pending anymore, release next week?
** [TE] vtkExporter classes [https://github.com/VisTrails/VisTrails/issues/1032 #1032]
** [RR] Hiding upgrades in version tree might make it (or might be 2.2.1 so we can test it out) [https://github.com/VisTrails/VisTrails/issues/949 #949]
** Output modules changes to go in
* add note to documentation about order of parameters in VTK
* add issue about exporter upgrades if not already there

=== March 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* 2.2 release
** Checklist on Github: https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist
** Review output modules
** RR has a couple more issues to fix
** Ready to go -- sign app package for OSX? [https://github.com/VisTrails/VisTrails/issues/984 #984] We need access to the Apple Membership team

=== March 18, 2015 ===
'''Updates'''
* [TE] VTK6 works

'''Items to Discuss'''
* [RR] Release v2.1.5 with backported tabledata?
** MTA example needs updated tabledata (for JoinTables)
** Google Maps package still not available
* [RR] Work torward v2.2.0?
** changes:
*** new persistence
*** API changes
*** output module changes (upgrades?), maintain cells but try to upgrade
*** not wrapping stuff
*** VTK6? yes
*** JobSubmission stuff?
*** relabeling for upgrades [https://github.com/VisTrails/VisTrails/issues/949 #949]
** makes sense, needs the tree view code to be updated, check selection
** See [https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist 2.2 checklist]
* Discussion of [https://github.com/VisTrails/VisTrails/issues/1016 #1016]
** plumbing between outputs and output modes, how to define a mode that works for many outputs without writing for each output?

=== March 11, 2015 ===
'''Updates'''
* [RR] persistent_archive done; merge? ([https://github.com/VisTrails/VisTrails/pull/755 #755])
** note about the focus events for widgets
** TE be aware of file_archive for future binaries that include persistent_archive
* [TE] [https://github.com/VisTrails/VisTrails/pull/998 New VTK package] finished

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails? (see last week; decision needed)
** RR email to JF about this
** yes; email sent to Github
* [RR] Switching order of output ports ([https://github.com/VisTrails/VisTrails/pull/1006 #1006])
** added port specs are sorted at a separate spot (Module.*_port_specs properties) than those in the registry (which are sorted in the registry), but those two lists are just combined without respect to sort keys
** need to determine whether the two lists should be merged or remain distinct
** should make sure that order of input ports and output ports makes parallel connections for things with same order
** DK suggests breaking backward compatibility here: workflows still run, can fix easily if a problem in an existing package.
* [RR] Question about output modes ([https://github.com/VisTrails/VisTrails/pull/1007 #1007]), how to integrate in API ([https://github.com/VisTrails/VisTrails/pull/24 #24])
** Should ImageFileMode be removed? ("image" is not a mode, "file" is)
** ImageOutput missing?
** Feel free to change how formats works
* [TE] Test suite segfaults on Fedora 17 virtualbox. Install newer version? (Support ended in 2013)

=== March 4, 2015 ===
'''Updates'''
* [TE] VTK wrapper
** Works on VTK 5.10
** Still need to test VTK 6
** New general wrappers for python functions and classes

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails?
** When [http://i.imgur.com/UTY2qfg.png filing a pull request] from UV-CDAT/VisTrails, VisTrails/VisTrails is selected by default
** People keep forgetting to change the default ([https://github.com/VisTrails/VisTrails/pull/956 #956] [https://github.com/VisTrails/VisTrails/pull/968 #968] [https://github.com/VisTrails/VisTrails/pull/999 #999] [https://github.com/VisTrails/VisTrails/pull/1000 #1000] [https://github.com/VisTrails/VisTrails/pull/1003 #1003] [https://github.com/VisTrails/VisTrails/pull/1004 #1004] [https://github.com/VisTrails/VisTrails/pull/1005 #1005])
** Only way to change that is to not have it marked as a fork of VisTrails/VisTrails
** Github staff [https://gist.github.com/remram44/b364c24ef1e462ce6e2f can make that change for us]; should we do it?
** Juliana: comments on this? visibility vs. convenience/annoyance for developers
* [RR] What about [https://github.com/VisTrails/VisTrails/issues/991 #991]?

=== February 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] vtkviewcell for infovis support, can we unify with VTKCell?
** need to test this
* [TE] vtk wrapping
** Mostly finished
** VTK 5.10 produce incorrect results with old wrapping
*** Old wrapper is based mostly on VTK 4
*** Most vtk_examples affected
*** [http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Replacement_of_SetInput]
*** should be able to upgrade from SetInput to SetInputData (need to drop GetOutput and replace with self ports)
*** can we change vtkInstance to just return self and not wrap things
** terminator example not working under 5.8?
* How does VTK wrapping fit into general wrapping framework?
* [RR] new persistence package

=== February 18, 2015 ===
'''Updates'''
* [RR] New VisTrails API and IPython integration ([https://github.com/VisTrails/VisTrails/pull/24 #24])

'''Items to Discuss'''
* [TE] VTK wrapping
** [https://gist.github.com/rexissimus/16b74693545b5e7c1035 Benchmarking vtk package]
*** Old: 24.7 seconds
*** New: 10.5 seconds (Except first time that adds 8 sec)
**** The parsing that calls is_abstract (that tries to instanciate all vtk classes) is now only run the first time.
**** get_items_from_sigstring takes 2 seconds, maybe we can use a lookup dict for already computed sigstrings?
** Now using a general python function wrapper
*** VTK classes are wrapped into python function that does not depend on vistrails
*** VTK functions can be executed without vistrails
*** The spec maps functions into vistrails modules, but can also describe wrapping
*** A general python function wrapper that supports
**** kwarg inputs
**** single, list, dict outputs
**** callback for progress reporting
**** temporary file generator for using FilePool
**** optional output generation
*** Creating specs:
***** Create spec by hand
***** Auto-create spec outline (TODO) and manually finish it
***** Dynamically create spec (VTK)
***** Implement documentation wrappers (Can use scikitlearn wrapper to wrap numpydoc) (TODO)
***** Classes as bad functions needs to be wrapped in new functions before they are wrapped. This is different for each package.
****** Classes is hard: Like VTK, and matplotlib. Scikit-learn does still not wrap classes
***** Spec diffing and patching could be done using code from matplotlib.
** Still needs upgrades from old VTK package
*** Is it possible to dynamically wrap functions, e.g, you see a SetFunc and just remove the 'Set' prefix. Or do you need to create a complete mapping?

=== February 11, 2015 ===
'''Updates'''
* Update from Friday's meeting
** discussed VisTrails internals
** discussed wrapping
*** xml discussion, hard to modify because tied to db code
*** TE has made it possible to add the schema-defined attributes to the intermediate representation
*** higher-level operations on the port specs
** make sure the simple case works
*** [JF] take a simple package with documentation and figure out what the base case for wrapping is

'''Items to Discuss'''
* [TE] VTK wrapping
** Dynamic loading works
** Reading XML is fast enough, but [https://gist.github.com/rexissimus/8272d3c776ccfa115d82 unserializing data is slow]
** Working on patterns for patching
** Matplotlib has many advanced patterns like argument ordering, nested arguments, alternateSpecs, output types.
*** Having all this in a general wrapper might confuse users?
** [RR] Delay module (except for identifiers) until you need it---e.g. don't deal with port specs, etc. until necessary
* Scripting Support [https://github.com/VisTrails/VisTrails/pull/950 #950]
** [RR] Issue with getting code from modules
** Design a simple solution
** [JF] Couldn't you use modules as black boxes without conversion, just to call into modules/subworkflows easily from e.g. IPython?
*** [RR] This is a job for the API, and a very separate use case. See [https://github.com/VisTrails/VisTrails/pull/24 #24]

=== February 4, 2015 ===
'''Updates'''

'''Items to Discuss'''
* Wrapping
** Format to use? Currently XML (like current matplotlib)
*** JSON and YAML have simple "to python dictionary" methods
*** But don't stream
*** YAML a lot easier for humans
** [DK] vtk-new-package also changes parameter names, creates enumerations
*** intermediate schema needs to be extensible
*** packages will want to store there specific infos for compute() method generation
*** also might have specs-altering info, like matplotlib's alternateSpec
** representation to code , registry already has schema for some aspects
** [RR] We might want to see if Module subclasses can be created lazily
*** no need to create all the classes just to register them in the registry and never actually use most of them
*** future effort
* [RR] Where should VisTrails packages live?
** tej installs as 'vistrailspkg.tej', TE installed it as 'userpackages.tej'
** Currently, standard packages are 'vistrails.packages.', user packages are 'userpackages.' and packages loaded through pkg_resources might be anything
** [RR] Use 'vistrailspkg.' everywhere?
** Long-term effort to simplify package distribution/installation (and have VisTrails get them automatically?)

=== January 28, 2015 ===
'''Updates'''
* T. Caswell to come visit on Fri 6 to discuss wrapping work

'''Items to Discuss'''
* [TE] New VTK wrapping
** Current code by DK seems a good deal faster
** Generates XML that can be patched/tweaked, generates Python code from it, VisTrails only loads generated Python code
** RR would rather have VisTrails load intermediate representation (= XML) directly, wants to make sure this is not slower
** The goal is to turn the intermediate step into something generic that would be used for every wrapped package (vtk, numpy, matplotlib, sklearn, java) instead of each having its own
** TC has its own code at [https://github.com/Nikea/VTTools/blob/master/vttools/wrap_lib.py github:VTTools] which parses numpy docstrings and generates modules, doesn't yet handle classes or persist anything
* Web crawler
** Right now, TE starts jobs for "start crawler", "stop crawler", "install classifier"
** RR would rather have the crawling be a job as far as VisTrails and tej are concerned
** The whole thing would be one pipeline: load examples, train classifier, start crawler [check for job, kill previous one, upload model, start processes], get snapshot, visualize
*** Need some support in tej and job submission system: long-running jobs, stop a job (wait for it to finish?), restart a job even though results are cached

=== January 21, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Unified wrapping method discussion [https://github.com/VisTrails/VisTrails/issues/991 #991]
** TE to work on reusable method with intermediate representation, starting with VTK
* [RR] Examples for scikit-learn: JF has an old example using Weka with parameter exploration (not currently in source tree)
** AM's examples are enough
* [AM] scikit-learn package is done, merge it in? [https://github.com/VisTrails/VisTrails/pull/955#issuecomment-70286788 #955]
** RR will merge
* [RR] What should copyright headers say? [https://github.com/VisTrails/VisTrails/pull/994#issuecomment-70173935 #994]
** Let's keep everything in there: Utah/Poly/NYU

=== January 14, 2015 ===
'''Updates'''
* [TE] Working on classifier
* [RR] Scripting integration, work in progress

'''Items to Discuss'''
* [RR] Unified wrapping method discussion ([https://github.com/VisTrails/VisTrails/issues/991 #991])
** Let's talk next week, [AM] and [DK] are not here

=== January 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* make sure that we address critical issues, questions, and pending review branches in a timely manner
* scripting support
** [RR] no issues if we want to just keep annotations in the generated code to allow the link back to a workflow
** [RR] can translate from workflow to script, working on script to workflow
** will work for parameter value changes, structural changes require changes to the annotations
** need to publish best practices here
** would be cool to do looping in scripts (easier interface than with workflows)
* notebook support (convert form notebook to workflow)
** RR will sync with FC on this
* Issue with console in built-from-scratch
** [TC] iPython rearranged some of the completion stuff in 2.2 and 2.3
** binary has old version of iPython -> 1.0.0, should we update?
* [TC] automated wrapping of numpy and scipy
** discovered a bunch of malformed documentation in numpy and scipy
** has github repo for vistrails tools
** example modules wrap a bunch of R stuff (not baked in, just how things are)
** will be pushing wrapping logic up
** port names forbidden (window and domain)
** have an import hook to get from yaml directly to VisTrails Modules
** should work for any python modules with well-formed numpy docstrings.
* [Action] should make it clear in documentation that Constant now means serializable not that the value doesn't change (e.g. List)
* [TC] might be interesting to try to build components of matplotlib and accumulate in figure (long-term project, but thinking about how this might work)
* [TE] build and build scripts
** completely automatic, buildbot
** need to set the build machines for the environment we want for the binary
** would virtualenv work here?
** [TC] anaconda can pin versions, potential path to test different configurations
** Q: upload nightly binary builds? A: makes sense, make sure they are well-labeled
* sourceforge stats: e.g. http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07
* package issues (see Remi's message)
* [TE] Scope of tej
** Support single ssh commands?
** Queue can be used as a remote machine (crawler is using queue.call*)
* SourceForge stats: http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07

== Older meetings ==
* [[Development/2014]]
* [[Development/2013]]
* [[Development/2012]]
* [[Development/2011]]
* [[Development/2010]]

Development

2016-05-11T14:48:47Z

Tommy: /* May 4, 2016 */

<div class="nonumtoc toclimit-1">
__TOC__
</div>

See also the [https://github.com/VisTrails/VisTrails/wiki/Development Github wiki]

== 2016 ==

=== May 11, 2016 ===

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]
** GUI-based solution [https://github.com/VisTrails/VisTrails/tree/union-port Branch union-port] Demo?
*** Shows single port for all ports with same sort_key
*** Select specific type when adding/showing
*** Only one type should be visible on the module at any time
*** Making tuple parameters union types is probably too complicated

* [TE] Feature suggestion: Let connections connect to functions/parameters
** Show functions and parameters as ports and toggle port visibility directly for functions and parameters
** Use separate views for ports and functions (like before)
*** Allow rearranging of functions
** Pros:
*** Supports ordered connections. Create 2 functions, make them visible as ports, make connections to them.
**** We can also have, e.g., a line joining the ports on the module to indicate they are part of a list.
**** Makes List module simpler
*** Connect to parameter in tuple
*** Functions that are visible on the module can connect to an actual function, and not just to the first one it finds.
*** Can replace operation modules (in python-wrapper) in some cases for, e.g., numpy.
** Cons:
*** Interface more complicated and crowded
*** More difficult for users to grasp?
*** No immediate use case
*** Makes no union type for tuple parameters a bigger problem.

* [TE] Publish user survey?
** No response from vistrails release yet
** Not announced on vistrails-users yet.

=== May 4, 2016 ===
'''Updates'''
* VisTrails 2.2.4 released

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]

=== April 27, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Wrapping Bokeh
** New method type "operation"
*** Transforms Figure->Glyph->Output into Glyph->Figure->Output
**** Glyph sets function name and arguments as output
***** Not serializable, but should always be computed together with the subject of the operation.
**** Figure applies Glyph operation on itself
*** Useful for matplotlib?
**** matplotlib currently find actors by searching upstream?
**** But this is more difficult since matplotlib is not function-based.
** New "union" port type
*** Turns "x(float), x(list)" into "x (float, list)" and uses first set value
**** Uses only first value in tuple
**** Bokeh have many properties that support (list, string, Float)
*** Does not work with depth=1 types (e.g. Float of depth 1)
**** Turn Depth 1 types with known type into lists?

* [TE] New bugfix release
** Finalize survey

=== April 20, 2016 ===
'''Updates'''
* Merged upgrade fixes
** Now has infinite loop test
** loop test now correctly loops 5 times
*** remap_module used wrong (current) package version when creating ModuleDescriptor
* Fixed multi-step group upgrades (PR: [https://github.com/VisTrails/VisTrails/issues/1168 #1168])

'''Items to Discuss'''
* New bugfix release
** Merge usagestats
** Need to finalize survey

=== April 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Chaining upgrades done ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Replace "Upgrade" description annotation with "upgraded_from" annotation to identify which tags to hide?

* [TE] Iterating handle_invalid_pipeline ([https://github.com/VisTrails/VisTrails/pull/1165 #1165])
** Not based on [https://github.com/VisTrails/VisTrails/tree/chain-upgrades-loop chain-upgrades-loop]
** Cherry-pick test to preserve source?
** Need maxPipelineFixAttempts option?
*** The code is now smarter about recursion, so max attempts will "probably" never be reached.
** Need [https://github.com/VisTrails/VisTrails/commit/0ef0667426937eddb1d1c1e397f0657ffec039a9 debug messages]?
*** Would need to be moved into handle_invalid_pipeline

=== April 6, 2016 ===
'''Updates'''
* [TE] Query View improvements
** Done except for displaying "Version Info" and #1164
* [RR] Working on finishing new interpreter (finally!)

'''Items to Discuss'''
* [TE] Chaining upgrades ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Try latest upgrade first, then previous.
** If all fail, select latest upgrade?

=== March 30, 2016 ===
'''Updates'''

'''Items to Discuss'''

* [TE] Query View improvements
** Unified do_version_switch and get_upgrades as validate_version()
** Problems with query view using its own controller
*** Fixed module info not being displayed for query results
*** Still no version info for query results
*** Still an issue with version query view not being updated

=== March 23, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Usage reporting almost ready to go
** Need to record whether specific features are used: paramexpore, mashup, query
*** [DK] Record if LaTeX extension is used? But hard to distinguish from direct batch invocation
** How to record size of vistrail?
*** [DK] IdScope already walks over vistrail, use that
*** but total number of modules and versions doesn't give an idea of average size of individual pipelines

=== March 16, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Upgrades in Query Mode
** Now using code similar to do_version_switch
*** Uses handle_invalid_pipeline
*** Differences: Not using current_pipeline, flushes changes
*** New controller method get_pipeline optimized using cached pipelines (but not current_pipeline)
*** Integrate to avoid repeated code?
*** Use this for query mode?
* [TE] VisTrails 2.2.4 ready for release?
** tej package updated. Others?
* [JF] upgrades and the version tree
* [JF] provenance in Jupyter
* [DK] bundles: [https://github.com/VisTrails/VisTrails/pull/1092 #1092]

=== March 9, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixing search mode
** String query now matches all by default
*** This caused pipeline queries to never match
** String query can search: User/Notes/Tagname/Time/Module name
*** Should we search module names by default? (Disabled by default because it is expensive)
*** Fixed notes search
** '>' parameter queries in documentation but has been removed
** Fixed module matches for upgraded pipelines (By not upgrading pipeline)
*** Upgrades still a problem
*** Add "Upgrade all menu option?" (Or upgrade all on open when `hideUpgrades`)
*** [JF] Allow search on past tags

* [TE] Create new bugfix release
** Finish querying
** Path issue on windows

* [DK] Look into sqlalchemy and new bundle branches

=== March 2, 2016 ===
'''Updates'''
* [TE] Fixed cache bug with port specs
* [TE] VisTrails Next
** Most packages now work
** No qgis for Python 3

'''Items to Discuss'''
** Always dereference symlinks? [https://github.com/VisTrails/VisTrails/issues/1146 #1146]

=== February 23, 2016 ===
'''Updates'''
* [TE] Fixed PythonSource 100% CPU bug
* [TE] VisTrails Next
** Updated [http://opendap.co-ops.nos.noaa.gov/axis/webservices/wind/ NOAA Web Service] examples
*** Now uses REST service, tabledata, and Google Maps
*** Web Service replaced with DownloadFile

'''Items to Discuss'''
* [RR] Couple of fixes are in for API, and tej&reprounzip on the Mac binary. Also new release of tej, and working on anonymous usage reports.
** New 2.2 release soon?
* [RR] Anonymous usage reports
** Sends out info like number of modules & versions, packages used, Python & libs versions, execution time, specific features [https://github.com/VisTrails/VisTrails/pull/1154 #1154]
* [JF] Bring in noWorkflow to track variable dependencies, for the considered Jupyter integration?
* noWorkflow - provenance for python scripts
** Recent work on tracking dependencies
* Also integrates ReproZip with Jupyter
** [http://mybinder.org mybinder]
*** Use with ReproZip to automatically build Jupyter notebook interfaces
* Daves comments on Jupyter integration
** It is possible to identify cell order on the server side
** Not trivial to track order of cells on client side
* How does Galaxy workflows relate to VisTrails?
** Packaging in Galaxy is hard
** Galaxy for biomedical workflows, difficulty making it general
* Action items
** How difficult to track cell dependencies in Jupyter notebooks?
** Use noWorkflow to track cell dependencies?
** How difficult to modify mybinder to use ReproZip packages?

=== February 17, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixed Group memory usage
** Modules in groups are supposed to be freed when done executing
*** Prevented by logger that stored references to the modules (fixed, now using id(module))
*** Prevented by list iterator bug that stored list of modules on the 'self' port bug (fixed)
* [TE] VisTrails Next
** Removed deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** PythonSources will be upgraded
*** Fixes for Python < 3
*** fixes for VTK < 6
** TODOs
*** Remove RemoteQ
**** Port Hadoop to tej (Already have pbs)
*** Merge package wrapper
*** Finish SQLAlchemy branch
*** Finish new bundle branch
** [JF] Will contact Jeff and Matthias about moving to Python 3
* [JF] Query by Example is broken
* [JF] VisTrails Data Cleaning Project
** Use VisTrails to process and explore task-specific data while keeping provenance.
** Remi's Idea
*** Use VisTrails as the backend in a Jupyter notebook
*** Overcome problems with executing cells in random order
**** Interesting research topic, but little interest has yet been noted
*** Interesting to study how such a notebook would be used (Is there notebook usage data available?)
*** Impose restrictions to notebook cell boundaries
*** It will only work for functional operations
*** Can we fix, or detect, non-functional (mutating) operations?
*** Analyse code and data flow and see if it mutates data in unexpected ways?
*** Mutable operations can be created in many ways in Python
* Next meeting Tuesday 11:30

=== February 10, 2016 ===
'''Updates'''

'''Items to Discuss'''
* VisTrails Next
** Test suite passes
*** Python 3 less deterministic, module upgrade order random.
** [RR] updating packages: Reprounzip (pushed), tej, persistent_archive, ...
** All of our packages should run fine :)
** VTK thumbnail comparison works
*** Rendering bug on some systems
**** QVTKCell now inherits QGLWidget
*** Old thumbnails had wrong height due to spreadsheetwindow being too small
**** Fixed by regenerating thumbnails
*** Silenced deprecation messages when generating modules
*** Many new classes in VTK 7
** Remove deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** Will break existing PythonSources
**** Try to upgrade?
*** Old-style packages
**** Or only allow a new style, like __init__.py renamed to info.py? (merge with identifiers.py?)
***** Read info.py without importing package?
*** Fixes for Python < 3
*** Fixes for Qt < 5
*** fixes for VTK < 7
*** Remove self port?

=== February 3, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] [http://lists.vistrails.org/pipermail/vistrails-users/2016-January/000402.html Rendering a .pvd (ParaView) file?]

* VisTrails Next
** All tests but thumbnail comparison passes
** Still issues with gui and more packages needs to be tested
** PythonSource and MplSource upgraded with lib2to3
** Keep contrib packages? Update?
** [https://blog.kitware.com/vtk-7-0-0/ VTK 7 is released]
*** Supports Python 3
*** Will hopefully get into conda and others soon
*** Deprecates a bunch of modules

* [https://travis-ci.org/VisTrails/VisTrails/builds/106743348 Travis builder] for VisTrails Next
** Runs!
** Uses conda
*** Many levels of requirements
**** apt packages
**** conda packages
**** python packages in requirements.txt
**** python packages in setup.py
*** Can probably drop conda. Default builder does not have Qt5, but beta builder do!
*** But useful if we want to use conda in our own build process.
** Lots of errors I do not get locally?

* [http://goo.gl/forms/Z4HBrwaBWL User Survey]
** Have you used any alternatives to vistrails?
*** Relevant? More options?
** How often do you use any of these particular features in VisTrails?
*** Add/Remove alternatives?
** How important would you rank the following potential improvements to VisTrails?
*** Add alternatives?

=== January 27, 2016 ===
'''Updates'''
* New interpreter
** Working prototype soon
** Looping not completely done (and port combination mode: pairwise/cartesian...)
** Need to integrate with VisTrails
*** Compatibility with existing modules
*** Use log controller
*** Want to cache at multiple levels (whole stream/single element of stream)
*** Non-runtime attributes of modules (cache check, automatic conversion check, constant from/to string)

'''Items to Discuss'''
* User Survey

* ZMQ failing on windows (vistrails-users)

* [TE] [https://github.com/VisTrails/VisTrails/pull/1143 Python 3 branch]
** Testsuite almost passes
*** Failing are unicode filenames, some users guide examples, and thumbnail comparisons.
** Fixed issues
*** Signatures are now bytes (convert to string to show in widget)
*** Cannot compare different types, e.g., (None < 1)
**** PortSpec.depth and min/maxConn could be None. (Backport!)
**** cell.row could be None
*** Lots of unicode/bytes fixes to serializations
**** We have encryption implementations in the code! (keychain)
*** Lots of small fixes to package method differences
** Current issues
*** logging widget empty?
*** version tree signals messed up
*** provenance view legend icons black
*** Text do not fit in some widgets
*** VTK thumbnail comparison fails
**** VTK Cells have some faces in wrong direction?
**** Because running in VM?
** Installing on Ubuntu LTS/Latest Mint
*** Install latest matplotlib from pip
*** Install VTK 7.0.0rc2 from source
*** No QtWebEngine binary (controversial) (Must install sip/PyQt5/Qt5 from source)

=== January 20, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Backporting features from Python 3 + PyQt5 + Qt5
** Merged unicode with master ([https://github.com/VisTrails/VisTrails/tree/unicode unicode])
*** One unicode test failing
*** Problem saving to xml
** Used [http://python-future.org/ python-future] to run futurize stage 1 to update legacy (pre 2.6) code ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized unicode-futurized])
*** Updates print to functions 'from __future__ import print_function'
*** Updates exception calls to use 'as'
*** removes most usages of 'long' (mostly used unnecessarily)
**** Only needed for 32-bit support
*** Fixes relative imports (from __future__ import absolute_import)
** Fixing code that is deprecated in Qt 4.8 and removed in Qt 5 ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized-qt5 unicode-futurized-qt5])
*** Updated all signals to new-style
* If we go 2 to 3, this could break packages
** means we should schedule any package format changes for the same time
** e.g., imports should be unrelated to code path (function to load module from package identifier?) (take them out of vistrails.* [https://github.com/VisTrails/VisTrails/pull/1002 #1002])
** any structural changes (e.g. the __init__ versus init thing) (RR thinks it makes sense, though having both named "init" is unfortunate)
** putting package identifier as xml?
*** Python not so bad, plus some stuff in there is Python code (checking dependencies)
** version the APIs?
*** RR planning on versioning vistrails_module.Module, no point versioning the whole package?
* file formats on 2 to 3:
** no real translation/upgrade, but non-ascii values that work on 3 won't load in 2

=== January 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://gist.github.com/rexissimus/dfd27e466427529c385c Porting to Python 3 / PyQt5]
** Basic GUI and execution works
** Minimal work to support 2to3
** Hard to support both PyQt4 and PyQt5

=== January 6, 2016 ===
'''Updates'''
'''Items to Discuss'''
* Updating VisTrails dependencies
** Successfully built [https://gist.github.com/rexissimus/f1a1aada7de1c00a57c7 Win7-64/Python3/PyQt5/Qt5/WebEngine/VTK7]
*** VTK 7 is the first supporting Python 3 but is only in release candidate phase.
**** Next version of VTK 6 is rumored to support Python 3
**** There is a development branch of VTK 6 supporting Python 3
*** Can travis build this?
**** We can skip tests for WebEngine and VTK if needed
** Python 3 [https://python3wos.appspot.com/ showstoppers]
*** No MySQL-python (sqlalchemy supports mysql through other drivers)
*** No suds (there are active forks but we could also drop support?)
* Options for python2/3 support:
** Interpreter could be python2/python3 based on packages
** six layer works but not the easiest to maintain (e.g. in reprozip)
* Drop support for win-64
* Update copyright headers to 2016

== 2015 ==

=== December 30, 2015 ===
'''Updates'''
* Bokeh package finished
** Can output to Browser/IPython/Spreadsheet (Limited functionality in spreadsheet)
'''Items to Discuss'''
* Updating VisTrails dependencies
** Bokeh needs QWebEngine (Chromium) in Qt5 which requires PyQt5
*** Many plotting libraries only work in browsers
*** But Chromium may be a big and controversial dependency
*** Or create a browser version of the spreadsheet?
** Some users have requested Python 3
** Not backwards compatible?
** Target for VisTrails 3.0 with new interpreter?

=== December 16, 2015 ===
'''Updates'''
'''Items to Discuss'''
* Users list question
* [TE] Wrapping Bokeh
** Added bokeh property parser
*** complements numpydoc parser
*** Not all attributes are available, partially because I am using a pre-release version.
** Wrapped modules
*** bokeh.plotting finished (Backwards like matplotlib: Create plot then draw on it)
*** bokeh.charts mostly done (Missing arguments)
** QWebView mostly works (but no zooming or buttons)
*** It would be better to use external browser or QWebEngineView
** Added improvements to wrapper
*** Generalized port translations (Color/Path to native types)
*** Can use multiple docstring/property parsers simultaneously

=== December 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Looking into wrapper
** Will port TensorFlow
** Doing a pass on the wrapper code & doc
*** UX improvements
** Factorize high-level docstring parsers into core.wrapper? (sphinx, numpy, google)
** Problem with name vs module_name (fails sklearn tests because class_by_name() is broken)
** Looking into compressing specs, lazy registration of modules

=== December 2, 2015 ===
'''Updates'''
* [TE] Package wrapping
** Wrapped most of numpy/scipy using __all__
** Added class attribute and method access for classes (Can add to class or to separate inspector module)
** TODO: Document wrapping procedure

'''Items to Discuss'''

=== November 25, 2015 ===
'''Updates'''
* [RR] New interpreter is coming along
** Everything is a stream
** Task system, eventually work-stealing parallelism
** Streams no longer advance in lock-step
*** Allows for constructions like filter, join, sorted-merge
** depth>1 still to be tested, no current plan to allow this through the module interface
*** Through looping though, can do streams of streams

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapped most numpy functions (no polynomials)
** and half of scipy classes and functions
** Added functions manually from documentation (no parseable lists?)
** Focusing on data flow constructs (no property/method access for classes)
*** Using spec diff (empty for now) and dynamic parser (stores spec in .vistrails/)
** Python class/function wrapper now stable
** Add google doc parser?
*** Is there a parser available?

=== November 18, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Numpy class wrapping works
*** Basic type is List, since most types are array_likes.
*** TODO: More classes and functions
*** Some operations are in-place and some aren't, and docstring not super clear
*** [RR] It seems only methods mutate, and most have a numpy.xx function equivalent; just manually go through the methods and remove the mutating ones?
** Class wrapper is modular
*** Docstring parser and type string parser can be customized
*** Classes can have optional attribute/method ports
**** Inspectors and attribute/method modules can be created separately
** Use PythonCalc as an example
*** Can be re-implemented as a function with a parseable docstring
*** [RR] PythonCalc is just an example, and it might actually make sense to get rid of it, or do a proper math package with scalar operations (as separate modules, no combobox)
** [RR] TensorFlow to use wrapping as well
*** Very simple (only types 'tensor' & 'variable')

=== November 11, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapping numpy's classes using numpydoc (ndarray)
*** Wrapping constructor arguments, attribute getters/setters as module ports
**** Then how to access attributes afterwards?
***** Use input value port to class modules?
*** Wrap methods as modules? E.g., `ndarray.shape`.
*** Function wrapping is almost a subset of class wrapping
**** May be able to use the same parsing/execution methods
** VTK's non-getter/setter methods could be wrapped as modules
*** We could then remove extra logic in interpreter for keeping function order
** Bokeh uses autogenerated docstrings
*** We may be able to read the specification directly

* [RR] [https://github.com/VisTrails/VisTrails/pull/1138 TensorFlow package]
** Basic setup working, can execute the Mandelbrot example
** Will autogenerate the operations

=== November 4, 2015 ===
'''Updates'''
* [RR] Interpreter work requires a fix for [https://github.com/VisTrails/VisTrails/issues/1137 DB issue #1137]
* [DK] Kitware's Resonant [http://www.kitware.com/source/home/post/173]
** [https://github.com/girder/girder Girder]: data management system
** [https://github.com/Kitware/romanesco Romanesco]: execution engine, uses [http://www.celeryproject.org/ Celery] for task management
** Resonant Flow: web app for editing and executing workflows

'''Items to Discuss'''
* [TE] Added OSX Lion (10.7) VM on build machine using vagrant (seems ok with license?)
** New builds works on Lion
** Change the minimum requirement to 10.7?
* [TE] Package wrapping
* Added upgrade suggestions using 2 spec versions ([http://pastebin.com/30XUU8Gp example])
** using name edit distance to find matches
** Could use something better like port similarity for modules, and type similarity for ports
** Should write python upgrade code?
** Added spec to sklearn package
*** Can now diff spec versions and keep the spec static
*** There will be problems with downgrades and package versions

=== October 29, 2015 ===
'''Updates'''
* [TE] nightly-build-mac fixed (Needed to approve xcode license)

'''Items to Discuss'''
* [TE] matplotlib wrapper
** ported to general spec
** Diff can be used on general spec
*** Only needed minor changes
*** Fixed indexing bug that corrupted specs
*** Can now move diff tools to core/wrapper
** Add new plots?
*** New plots in mpl 1.3: eventplot
*** New plots in mpl 1.4: angle_spectrum, magnitude_spectrum, phase_spectrum', violinplot
*** No new plots in mpl 1.5 (from looking at boilerplate.py)

=== October 21, 2015 ===
'''Updates'''
* [RR] Alexis has arrived, will be working with [RR] on a more efficient interpreter

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package]
** Supporting multiple package versions
*** Check which version can be loaded [https://github.com/VisTrails/VisTrails/pull/1135 #1135]
*** We cannot show version requirements in the list of packages because old packages are loaded when importing the codepath
** Visual diff does not work well, but we can use the spec differ to see differences.
** Unifying vtk and matplotlib wrapping specs (WIP)
*** And porting matplotlibs spec differ to work on the general spec
*** Spec differ can then be used on vtk and other packages in the future
*** Will enable automatic upgrade generation
* [RR] Rework interpreter
** restore abstraction between interpreter/module code
** build looping, streaming, caching into the interpreter
** rework cache
** look into parallelism once basic functionality is there

=== October 14, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package] (adding numpydoc parser)

=== October 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/tree/fix-matplotlib-parser New matplotlib parser] (adding numpydoc parser)
** Added numpydoc attribute parser for plots.
*** TODO: Need better port spec reconciliation with call signature parser.
*** We can create a general numpydoc parser, but attribute types are unique to matplotlib.
** Needs package versioning
*** New spec will not support matplotlib < v1.4 due to changed path to axes classes.
*** Load spec version corresponding to installed matplotlib version?
*** Need version downgrades?

=== September 30, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Updating Matplotlib parser
** Matplotlib docstring parser fails on numpy docstrings
** I have [https://github.com/VisTrails/VisTrails/commit/eae8b0c16260810587e47c41cab53552cbb3cf0a added basic numpydoc parsing]
*** Only used by a few docstrings so far
*** Parsing uses many sources (class tables, signatures, ACCEPTS, method docstrings, definition parsing).
** Caswell said they were thinking about moving to traitlets, but this is not ready yet

=== September 23, 2015 ===
'''Updates'''
* [TE] VisTrails 2.2.3 released
** Also have pushed to PyPI, binstar, etc.
** Sourceforge vs. GitHub
*** should be able to host releases on GitHub
*** nightly binaries pushed to sf each night
*** old binaries?
* [TE] Re-wrapping MatPlotlib
** Keep static generation - Docstrings are brittle beween matplotlib versions
** Keep generating the executable classes - but create functions, not vistrails Modules
*** Why is there so much patching?
** Re-implemented Alternate PortSpec for InputPortSpec
*** It will now inherit specs from parent (No need to reimplement)
** Module upgrades?

'''Items to Discuss'''

=== September 16, 2015 ===
'''Updates'''
* [TE] Job Monitor tests and documentation done
** OK to leave document package in packages directory?

'''Items to Discuss'''
* [TE] Library wrapping: How to do code patching? [https://docs.google.com/drawings/d/1Sh3eOXot6v2y880jHKQrqXqAwr-0aoqYligg3z8G8MY/edit?usp=sharing Wrapping diagram]
** Insert code into module template (Old VTK code)
** Patch the library that is called (New VTK code)
** Somehow store code in spec and apply when executed?
*** Executed code needs at a minimum access to inputs, outputs, current class
*** Use standard input/output dict and obj reference that the code operates on?
*** Can this be done while keeping the execution abstract?

* Do new release now?

=== September 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* New release?
** [RR] wants reprounzip
** tej changes & doc
** job monitor & jobmixin fixes
** mongodb
** reprounzip
** warning: MplFigure type is int
** tabledata: add Reshape, DictoToTable & ListToTable, fix ListToTable with numpy arrays
** PythonSource can have same name for an input & output
** don't show spreadsheet at exit

=== September 2, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Limit autosaves? [https://github.com/VisTrails/VisTrails/pull/1126 #1126]

=== August 26, 2015 ===
'''Updates'''
* [TE] Added Job support to Parameter Explorations (Requested by Colin), and Mashups
** specify job ids, need to specify different ids for parameter explorations since they have the same version id
** how to deal with parameters passed in on command line
* [General] provenance: should be creating a new version when we execute workflow with changed parameters?
** currently, custom_params annotation stores this in provenance currently
** [RR] API doesn't record provenance if passing in parameters: http://git.io/vsAA5
'''Items to Discuss'''

=== August 19, 2015 ===
'''Updates'''
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [TE] Working on Job Monitor documentation

'''Items to Discuss'''
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [TE] Stop testing VisTrails 2.0?

=== August 12, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Build broken on Travis; because of IPython 4 released today? ([https://travis-ci.org/VisTrails/VisTrails/builds/75279795 build 992]; [https://github.com/VisTrails/VisTrails/issues/1123 #1123])

=== August 5, 2015 ===
'''Updates'''
* [TE] Fixes to Jobs
** Could not delete jobs
** Could not run job in group
** Job not reset when calling ModuleSuspended
** Added deleting job from context menu
* [RR] Writing documentation for everything [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

'''Items to Discuss'''

=== July 29, 2015 ===
'''Updates'''
* RR still looking into new interpreter thing
** Goal is to take out scheduling logic from Module so it can be split in multiple processes, and so that smarter strategies can be added in time
** This means some work on packages
** Spreadsheet can live in kernel process? Still some UI stuff that will take work (changing configuration, persistent archive's viewer, ...)
* [TE] Problems running examples [https://github.com/VisTrails/VisTrails/pull/1111 #1111]
** Testing of more examples requires additional packages on the test machines.
** Fixed faulty line-ending in PythonSource:s failing on Python 2.6.
** Test suite now testing SUDSWebServices (If web service is down, test suite will fail)
** preferences.py test failed reloading 'dialogs' package, switched to using 'URL'.

'''Items to Discuss'''

=== July 22, 2015 ===
'''Updates'''
* [TE] mailing lists back online
* [TE] Working on [https://github.com/VisTrails/VisTrails/issues/1107 #1107]
* [RR] Working on ReproZip package

'''Items to Discuss'''
* [RR] MongoDB package [https://github.com/VisTrails/VisTrails/pull/1106 #1106]
* [RR] Example for tej docs? [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

=== July 15, 2015 ===
'''Updates'''
* 2.2.2 released

'''Items to Discuss'''
* RR is considering executing everything in an IPython kernel (i.e. separate Python interpreter, like the one spawned for a notebook)
** It's a separate process that we can restart without restarting the app/gui
** We can isolate the execution environment (e.g. for the server)
** We can run the whole thing remotely (if your data is elsewhere, just run VisTrails locally and the pipeline elsewhere)
** Pipeline execution no longer makes the interface hang, it just makes the kernel hang (but that's fine)
** We can use notebooks as modules (probably way nicer than the PythonSource module)
** We can run multiple kernels so long as the ports carry things that are serializable
*** meaning we can put the multithreaded-interpreter without all the hacky parts it has now
*** we can run IPython kernels in all the languages IPython supports, [https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages currently 46]

=== July 8, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Buildbot github hook not working after IP address change
* [TE] No reference to VistrailsApplication ([https://github.com/VisTrails/VisTrails/issues/1103 #1103])
** [RR] Added PR [https://github.com/VisTrails/VisTrails/pull/1104 #1104]
* [TE] Reopening VT file after saving with bundled subworkflow won't offer subworkflow upgrade ([https://github.com/VisTrails/VisTrails/issues/1102 #1102])
** allow manual delete to fix right now
** fix this on top of the use-uuid branch
* [TE] Release VisTrails 2.2.1? ([https://github.com/VisTrails/VisTrails/blob/v2.2/CHANGELOG CHANGELOG])
** [https://github.com/VisTrails/VisTrails/pull/1093 output-modules-use-global-dir]
** [https://github.com/VisTrails/VisTrails/milestones/version%202.2 Current issues for 2.2]

=== July 1, 2015 ===
'''Updates'''
* [TE] PROV fixed
* [TE] Working on subworkflow issues
* [RR] Considering reworking the controller (log vs exception problem, retained upgrades causing interferences) and also the interpreter (IPython?)

'''Items to Discuss'''

=== June 24, 2015 ===
'''Updates'''

'''Items to Discuss'''
* UV-CDAT
* [TE] Can a cyclic workflow be valid? ([https://github.com/VisTrails/VisTrails/issues/1097 #1097])
** focus on disabling the ability to create cyclic pipelines because more things break than just this with a cyclic pipeline
* [RR] Relative paths ([https://github.com/VisTrails/VisTrails/pull/1057 #1057])
** This interacts with the new bundle; how do handle packing files inside the VT bundle?

=== June 17, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] current_version and reusing existing upgrades are broken ([https://github.com/VisTrails/VisTrails/issues/1095 ticket #1095])
** Could be that export to PROV is using an unflushed upgrade pipeline?
** current_version would then be correct.
** It may work to flush the actions before exporting?

=== June 10, 2015 ===
'''Updates'''
* DAT: fixed VTK issue on Linux and Mac
* Still crashes on Windows. Need help! Reminder: this works in the VisTrails spreadsheet (QCellPresenter), although no widget get changed there during a drag
** Is it a VTK bug?
** Is it simply impossible to change widgets during the drag, should we do it a different way?
** Did I miss something that is done in VisTrails but somehow not in DAT?
** Low prio, UV-CDAT doesn't run on Windows anyway

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 Updated pull request])
* Single instance code and batch mode

=== June 3, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 pr])
** Requires fixes to command line parameters, Output modules, and batch mode
** How to test this
** Updated missing/outdated flags
** Fixed view issues when generating graphs
* [TE] batch mode
** SpreadsheetOutput not enabled in batch mode. Should we check is_running_gui instead?
** Other instance setting flags from caller
** Is graphsAsPdf replacing spreadsheetDumpPdf?
** graphsAsPdf true by Default?
** Batch mode executing by default (Not needed when generating graphs)
** Re-added workflowInfo as withWorkflowInfo for writing graph and xml workflow
** [DK] batch mode should be outputting to files or stdout, shouldn't always trigger SpreadsheetMode
** execute flag, maybe make execution the default and allow a "--no-execute" if you only want to capture graphs, for example

=== May 27, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] API question
** http://lists.vistrails.org/pipermail/vistrails-users/2015-May/000357.html
* Status of DAT
** Can add VCS plot to DAT but need to work on configuration windows
** Documentation for graphics templates for UV-CDAT/vcs?
* Qt support?

=== May 20, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Reviving the DAT, integrating scripting & porting UV-CDAT!
** On [https://github.com/VisTrails/DAT GitHub] ([https://github.com/VisTrails/DAT/issues issues])
** Merging 2 years of development taking longer than expected, but getting there. The plan is to get the patches in VisTrails and never fork again, we never want to get in UV-CDAT's situation (and don't need to).
** VTK cell works fine on Linux but there was flickering on Mac & Windows before; still issues on Mac (Windows status unknown)
** Can get a VCS plot soon (but will need VTK cell fix)
** Integrate in UV-CDAT's build system (so we have cdms, VCS, ...) -> RR can do this, low priority
** How do we integrate scripting?
*** We want to be able to seamlessly make changes to a plot by changing Python code
*** Define new plots by entering Python code without writing modules/packages?
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 13, 2015 ===
'''Updates'''
* [RR] Test skipping whitelist ([https://github.com/VisTrails/VisTrails/pull/1069 #1069]) -- low priority
* [RR] Custom matplotlib modules can't be compatible with both 2.1 and 2.2 ([https://github.com/VisTrails/VisTrails/issues/1067 #1067]); should be fixed for ALPS ([https://github.com/VisTrails/VisTrails/issues/1070 #1070])

'''Items to Discuss'''
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 7, 2015 ===
'''Updates'''
* [RR] Export/import workflow to Python working!

'''Items to Discuss'''
* [Claudio] UV-CDAT
** The UV-CDAT project is the biggest user base of VisTrails
** VisTrails package management provides a lot of friction towards people plugging in their code
** Need to make it easy to integrate your random Python scripts in the system without having to deal with all the boilerplate, at least in the first step
** [RR] argues that modules are still good; UV-CDAT shouldn't move towards a purely script-based backend
** [RR] export/import with Python could reduce a lot of that friction by allowing 1) to edit workflow as Python 2) to open up boxes automatically if needed code doesn't match actual modules
** ...

=== April 29, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] <strike>Abstractions</strike> subworkflows status ([https://github.com/VisTrails/VisTrails/labels/subworkflows tickets])
* [RR] matplotlib compatibility (2.1 & 2.2), [https://github.com/VisTrails/VisTrails/issues/1067 #1067]
** RR to try and fix ALPS matplotlib modules

=== April 22, 2015 ===
'''Updates'''
* 2.2.0 has been released!
* Windows issue (via email from Ryan)
** issue with manifest file (may be a new file in VTK6?)
** Tommy has regenerated new Windows builds
* Binaries, pypi, and conda released
* [RR] Export as script
* Python sources using VTK need to switch to SetInputData (users should be aware of this)

=== April 15, 2015 ===
'''Updates'''
* Ready for 2.2.0 (apart from binary/deps issues)
** Missing some libs (scikit-learn, tej, tdparser, SQLAlchemy+connectors
** Windows: runvistrails.py is no longer used, so the PATH is wrong
** Windows: pip is broken, but it probably wouldn't work anyway because of permission issues (disable this?)
* Queries, upgrades and getPipeline() usage ([https://github.com/VisTrails/VisTrails/issues/1054 #1054])
** Getting a pipeline with getPipeline() is not safe: it might return an invalid pipeline
** This is used in many places throughout the code, like queries
** Upgrading would require going through the controller, but that creates new actions
* [TC] Avoid copying a module's output if it's used as input by exactly one downstream module ([https://github.com/VisTrails/VisTrails/issues/1060 #1060]) (useful for big numpy arrays you can update in-place)

=== April 8, 2015 ===
'''Updates'''
* [DK] Merged RR's changes for output modules (1012 and 1013)
** RR will merge remaining changes, then create v2.2 branch!

'''Items to Discuss'''
* BNL need numpy array to VTK image
** Looks like VTK has some helpers for this
** We will help if issues arise
** Will contribute back to VisTrails package
* Upgrade issue: [https://github.com/VisTrails/VisTrails/issues/1017 #1017]
** Automatic upgrades should happen between versions of provided upgrades
** Our existing upgrades work around this so it doesn't need to be 2.2.0
* Corner-case VTK modules
** No longer need VTKCell input port, so don't interfere with registry and API anymore
** Still work weirdly, people probably shouldn't use them
** But we have lots of clunky modules since we wrap the whole of VTK; some people might rely on this and know how to use them, let's keep them anyway
** Ready for 2.2.0

=== April 1, 2015 ===
'''Updates'''
* [RR] UV-CDAT: bugfixing for 2.2, long-term plans: implement scripting import/export in VisTrails, port to UV-CDAT
* Possibly, try to move to regular VisTrails to use new features

'''Items to Discuss'''
* 2.2 release: nothing much is pending anymore, release next week?
** [TE] vtkExporter classes [https://github.com/VisTrails/VisTrails/issues/1032 #1032]
** [RR] Hiding upgrades in version tree might make it (or might be 2.2.1 so we can test it out) [https://github.com/VisTrails/VisTrails/issues/949 #949]
** Output modules changes to go in
* add note to documentation about order of parameters in VTK
* add issue about exporter upgrades if not already there

=== March 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* 2.2 release
** Checklist on Github: https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist
** Review output modules
** RR has a couple more issues to fix
** Ready to go -- sign app package for OSX? [https://github.com/VisTrails/VisTrails/issues/984 #984] We need access to the Apple Membership team

=== March 18, 2015 ===
'''Updates'''
* [TE] VTK6 works

'''Items to Discuss'''
* [RR] Release v2.1.5 with backported tabledata?
** MTA example needs updated tabledata (for JoinTables)
** Google Maps package still not available
* [RR] Work torward v2.2.0?
** changes:
*** new persistence
*** API changes
*** output module changes (upgrades?), maintain cells but try to upgrade
*** not wrapping stuff
*** VTK6? yes
*** JobSubmission stuff?
*** relabeling for upgrades [https://github.com/VisTrails/VisTrails/issues/949 #949]
** makes sense, needs the tree view code to be updated, check selection
** See [https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist 2.2 checklist]
* Discussion of [https://github.com/VisTrails/VisTrails/issues/1016 #1016]
** plumbing between outputs and output modes, how to define a mode that works for many outputs without writing for each output?

=== March 11, 2015 ===
'''Updates'''
* [RR] persistent_archive done; merge? ([https://github.com/VisTrails/VisTrails/pull/755 #755])
** note about the focus events for widgets
** TE be aware of file_archive for future binaries that include persistent_archive
* [TE] [https://github.com/VisTrails/VisTrails/pull/998 New VTK package] finished

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails? (see last week; decision needed)
** RR email to JF about this
** yes; email sent to Github
* [RR] Switching order of output ports ([https://github.com/VisTrails/VisTrails/pull/1006 #1006])
** added port specs are sorted at a separate spot (Module.*_port_specs properties) than those in the registry (which are sorted in the registry), but those two lists are just combined without respect to sort keys
** need to determine whether the two lists should be merged or remain distinct
** should make sure that order of input ports and output ports makes parallel connections for things with same order
** DK suggests breaking backward compatibility here: workflows still run, can fix easily if a problem in an existing package.
* [RR] Question about output modes ([https://github.com/VisTrails/VisTrails/pull/1007 #1007]), how to integrate in API ([https://github.com/VisTrails/VisTrails/pull/24 #24])
** Should ImageFileMode be removed? ("image" is not a mode, "file" is)
** ImageOutput missing?
** Feel free to change how formats works
* [TE] Test suite segfaults on Fedora 17 virtualbox. Install newer version? (Support ended in 2013)

=== March 4, 2015 ===
'''Updates'''
* [TE] VTK wrapper
** Works on VTK 5.10
** Still need to test VTK 6
** New general wrappers for python functions and classes

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails?
** When [http://i.imgur.com/UTY2qfg.png filing a pull request] from UV-CDAT/VisTrails, VisTrails/VisTrails is selected by default
** People keep forgetting to change the default ([https://github.com/VisTrails/VisTrails/pull/956 #956] [https://github.com/VisTrails/VisTrails/pull/968 #968] [https://github.com/VisTrails/VisTrails/pull/999 #999] [https://github.com/VisTrails/VisTrails/pull/1000 #1000] [https://github.com/VisTrails/VisTrails/pull/1003 #1003] [https://github.com/VisTrails/VisTrails/pull/1004 #1004] [https://github.com/VisTrails/VisTrails/pull/1005 #1005])
** Only way to change that is to not have it marked as a fork of VisTrails/VisTrails
** Github staff [https://gist.github.com/remram44/b364c24ef1e462ce6e2f can make that change for us]; should we do it?
** Juliana: comments on this? visibility vs. convenience/annoyance for developers
* [RR] What about [https://github.com/VisTrails/VisTrails/issues/991 #991]?

=== February 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] vtkviewcell for infovis support, can we unify with VTKCell?
** need to test this
* [TE] vtk wrapping
** Mostly finished
** VTK 5.10 produce incorrect results with old wrapping
*** Old wrapper is based mostly on VTK 4
*** Most vtk_examples affected
*** [http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Replacement_of_SetInput]
*** should be able to upgrade from SetInput to SetInputData (need to drop GetOutput and replace with self ports)
*** can we change vtkInstance to just return self and not wrap things
** terminator example not working under 5.8?
* How does VTK wrapping fit into general wrapping framework?
* [RR] new persistence package

=== February 18, 2015 ===
'''Updates'''
* [RR] New VisTrails API and IPython integration ([https://github.com/VisTrails/VisTrails/pull/24 #24])

'''Items to Discuss'''
* [TE] VTK wrapping
** [https://gist.github.com/rexissimus/16b74693545b5e7c1035 Benchmarking vtk package]
*** Old: 24.7 seconds
*** New: 10.5 seconds (Except first time that adds 8 sec)
**** The parsing that calls is_abstract (that tries to instanciate all vtk classes) is now only run the first time.
**** get_items_from_sigstring takes 2 seconds, maybe we can use a lookup dict for already computed sigstrings?
** Now using a general python function wrapper
*** VTK classes are wrapped into python function that does not depend on vistrails
*** VTK functions can be executed without vistrails
*** The spec maps functions into vistrails modules, but can also describe wrapping
*** A general python function wrapper that supports
**** kwarg inputs
**** single, list, dict outputs
**** callback for progress reporting
**** temporary file generator for using FilePool
**** optional output generation
*** Creating specs:
***** Create spec by hand
***** Auto-create spec outline (TODO) and manually finish it
***** Dynamically create spec (VTK)
***** Implement documentation wrappers (Can use scikitlearn wrapper to wrap numpydoc) (TODO)
***** Classes as bad functions needs to be wrapped in new functions before they are wrapped. This is different for each package.
****** Classes is hard: Like VTK, and matplotlib. Scikit-learn does still not wrap classes
***** Spec diffing and patching could be done using code from matplotlib.
** Still needs upgrades from old VTK package
*** Is it possible to dynamically wrap functions, e.g, you see a SetFunc and just remove the 'Set' prefix. Or do you need to create a complete mapping?

=== February 11, 2015 ===
'''Updates'''
* Update from Friday's meeting
** discussed VisTrails internals
** discussed wrapping
*** xml discussion, hard to modify because tied to db code
*** TE has made it possible to add the schema-defined attributes to the intermediate representation
*** higher-level operations on the port specs
** make sure the simple case works
*** [JF] take a simple package with documentation and figure out what the base case for wrapping is

'''Items to Discuss'''
* [TE] VTK wrapping
** Dynamic loading works
** Reading XML is fast enough, but [https://gist.github.com/rexissimus/8272d3c776ccfa115d82 unserializing data is slow]
** Working on patterns for patching
** Matplotlib has many advanced patterns like argument ordering, nested arguments, alternateSpecs, output types.
*** Having all this in a general wrapper might confuse users?
** [RR] Delay module (except for identifiers) until you need it---e.g. don't deal with port specs, etc. until necessary
* Scripting Support [https://github.com/VisTrails/VisTrails/pull/950 #950]
** [RR] Issue with getting code from modules
** Design a simple solution
** [JF] Couldn't you use modules as black boxes without conversion, just to call into modules/subworkflows easily from e.g. IPython?
*** [RR] This is a job for the API, and a very separate use case. See [https://github.com/VisTrails/VisTrails/pull/24 #24]

=== February 4, 2015 ===
'''Updates'''

'''Items to Discuss'''
* Wrapping
** Format to use? Currently XML (like current matplotlib)
*** JSON and YAML have simple "to python dictionary" methods
*** But don't stream
*** YAML a lot easier for humans
** [DK] vtk-new-package also changes parameter names, creates enumerations
*** intermediate schema needs to be extensible
*** packages will want to store there specific infos for compute() method generation
*** also might have specs-altering info, like matplotlib's alternateSpec
** representation to code , registry already has schema for some aspects
** [RR] We might want to see if Module subclasses can be created lazily
*** no need to create all the classes just to register them in the registry and never actually use most of them
*** future effort
* [RR] Where should VisTrails packages live?
** tej installs as 'vistrailspkg.tej', TE installed it as 'userpackages.tej'
** Currently, standard packages are 'vistrails.packages.', user packages are 'userpackages.' and packages loaded through pkg_resources might be anything
** [RR] Use 'vistrailspkg.' everywhere?
** Long-term effort to simplify package distribution/installation (and have VisTrails get them automatically?)

=== January 28, 2015 ===
'''Updates'''
* T. Caswell to come visit on Fri 6 to discuss wrapping work

'''Items to Discuss'''
* [TE] New VTK wrapping
** Current code by DK seems a good deal faster
** Generates XML that can be patched/tweaked, generates Python code from it, VisTrails only loads generated Python code
** RR would rather have VisTrails load intermediate representation (= XML) directly, wants to make sure this is not slower
** The goal is to turn the intermediate step into something generic that would be used for every wrapped package (vtk, numpy, matplotlib, sklearn, java) instead of each having its own
** TC has its own code at [https://github.com/Nikea/VTTools/blob/master/vttools/wrap_lib.py github:VTTools] which parses numpy docstrings and generates modules, doesn't yet handle classes or persist anything
* Web crawler
** Right now, TE starts jobs for "start crawler", "stop crawler", "install classifier"
** RR would rather have the crawling be a job as far as VisTrails and tej are concerned
** The whole thing would be one pipeline: load examples, train classifier, start crawler [check for job, kill previous one, upload model, start processes], get snapshot, visualize
*** Need some support in tej and job submission system: long-running jobs, stop a job (wait for it to finish?), restart a job even though results are cached

=== January 21, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Unified wrapping method discussion [https://github.com/VisTrails/VisTrails/issues/991 #991]
** TE to work on reusable method with intermediate representation, starting with VTK
* [RR] Examples for scikit-learn: JF has an old example using Weka with parameter exploration (not currently in source tree)
** AM's examples are enough
* [AM] scikit-learn package is done, merge it in? [https://github.com/VisTrails/VisTrails/pull/955#issuecomment-70286788 #955]
** RR will merge
* [RR] What should copyright headers say? [https://github.com/VisTrails/VisTrails/pull/994#issuecomment-70173935 #994]
** Let's keep everything in there: Utah/Poly/NYU

=== January 14, 2015 ===
'''Updates'''
* [TE] Working on classifier
* [RR] Scripting integration, work in progress

'''Items to Discuss'''
* [RR] Unified wrapping method discussion ([https://github.com/VisTrails/VisTrails/issues/991 #991])
** Let's talk next week, [AM] and [DK] are not here

=== January 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* make sure that we address critical issues, questions, and pending review branches in a timely manner
* scripting support
** [RR] no issues if we want to just keep annotations in the generated code to allow the link back to a workflow
** [RR] can translate from workflow to script, working on script to workflow
** will work for parameter value changes, structural changes require changes to the annotations
** need to publish best practices here
** would be cool to do looping in scripts (easier interface than with workflows)
* notebook support (convert form notebook to workflow)
** RR will sync with FC on this
* Issue with console in built-from-scratch
** [TC] iPython rearranged some of the completion stuff in 2.2 and 2.3
** binary has old version of iPython -> 1.0.0, should we update?
* [TC] automated wrapping of numpy and scipy
** discovered a bunch of malformed documentation in numpy and scipy
** has github repo for vistrails tools
** example modules wrap a bunch of R stuff (not baked in, just how things are)
** will be pushing wrapping logic up
** port names forbidden (window and domain)
** have an import hook to get from yaml directly to VisTrails Modules
** should work for any python modules with well-formed numpy docstrings.
* [Action] should make it clear in documentation that Constant now means serializable not that the value doesn't change (e.g. List)
* [TC] might be interesting to try to build components of matplotlib and accumulate in figure (long-term project, but thinking about how this might work)
* [TE] build and build scripts
** completely automatic, buildbot
** need to set the build machines for the environment we want for the binary
** would virtualenv work here?
** [TC] anaconda can pin versions, potential path to test different configurations
** Q: upload nightly binary builds? A: makes sense, make sure they are well-labeled
* sourceforge stats: e.g. http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07
* package issues (see Remi's message)
* [TE] Scope of tej
** Support single ssh commands?
** Queue can be used as a remote machine (crawler is using queue.call*)
* SourceForge stats: http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07

== Older meetings ==
* [[Development/2014]]
* [[Development/2013]]
* [[Development/2012]]
* [[Development/2011]]
* [[Development/2010]]

Development

2016-05-04T14:57:24Z

Tommy: /* April 27, 2016 */

<div class="nonumtoc toclimit-1">
__TOC__
</div>

See also the [https://github.com/VisTrails/VisTrails/wiki/Development Github wiki]

== 2016 ==

=== May 4, 2016 ===
'''Updates'''
* VisTrails 2.2.4 released

'''Items to Discuss'''
* [TE] Union type [https://github.com/VisTrails/VisTrails/issues/1172 #1172]

=== April 27, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Wrapping Bokeh
** New method type "operation"
*** Transforms Figure->Glyph->Output into Glyph->Figure->Output
**** Glyph sets function name and arguments as output
***** Not serializable, but should always be computed together with the subject of the operation.
**** Figure applies Glyph operation on itself
*** Useful for matplotlib?
**** matplotlib currently find actors by searching upstream?
**** But this is more difficult since matplotlib is not function-based.
** New "union" port type
*** Turns "x(float), x(list)" into "x (float, list)" and uses first set value
**** Uses only first value in tuple
**** Bokeh have many properties that support (list, string, Float)
*** Does not work with depth=1 types (e.g. Float of depth 1)
**** Turn Depth 1 types with known type into lists?

* [TE] New bugfix release
** Finalize survey

=== April 20, 2016 ===
'''Updates'''
* Merged upgrade fixes
** Now has infinite loop test
** loop test now correctly loops 5 times
*** remap_module used wrong (current) package version when creating ModuleDescriptor
* Fixed multi-step group upgrades (PR: [https://github.com/VisTrails/VisTrails/issues/1168 #1168])

'''Items to Discuss'''
* New bugfix release
** Merge usagestats
** Need to finalize survey

=== April 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Chaining upgrades done ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Replace "Upgrade" description annotation with "upgraded_from" annotation to identify which tags to hide?

* [TE] Iterating handle_invalid_pipeline ([https://github.com/VisTrails/VisTrails/pull/1165 #1165])
** Not based on [https://github.com/VisTrails/VisTrails/tree/chain-upgrades-loop chain-upgrades-loop]
** Cherry-pick test to preserve source?
** Need maxPipelineFixAttempts option?
*** The code is now smarter about recursion, so max attempts will "probably" never be reached.
** Need [https://github.com/VisTrails/VisTrails/commit/0ef0667426937eddb1d1c1e397f0657ffec039a9 debug messages]?
*** Would need to be moved into handle_invalid_pipeline

=== April 6, 2016 ===
'''Updates'''
* [TE] Query View improvements
** Done except for displaying "Version Info" and #1164
* [RR] Working on finishing new interpreter (finally!)

'''Items to Discuss'''
* [TE] Chaining upgrades ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Try latest upgrade first, then previous.
** If all fail, select latest upgrade?

=== March 30, 2016 ===
'''Updates'''

'''Items to Discuss'''

* [TE] Query View improvements
** Unified do_version_switch and get_upgrades as validate_version()
** Problems with query view using its own controller
*** Fixed module info not being displayed for query results
*** Still no version info for query results
*** Still an issue with version query view not being updated

=== March 23, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Usage reporting almost ready to go
** Need to record whether specific features are used: paramexpore, mashup, query
*** [DK] Record if LaTeX extension is used? But hard to distinguish from direct batch invocation
** How to record size of vistrail?
*** [DK] IdScope already walks over vistrail, use that
*** but total number of modules and versions doesn't give an idea of average size of individual pipelines

=== March 16, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Upgrades in Query Mode
** Now using code similar to do_version_switch
*** Uses handle_invalid_pipeline
*** Differences: Not using current_pipeline, flushes changes
*** New controller method get_pipeline optimized using cached pipelines (but not current_pipeline)
*** Integrate to avoid repeated code?
*** Use this for query mode?
* [TE] VisTrails 2.2.4 ready for release?
** tej package updated. Others?
* [JF] upgrades and the version tree
* [JF] provenance in Jupyter
* [DK] bundles: [https://github.com/VisTrails/VisTrails/pull/1092 #1092]

=== March 9, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixing search mode
** String query now matches all by default
*** This caused pipeline queries to never match
** String query can search: User/Notes/Tagname/Time/Module name
*** Should we search module names by default? (Disabled by default because it is expensive)
*** Fixed notes search
** '>' parameter queries in documentation but has been removed
** Fixed module matches for upgraded pipelines (By not upgrading pipeline)
*** Upgrades still a problem
*** Add "Upgrade all menu option?" (Or upgrade all on open when `hideUpgrades`)
*** [JF] Allow search on past tags

* [TE] Create new bugfix release
** Finish querying
** Path issue on windows

* [DK] Look into sqlalchemy and new bundle branches

=== March 2, 2016 ===
'''Updates'''
* [TE] Fixed cache bug with port specs
* [TE] VisTrails Next
** Most packages now work
** No qgis for Python 3

'''Items to Discuss'''
** Always dereference symlinks? [https://github.com/VisTrails/VisTrails/issues/1146 #1146]

=== February 23, 2016 ===
'''Updates'''
* [TE] Fixed PythonSource 100% CPU bug
* [TE] VisTrails Next
** Updated [http://opendap.co-ops.nos.noaa.gov/axis/webservices/wind/ NOAA Web Service] examples
*** Now uses REST service, tabledata, and Google Maps
*** Web Service replaced with DownloadFile

'''Items to Discuss'''
* [RR] Couple of fixes are in for API, and tej&reprounzip on the Mac binary. Also new release of tej, and working on anonymous usage reports.
** New 2.2 release soon?
* [RR] Anonymous usage reports
** Sends out info like number of modules & versions, packages used, Python & libs versions, execution time, specific features [https://github.com/VisTrails/VisTrails/pull/1154 #1154]
* [JF] Bring in noWorkflow to track variable dependencies, for the considered Jupyter integration?
* noWorkflow - provenance for python scripts
** Recent work on tracking dependencies
* Also integrates ReproZip with Jupyter
** [http://mybinder.org mybinder]
*** Use with ReproZip to automatically build Jupyter notebook interfaces
* Daves comments on Jupyter integration
** It is possible to identify cell order on the server side
** Not trivial to track order of cells on client side
* How does Galaxy workflows relate to VisTrails?
** Packaging in Galaxy is hard
** Galaxy for biomedical workflows, difficulty making it general
* Action items
** How difficult to track cell dependencies in Jupyter notebooks?
** Use noWorkflow to track cell dependencies?
** How difficult to modify mybinder to use ReproZip packages?

=== February 17, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixed Group memory usage
** Modules in groups are supposed to be freed when done executing
*** Prevented by logger that stored references to the modules (fixed, now using id(module))
*** Prevented by list iterator bug that stored list of modules on the 'self' port bug (fixed)
* [TE] VisTrails Next
** Removed deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** PythonSources will be upgraded
*** Fixes for Python < 3
*** fixes for VTK < 6
** TODOs
*** Remove RemoteQ
**** Port Hadoop to tej (Already have pbs)
*** Merge package wrapper
*** Finish SQLAlchemy branch
*** Finish new bundle branch
** [JF] Will contact Jeff and Matthias about moving to Python 3
* [JF] Query by Example is broken
* [JF] VisTrails Data Cleaning Project
** Use VisTrails to process and explore task-specific data while keeping provenance.
** Remi's Idea
*** Use VisTrails as the backend in a Jupyter notebook
*** Overcome problems with executing cells in random order
**** Interesting research topic, but little interest has yet been noted
*** Interesting to study how such a notebook would be used (Is there notebook usage data available?)
*** Impose restrictions to notebook cell boundaries
*** It will only work for functional operations
*** Can we fix, or detect, non-functional (mutating) operations?
*** Analyse code and data flow and see if it mutates data in unexpected ways?
*** Mutable operations can be created in many ways in Python
* Next meeting Tuesday 11:30

=== February 10, 2016 ===
'''Updates'''

'''Items to Discuss'''
* VisTrails Next
** Test suite passes
*** Python 3 less deterministic, module upgrade order random.
** [RR] updating packages: Reprounzip (pushed), tej, persistent_archive, ...
** All of our packages should run fine :)
** VTK thumbnail comparison works
*** Rendering bug on some systems
**** QVTKCell now inherits QGLWidget
*** Old thumbnails had wrong height due to spreadsheetwindow being too small
**** Fixed by regenerating thumbnails
*** Silenced deprecation messages when generating modules
*** Many new classes in VTK 7
** Remove deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** Will break existing PythonSources
**** Try to upgrade?
*** Old-style packages
**** Or only allow a new style, like __init__.py renamed to info.py? (merge with identifiers.py?)
***** Read info.py without importing package?
*** Fixes for Python < 3
*** Fixes for Qt < 5
*** fixes for VTK < 7
*** Remove self port?

=== February 3, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] [http://lists.vistrails.org/pipermail/vistrails-users/2016-January/000402.html Rendering a .pvd (ParaView) file?]

* VisTrails Next
** All tests but thumbnail comparison passes
** Still issues with gui and more packages needs to be tested
** PythonSource and MplSource upgraded with lib2to3
** Keep contrib packages? Update?
** [https://blog.kitware.com/vtk-7-0-0/ VTK 7 is released]
*** Supports Python 3
*** Will hopefully get into conda and others soon
*** Deprecates a bunch of modules

* [https://travis-ci.org/VisTrails/VisTrails/builds/106743348 Travis builder] for VisTrails Next
** Runs!
** Uses conda
*** Many levels of requirements
**** apt packages
**** conda packages
**** python packages in requirements.txt
**** python packages in setup.py
*** Can probably drop conda. Default builder does not have Qt5, but beta builder do!
*** But useful if we want to use conda in our own build process.
** Lots of errors I do not get locally?

* [http://goo.gl/forms/Z4HBrwaBWL User Survey]
** Have you used any alternatives to vistrails?
*** Relevant? More options?
** How often do you use any of these particular features in VisTrails?
*** Add/Remove alternatives?
** How important would you rank the following potential improvements to VisTrails?
*** Add alternatives?

=== January 27, 2016 ===
'''Updates'''
* New interpreter
** Working prototype soon
** Looping not completely done (and port combination mode: pairwise/cartesian...)
** Need to integrate with VisTrails
*** Compatibility with existing modules
*** Use log controller
*** Want to cache at multiple levels (whole stream/single element of stream)
*** Non-runtime attributes of modules (cache check, automatic conversion check, constant from/to string)

'''Items to Discuss'''
* User Survey

* ZMQ failing on windows (vistrails-users)

* [TE] [https://github.com/VisTrails/VisTrails/pull/1143 Python 3 branch]
** Testsuite almost passes
*** Failing are unicode filenames, some users guide examples, and thumbnail comparisons.
** Fixed issues
*** Signatures are now bytes (convert to string to show in widget)
*** Cannot compare different types, e.g., (None < 1)
**** PortSpec.depth and min/maxConn could be None. (Backport!)
**** cell.row could be None
*** Lots of unicode/bytes fixes to serializations
**** We have encryption implementations in the code! (keychain)
*** Lots of small fixes to package method differences
** Current issues
*** logging widget empty?
*** version tree signals messed up
*** provenance view legend icons black
*** Text do not fit in some widgets
*** VTK thumbnail comparison fails
**** VTK Cells have some faces in wrong direction?
**** Because running in VM?
** Installing on Ubuntu LTS/Latest Mint
*** Install latest matplotlib from pip
*** Install VTK 7.0.0rc2 from source
*** No QtWebEngine binary (controversial) (Must install sip/PyQt5/Qt5 from source)

=== January 20, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Backporting features from Python 3 + PyQt5 + Qt5
** Merged unicode with master ([https://github.com/VisTrails/VisTrails/tree/unicode unicode])
*** One unicode test failing
*** Problem saving to xml
** Used [http://python-future.org/ python-future] to run futurize stage 1 to update legacy (pre 2.6) code ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized unicode-futurized])
*** Updates print to functions 'from __future__ import print_function'
*** Updates exception calls to use 'as'
*** removes most usages of 'long' (mostly used unnecessarily)
**** Only needed for 32-bit support
*** Fixes relative imports (from __future__ import absolute_import)
** Fixing code that is deprecated in Qt 4.8 and removed in Qt 5 ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized-qt5 unicode-futurized-qt5])
*** Updated all signals to new-style
* If we go 2 to 3, this could break packages
** means we should schedule any package format changes for the same time
** e.g., imports should be unrelated to code path (function to load module from package identifier?) (take them out of vistrails.* [https://github.com/VisTrails/VisTrails/pull/1002 #1002])
** any structural changes (e.g. the __init__ versus init thing) (RR thinks it makes sense, though having both named "init" is unfortunate)
** putting package identifier as xml?
*** Python not so bad, plus some stuff in there is Python code (checking dependencies)
** version the APIs?
*** RR planning on versioning vistrails_module.Module, no point versioning the whole package?
* file formats on 2 to 3:
** no real translation/upgrade, but non-ascii values that work on 3 won't load in 2

=== January 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://gist.github.com/rexissimus/dfd27e466427529c385c Porting to Python 3 / PyQt5]
** Basic GUI and execution works
** Minimal work to support 2to3
** Hard to support both PyQt4 and PyQt5

=== January 6, 2016 ===
'''Updates'''
'''Items to Discuss'''
* Updating VisTrails dependencies
** Successfully built [https://gist.github.com/rexissimus/f1a1aada7de1c00a57c7 Win7-64/Python3/PyQt5/Qt5/WebEngine/VTK7]
*** VTK 7 is the first supporting Python 3 but is only in release candidate phase.
**** Next version of VTK 6 is rumored to support Python 3
**** There is a development branch of VTK 6 supporting Python 3
*** Can travis build this?
**** We can skip tests for WebEngine and VTK if needed
** Python 3 [https://python3wos.appspot.com/ showstoppers]
*** No MySQL-python (sqlalchemy supports mysql through other drivers)
*** No suds (there are active forks but we could also drop support?)
* Options for python2/3 support:
** Interpreter could be python2/python3 based on packages
** six layer works but not the easiest to maintain (e.g. in reprozip)
* Drop support for win-64
* Update copyright headers to 2016

== 2015 ==

=== December 30, 2015 ===
'''Updates'''
* Bokeh package finished
** Can output to Browser/IPython/Spreadsheet (Limited functionality in spreadsheet)
'''Items to Discuss'''
* Updating VisTrails dependencies
** Bokeh needs QWebEngine (Chromium) in Qt5 which requires PyQt5
*** Many plotting libraries only work in browsers
*** But Chromium may be a big and controversial dependency
*** Or create a browser version of the spreadsheet?
** Some users have requested Python 3
** Not backwards compatible?
** Target for VisTrails 3.0 with new interpreter?

=== December 16, 2015 ===
'''Updates'''
'''Items to Discuss'''
* Users list question
* [TE] Wrapping Bokeh
** Added bokeh property parser
*** complements numpydoc parser
*** Not all attributes are available, partially because I am using a pre-release version.
** Wrapped modules
*** bokeh.plotting finished (Backwards like matplotlib: Create plot then draw on it)
*** bokeh.charts mostly done (Missing arguments)
** QWebView mostly works (but no zooming or buttons)
*** It would be better to use external browser or QWebEngineView
** Added improvements to wrapper
*** Generalized port translations (Color/Path to native types)
*** Can use multiple docstring/property parsers simultaneously

=== December 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Looking into wrapper
** Will port TensorFlow
** Doing a pass on the wrapper code & doc
*** UX improvements
** Factorize high-level docstring parsers into core.wrapper? (sphinx, numpy, google)
** Problem with name vs module_name (fails sklearn tests because class_by_name() is broken)
** Looking into compressing specs, lazy registration of modules

=== December 2, 2015 ===
'''Updates'''
* [TE] Package wrapping
** Wrapped most of numpy/scipy using __all__
** Added class attribute and method access for classes (Can add to class or to separate inspector module)
** TODO: Document wrapping procedure

'''Items to Discuss'''

=== November 25, 2015 ===
'''Updates'''
* [RR] New interpreter is coming along
** Everything is a stream
** Task system, eventually work-stealing parallelism
** Streams no longer advance in lock-step
*** Allows for constructions like filter, join, sorted-merge
** depth>1 still to be tested, no current plan to allow this through the module interface
*** Through looping though, can do streams of streams

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapped most numpy functions (no polynomials)
** and half of scipy classes and functions
** Added functions manually from documentation (no parseable lists?)
** Focusing on data flow constructs (no property/method access for classes)
*** Using spec diff (empty for now) and dynamic parser (stores spec in .vistrails/)
** Python class/function wrapper now stable
** Add google doc parser?
*** Is there a parser available?

=== November 18, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Numpy class wrapping works
*** Basic type is List, since most types are array_likes.
*** TODO: More classes and functions
*** Some operations are in-place and some aren't, and docstring not super clear
*** [RR] It seems only methods mutate, and most have a numpy.xx function equivalent; just manually go through the methods and remove the mutating ones?
** Class wrapper is modular
*** Docstring parser and type string parser can be customized
*** Classes can have optional attribute/method ports
**** Inspectors and attribute/method modules can be created separately
** Use PythonCalc as an example
*** Can be re-implemented as a function with a parseable docstring
*** [RR] PythonCalc is just an example, and it might actually make sense to get rid of it, or do a proper math package with scalar operations (as separate modules, no combobox)
** [RR] TensorFlow to use wrapping as well
*** Very simple (only types 'tensor' & 'variable')

=== November 11, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapping numpy's classes using numpydoc (ndarray)
*** Wrapping constructor arguments, attribute getters/setters as module ports
**** Then how to access attributes afterwards?
***** Use input value port to class modules?
*** Wrap methods as modules? E.g., `ndarray.shape`.
*** Function wrapping is almost a subset of class wrapping
**** May be able to use the same parsing/execution methods
** VTK's non-getter/setter methods could be wrapped as modules
*** We could then remove extra logic in interpreter for keeping function order
** Bokeh uses autogenerated docstrings
*** We may be able to read the specification directly

* [RR] [https://github.com/VisTrails/VisTrails/pull/1138 TensorFlow package]
** Basic setup working, can execute the Mandelbrot example
** Will autogenerate the operations

=== November 4, 2015 ===
'''Updates'''
* [RR] Interpreter work requires a fix for [https://github.com/VisTrails/VisTrails/issues/1137 DB issue #1137]
* [DK] Kitware's Resonant [http://www.kitware.com/source/home/post/173]
** [https://github.com/girder/girder Girder]: data management system
** [https://github.com/Kitware/romanesco Romanesco]: execution engine, uses [http://www.celeryproject.org/ Celery] for task management
** Resonant Flow: web app for editing and executing workflows

'''Items to Discuss'''
* [TE] Added OSX Lion (10.7) VM on build machine using vagrant (seems ok with license?)
** New builds works on Lion
** Change the minimum requirement to 10.7?
* [TE] Package wrapping
* Added upgrade suggestions using 2 spec versions ([http://pastebin.com/30XUU8Gp example])
** using name edit distance to find matches
** Could use something better like port similarity for modules, and type similarity for ports
** Should write python upgrade code?
** Added spec to sklearn package
*** Can now diff spec versions and keep the spec static
*** There will be problems with downgrades and package versions

=== October 29, 2015 ===
'''Updates'''
* [TE] nightly-build-mac fixed (Needed to approve xcode license)

'''Items to Discuss'''
* [TE] matplotlib wrapper
** ported to general spec
** Diff can be used on general spec
*** Only needed minor changes
*** Fixed indexing bug that corrupted specs
*** Can now move diff tools to core/wrapper
** Add new plots?
*** New plots in mpl 1.3: eventplot
*** New plots in mpl 1.4: angle_spectrum, magnitude_spectrum, phase_spectrum', violinplot
*** No new plots in mpl 1.5 (from looking at boilerplate.py)

=== October 21, 2015 ===
'''Updates'''
* [RR] Alexis has arrived, will be working with [RR] on a more efficient interpreter

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package]
** Supporting multiple package versions
*** Check which version can be loaded [https://github.com/VisTrails/VisTrails/pull/1135 #1135]
*** We cannot show version requirements in the list of packages because old packages are loaded when importing the codepath
** Visual diff does not work well, but we can use the spec differ to see differences.
** Unifying vtk and matplotlib wrapping specs (WIP)
*** And porting matplotlibs spec differ to work on the general spec
*** Spec differ can then be used on vtk and other packages in the future
*** Will enable automatic upgrade generation
* [RR] Rework interpreter
** restore abstraction between interpreter/module code
** build looping, streaming, caching into the interpreter
** rework cache
** look into parallelism once basic functionality is there

=== October 14, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package] (adding numpydoc parser)

=== October 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/tree/fix-matplotlib-parser New matplotlib parser] (adding numpydoc parser)
** Added numpydoc attribute parser for plots.
*** TODO: Need better port spec reconciliation with call signature parser.
*** We can create a general numpydoc parser, but attribute types are unique to matplotlib.
** Needs package versioning
*** New spec will not support matplotlib < v1.4 due to changed path to axes classes.
*** Load spec version corresponding to installed matplotlib version?
*** Need version downgrades?

=== September 30, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Updating Matplotlib parser
** Matplotlib docstring parser fails on numpy docstrings
** I have [https://github.com/VisTrails/VisTrails/commit/eae8b0c16260810587e47c41cab53552cbb3cf0a added basic numpydoc parsing]
*** Only used by a few docstrings so far
*** Parsing uses many sources (class tables, signatures, ACCEPTS, method docstrings, definition parsing).
** Caswell said they were thinking about moving to traitlets, but this is not ready yet

=== September 23, 2015 ===
'''Updates'''
* [TE] VisTrails 2.2.3 released
** Also have pushed to PyPI, binstar, etc.
** Sourceforge vs. GitHub
*** should be able to host releases on GitHub
*** nightly binaries pushed to sf each night
*** old binaries?
* [TE] Re-wrapping MatPlotlib
** Keep static generation - Docstrings are brittle beween matplotlib versions
** Keep generating the executable classes - but create functions, not vistrails Modules
*** Why is there so much patching?
** Re-implemented Alternate PortSpec for InputPortSpec
*** It will now inherit specs from parent (No need to reimplement)
** Module upgrades?

'''Items to Discuss'''

=== September 16, 2015 ===
'''Updates'''
* [TE] Job Monitor tests and documentation done
** OK to leave document package in packages directory?

'''Items to Discuss'''
* [TE] Library wrapping: How to do code patching? [https://docs.google.com/drawings/d/1Sh3eOXot6v2y880jHKQrqXqAwr-0aoqYligg3z8G8MY/edit?usp=sharing Wrapping diagram]
** Insert code into module template (Old VTK code)
** Patch the library that is called (New VTK code)
** Somehow store code in spec and apply when executed?
*** Executed code needs at a minimum access to inputs, outputs, current class
*** Use standard input/output dict and obj reference that the code operates on?
*** Can this be done while keeping the execution abstract?

* Do new release now?

=== September 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* New release?
** [RR] wants reprounzip
** tej changes & doc
** job monitor & jobmixin fixes
** mongodb
** reprounzip
** warning: MplFigure type is int
** tabledata: add Reshape, DictoToTable & ListToTable, fix ListToTable with numpy arrays
** PythonSource can have same name for an input & output
** don't show spreadsheet at exit

=== September 2, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Limit autosaves? [https://github.com/VisTrails/VisTrails/pull/1126 #1126]

=== August 26, 2015 ===
'''Updates'''
* [TE] Added Job support to Parameter Explorations (Requested by Colin), and Mashups
** specify job ids, need to specify different ids for parameter explorations since they have the same version id
** how to deal with parameters passed in on command line
* [General] provenance: should be creating a new version when we execute workflow with changed parameters?
** currently, custom_params annotation stores this in provenance currently
** [RR] API doesn't record provenance if passing in parameters: http://git.io/vsAA5
'''Items to Discuss'''

=== August 19, 2015 ===
'''Updates'''
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [TE] Working on Job Monitor documentation

'''Items to Discuss'''
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [TE] Stop testing VisTrails 2.0?

=== August 12, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Build broken on Travis; because of IPython 4 released today? ([https://travis-ci.org/VisTrails/VisTrails/builds/75279795 build 992]; [https://github.com/VisTrails/VisTrails/issues/1123 #1123])

=== August 5, 2015 ===
'''Updates'''
* [TE] Fixes to Jobs
** Could not delete jobs
** Could not run job in group
** Job not reset when calling ModuleSuspended
** Added deleting job from context menu
* [RR] Writing documentation for everything [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

'''Items to Discuss'''

=== July 29, 2015 ===
'''Updates'''
* RR still looking into new interpreter thing
** Goal is to take out scheduling logic from Module so it can be split in multiple processes, and so that smarter strategies can be added in time
** This means some work on packages
** Spreadsheet can live in kernel process? Still some UI stuff that will take work (changing configuration, persistent archive's viewer, ...)
* [TE] Problems running examples [https://github.com/VisTrails/VisTrails/pull/1111 #1111]
** Testing of more examples requires additional packages on the test machines.
** Fixed faulty line-ending in PythonSource:s failing on Python 2.6.
** Test suite now testing SUDSWebServices (If web service is down, test suite will fail)
** preferences.py test failed reloading 'dialogs' package, switched to using 'URL'.

'''Items to Discuss'''

=== July 22, 2015 ===
'''Updates'''
* [TE] mailing lists back online
* [TE] Working on [https://github.com/VisTrails/VisTrails/issues/1107 #1107]
* [RR] Working on ReproZip package

'''Items to Discuss'''
* [RR] MongoDB package [https://github.com/VisTrails/VisTrails/pull/1106 #1106]
* [RR] Example for tej docs? [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

=== July 15, 2015 ===
'''Updates'''
* 2.2.2 released

'''Items to Discuss'''
* RR is considering executing everything in an IPython kernel (i.e. separate Python interpreter, like the one spawned for a notebook)
** It's a separate process that we can restart without restarting the app/gui
** We can isolate the execution environment (e.g. for the server)
** We can run the whole thing remotely (if your data is elsewhere, just run VisTrails locally and the pipeline elsewhere)
** Pipeline execution no longer makes the interface hang, it just makes the kernel hang (but that's fine)
** We can use notebooks as modules (probably way nicer than the PythonSource module)
** We can run multiple kernels so long as the ports carry things that are serializable
*** meaning we can put the multithreaded-interpreter without all the hacky parts it has now
*** we can run IPython kernels in all the languages IPython supports, [https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages currently 46]

=== July 8, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Buildbot github hook not working after IP address change
* [TE] No reference to VistrailsApplication ([https://github.com/VisTrails/VisTrails/issues/1103 #1103])
** [RR] Added PR [https://github.com/VisTrails/VisTrails/pull/1104 #1104]
* [TE] Reopening VT file after saving with bundled subworkflow won't offer subworkflow upgrade ([https://github.com/VisTrails/VisTrails/issues/1102 #1102])
** allow manual delete to fix right now
** fix this on top of the use-uuid branch
* [TE] Release VisTrails 2.2.1? ([https://github.com/VisTrails/VisTrails/blob/v2.2/CHANGELOG CHANGELOG])
** [https://github.com/VisTrails/VisTrails/pull/1093 output-modules-use-global-dir]
** [https://github.com/VisTrails/VisTrails/milestones/version%202.2 Current issues for 2.2]

=== July 1, 2015 ===
'''Updates'''
* [TE] PROV fixed
* [TE] Working on subworkflow issues
* [RR] Considering reworking the controller (log vs exception problem, retained upgrades causing interferences) and also the interpreter (IPython?)

'''Items to Discuss'''

=== June 24, 2015 ===
'''Updates'''

'''Items to Discuss'''
* UV-CDAT
* [TE] Can a cyclic workflow be valid? ([https://github.com/VisTrails/VisTrails/issues/1097 #1097])
** focus on disabling the ability to create cyclic pipelines because more things break than just this with a cyclic pipeline
* [RR] Relative paths ([https://github.com/VisTrails/VisTrails/pull/1057 #1057])
** This interacts with the new bundle; how do handle packing files inside the VT bundle?

=== June 17, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] current_version and reusing existing upgrades are broken ([https://github.com/VisTrails/VisTrails/issues/1095 ticket #1095])
** Could be that export to PROV is using an unflushed upgrade pipeline?
** current_version would then be correct.
** It may work to flush the actions before exporting?

=== June 10, 2015 ===
'''Updates'''
* DAT: fixed VTK issue on Linux and Mac
* Still crashes on Windows. Need help! Reminder: this works in the VisTrails spreadsheet (QCellPresenter), although no widget get changed there during a drag
** Is it a VTK bug?
** Is it simply impossible to change widgets during the drag, should we do it a different way?
** Did I miss something that is done in VisTrails but somehow not in DAT?
** Low prio, UV-CDAT doesn't run on Windows anyway

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 Updated pull request])
* Single instance code and batch mode

=== June 3, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 pr])
** Requires fixes to command line parameters, Output modules, and batch mode
** How to test this
** Updated missing/outdated flags
** Fixed view issues when generating graphs
* [TE] batch mode
** SpreadsheetOutput not enabled in batch mode. Should we check is_running_gui instead?
** Other instance setting flags from caller
** Is graphsAsPdf replacing spreadsheetDumpPdf?
** graphsAsPdf true by Default?
** Batch mode executing by default (Not needed when generating graphs)
** Re-added workflowInfo as withWorkflowInfo for writing graph and xml workflow
** [DK] batch mode should be outputting to files or stdout, shouldn't always trigger SpreadsheetMode
** execute flag, maybe make execution the default and allow a "--no-execute" if you only want to capture graphs, for example

=== May 27, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] API question
** http://lists.vistrails.org/pipermail/vistrails-users/2015-May/000357.html
* Status of DAT
** Can add VCS plot to DAT but need to work on configuration windows
** Documentation for graphics templates for UV-CDAT/vcs?
* Qt support?

=== May 20, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Reviving the DAT, integrating scripting & porting UV-CDAT!
** On [https://github.com/VisTrails/DAT GitHub] ([https://github.com/VisTrails/DAT/issues issues])
** Merging 2 years of development taking longer than expected, but getting there. The plan is to get the patches in VisTrails and never fork again, we never want to get in UV-CDAT's situation (and don't need to).
** VTK cell works fine on Linux but there was flickering on Mac & Windows before; still issues on Mac (Windows status unknown)
** Can get a VCS plot soon (but will need VTK cell fix)
** Integrate in UV-CDAT's build system (so we have cdms, VCS, ...) -> RR can do this, low priority
** How do we integrate scripting?
*** We want to be able to seamlessly make changes to a plot by changing Python code
*** Define new plots by entering Python code without writing modules/packages?
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 13, 2015 ===
'''Updates'''
* [RR] Test skipping whitelist ([https://github.com/VisTrails/VisTrails/pull/1069 #1069]) -- low priority
* [RR] Custom matplotlib modules can't be compatible with both 2.1 and 2.2 ([https://github.com/VisTrails/VisTrails/issues/1067 #1067]); should be fixed for ALPS ([https://github.com/VisTrails/VisTrails/issues/1070 #1070])

'''Items to Discuss'''
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 7, 2015 ===
'''Updates'''
* [RR] Export/import workflow to Python working!

'''Items to Discuss'''
* [Claudio] UV-CDAT
** The UV-CDAT project is the biggest user base of VisTrails
** VisTrails package management provides a lot of friction towards people plugging in their code
** Need to make it easy to integrate your random Python scripts in the system without having to deal with all the boilerplate, at least in the first step
** [RR] argues that modules are still good; UV-CDAT shouldn't move towards a purely script-based backend
** [RR] export/import with Python could reduce a lot of that friction by allowing 1) to edit workflow as Python 2) to open up boxes automatically if needed code doesn't match actual modules
** ...

=== April 29, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] <strike>Abstractions</strike> subworkflows status ([https://github.com/VisTrails/VisTrails/labels/subworkflows tickets])
* [RR] matplotlib compatibility (2.1 & 2.2), [https://github.com/VisTrails/VisTrails/issues/1067 #1067]
** RR to try and fix ALPS matplotlib modules

=== April 22, 2015 ===
'''Updates'''
* 2.2.0 has been released!
* Windows issue (via email from Ryan)
** issue with manifest file (may be a new file in VTK6?)
** Tommy has regenerated new Windows builds
* Binaries, pypi, and conda released
* [RR] Export as script
* Python sources using VTK need to switch to SetInputData (users should be aware of this)

=== April 15, 2015 ===
'''Updates'''
* Ready for 2.2.0 (apart from binary/deps issues)
** Missing some libs (scikit-learn, tej, tdparser, SQLAlchemy+connectors
** Windows: runvistrails.py is no longer used, so the PATH is wrong
** Windows: pip is broken, but it probably wouldn't work anyway because of permission issues (disable this?)
* Queries, upgrades and getPipeline() usage ([https://github.com/VisTrails/VisTrails/issues/1054 #1054])
** Getting a pipeline with getPipeline() is not safe: it might return an invalid pipeline
** This is used in many places throughout the code, like queries
** Upgrading would require going through the controller, but that creates new actions
* [TC] Avoid copying a module's output if it's used as input by exactly one downstream module ([https://github.com/VisTrails/VisTrails/issues/1060 #1060]) (useful for big numpy arrays you can update in-place)

=== April 8, 2015 ===
'''Updates'''
* [DK] Merged RR's changes for output modules (1012 and 1013)
** RR will merge remaining changes, then create v2.2 branch!

'''Items to Discuss'''
* BNL need numpy array to VTK image
** Looks like VTK has some helpers for this
** We will help if issues arise
** Will contribute back to VisTrails package
* Upgrade issue: [https://github.com/VisTrails/VisTrails/issues/1017 #1017]
** Automatic upgrades should happen between versions of provided upgrades
** Our existing upgrades work around this so it doesn't need to be 2.2.0
* Corner-case VTK modules
** No longer need VTKCell input port, so don't interfere with registry and API anymore
** Still work weirdly, people probably shouldn't use them
** But we have lots of clunky modules since we wrap the whole of VTK; some people might rely on this and know how to use them, let's keep them anyway
** Ready for 2.2.0

=== April 1, 2015 ===
'''Updates'''
* [RR] UV-CDAT: bugfixing for 2.2, long-term plans: implement scripting import/export in VisTrails, port to UV-CDAT
* Possibly, try to move to regular VisTrails to use new features

'''Items to Discuss'''
* 2.2 release: nothing much is pending anymore, release next week?
** [TE] vtkExporter classes [https://github.com/VisTrails/VisTrails/issues/1032 #1032]
** [RR] Hiding upgrades in version tree might make it (or might be 2.2.1 so we can test it out) [https://github.com/VisTrails/VisTrails/issues/949 #949]
** Output modules changes to go in
* add note to documentation about order of parameters in VTK
* add issue about exporter upgrades if not already there

=== March 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* 2.2 release
** Checklist on Github: https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist
** Review output modules
** RR has a couple more issues to fix
** Ready to go -- sign app package for OSX? [https://github.com/VisTrails/VisTrails/issues/984 #984] We need access to the Apple Membership team

=== March 18, 2015 ===
'''Updates'''
* [TE] VTK6 works

'''Items to Discuss'''
* [RR] Release v2.1.5 with backported tabledata?
** MTA example needs updated tabledata (for JoinTables)
** Google Maps package still not available
* [RR] Work torward v2.2.0?
** changes:
*** new persistence
*** API changes
*** output module changes (upgrades?), maintain cells but try to upgrade
*** not wrapping stuff
*** VTK6? yes
*** JobSubmission stuff?
*** relabeling for upgrades [https://github.com/VisTrails/VisTrails/issues/949 #949]
** makes sense, needs the tree view code to be updated, check selection
** See [https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist 2.2 checklist]
* Discussion of [https://github.com/VisTrails/VisTrails/issues/1016 #1016]
** plumbing between outputs and output modes, how to define a mode that works for many outputs without writing for each output?

=== March 11, 2015 ===
'''Updates'''
* [RR] persistent_archive done; merge? ([https://github.com/VisTrails/VisTrails/pull/755 #755])
** note about the focus events for widgets
** TE be aware of file_archive for future binaries that include persistent_archive
* [TE] [https://github.com/VisTrails/VisTrails/pull/998 New VTK package] finished

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails? (see last week; decision needed)
** RR email to JF about this
** yes; email sent to Github
* [RR] Switching order of output ports ([https://github.com/VisTrails/VisTrails/pull/1006 #1006])
** added port specs are sorted at a separate spot (Module.*_port_specs properties) than those in the registry (which are sorted in the registry), but those two lists are just combined without respect to sort keys
** need to determine whether the two lists should be merged or remain distinct
** should make sure that order of input ports and output ports makes parallel connections for things with same order
** DK suggests breaking backward compatibility here: workflows still run, can fix easily if a problem in an existing package.
* [RR] Question about output modes ([https://github.com/VisTrails/VisTrails/pull/1007 #1007]), how to integrate in API ([https://github.com/VisTrails/VisTrails/pull/24 #24])
** Should ImageFileMode be removed? ("image" is not a mode, "file" is)
** ImageOutput missing?
** Feel free to change how formats works
* [TE] Test suite segfaults on Fedora 17 virtualbox. Install newer version? (Support ended in 2013)

=== March 4, 2015 ===
'''Updates'''
* [TE] VTK wrapper
** Works on VTK 5.10
** Still need to test VTK 6
** New general wrappers for python functions and classes

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails?
** When [http://i.imgur.com/UTY2qfg.png filing a pull request] from UV-CDAT/VisTrails, VisTrails/VisTrails is selected by default
** People keep forgetting to change the default ([https://github.com/VisTrails/VisTrails/pull/956 #956] [https://github.com/VisTrails/VisTrails/pull/968 #968] [https://github.com/VisTrails/VisTrails/pull/999 #999] [https://github.com/VisTrails/VisTrails/pull/1000 #1000] [https://github.com/VisTrails/VisTrails/pull/1003 #1003] [https://github.com/VisTrails/VisTrails/pull/1004 #1004] [https://github.com/VisTrails/VisTrails/pull/1005 #1005])
** Only way to change that is to not have it marked as a fork of VisTrails/VisTrails
** Github staff [https://gist.github.com/remram44/b364c24ef1e462ce6e2f can make that change for us]; should we do it?
** Juliana: comments on this? visibility vs. convenience/annoyance for developers
* [RR] What about [https://github.com/VisTrails/VisTrails/issues/991 #991]?

=== February 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] vtkviewcell for infovis support, can we unify with VTKCell?
** need to test this
* [TE] vtk wrapping
** Mostly finished
** VTK 5.10 produce incorrect results with old wrapping
*** Old wrapper is based mostly on VTK 4
*** Most vtk_examples affected
*** [http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Replacement_of_SetInput]
*** should be able to upgrade from SetInput to SetInputData (need to drop GetOutput and replace with self ports)
*** can we change vtkInstance to just return self and not wrap things
** terminator example not working under 5.8?
* How does VTK wrapping fit into general wrapping framework?
* [RR] new persistence package

=== February 18, 2015 ===
'''Updates'''
* [RR] New VisTrails API and IPython integration ([https://github.com/VisTrails/VisTrails/pull/24 #24])

'''Items to Discuss'''
* [TE] VTK wrapping
** [https://gist.github.com/rexissimus/16b74693545b5e7c1035 Benchmarking vtk package]
*** Old: 24.7 seconds
*** New: 10.5 seconds (Except first time that adds 8 sec)
**** The parsing that calls is_abstract (that tries to instanciate all vtk classes) is now only run the first time.
**** get_items_from_sigstring takes 2 seconds, maybe we can use a lookup dict for already computed sigstrings?
** Now using a general python function wrapper
*** VTK classes are wrapped into python function that does not depend on vistrails
*** VTK functions can be executed without vistrails
*** The spec maps functions into vistrails modules, but can also describe wrapping
*** A general python function wrapper that supports
**** kwarg inputs
**** single, list, dict outputs
**** callback for progress reporting
**** temporary file generator for using FilePool
**** optional output generation
*** Creating specs:
***** Create spec by hand
***** Auto-create spec outline (TODO) and manually finish it
***** Dynamically create spec (VTK)
***** Implement documentation wrappers (Can use scikitlearn wrapper to wrap numpydoc) (TODO)
***** Classes as bad functions needs to be wrapped in new functions before they are wrapped. This is different for each package.
****** Classes is hard: Like VTK, and matplotlib. Scikit-learn does still not wrap classes
***** Spec diffing and patching could be done using code from matplotlib.
** Still needs upgrades from old VTK package
*** Is it possible to dynamically wrap functions, e.g, you see a SetFunc and just remove the 'Set' prefix. Or do you need to create a complete mapping?

=== February 11, 2015 ===
'''Updates'''
* Update from Friday's meeting
** discussed VisTrails internals
** discussed wrapping
*** xml discussion, hard to modify because tied to db code
*** TE has made it possible to add the schema-defined attributes to the intermediate representation
*** higher-level operations on the port specs
** make sure the simple case works
*** [JF] take a simple package with documentation and figure out what the base case for wrapping is

'''Items to Discuss'''
* [TE] VTK wrapping
** Dynamic loading works
** Reading XML is fast enough, but [https://gist.github.com/rexissimus/8272d3c776ccfa115d82 unserializing data is slow]
** Working on patterns for patching
** Matplotlib has many advanced patterns like argument ordering, nested arguments, alternateSpecs, output types.
*** Having all this in a general wrapper might confuse users?
** [RR] Delay module (except for identifiers) until you need it---e.g. don't deal with port specs, etc. until necessary
* Scripting Support [https://github.com/VisTrails/VisTrails/pull/950 #950]
** [RR] Issue with getting code from modules
** Design a simple solution
** [JF] Couldn't you use modules as black boxes without conversion, just to call into modules/subworkflows easily from e.g. IPython?
*** [RR] This is a job for the API, and a very separate use case. See [https://github.com/VisTrails/VisTrails/pull/24 #24]

=== February 4, 2015 ===
'''Updates'''

'''Items to Discuss'''
* Wrapping
** Format to use? Currently XML (like current matplotlib)
*** JSON and YAML have simple "to python dictionary" methods
*** But don't stream
*** YAML a lot easier for humans
** [DK] vtk-new-package also changes parameter names, creates enumerations
*** intermediate schema needs to be extensible
*** packages will want to store there specific infos for compute() method generation
*** also might have specs-altering info, like matplotlib's alternateSpec
** representation to code , registry already has schema for some aspects
** [RR] We might want to see if Module subclasses can be created lazily
*** no need to create all the classes just to register them in the registry and never actually use most of them
*** future effort
* [RR] Where should VisTrails packages live?
** tej installs as 'vistrailspkg.tej', TE installed it as 'userpackages.tej'
** Currently, standard packages are 'vistrails.packages.', user packages are 'userpackages.' and packages loaded through pkg_resources might be anything
** [RR] Use 'vistrailspkg.' everywhere?
** Long-term effort to simplify package distribution/installation (and have VisTrails get them automatically?)

=== January 28, 2015 ===
'''Updates'''
* T. Caswell to come visit on Fri 6 to discuss wrapping work

'''Items to Discuss'''
* [TE] New VTK wrapping
** Current code by DK seems a good deal faster
** Generates XML that can be patched/tweaked, generates Python code from it, VisTrails only loads generated Python code
** RR would rather have VisTrails load intermediate representation (= XML) directly, wants to make sure this is not slower
** The goal is to turn the intermediate step into something generic that would be used for every wrapped package (vtk, numpy, matplotlib, sklearn, java) instead of each having its own
** TC has its own code at [https://github.com/Nikea/VTTools/blob/master/vttools/wrap_lib.py github:VTTools] which parses numpy docstrings and generates modules, doesn't yet handle classes or persist anything
* Web crawler
** Right now, TE starts jobs for "start crawler", "stop crawler", "install classifier"
** RR would rather have the crawling be a job as far as VisTrails and tej are concerned
** The whole thing would be one pipeline: load examples, train classifier, start crawler [check for job, kill previous one, upload model, start processes], get snapshot, visualize
*** Need some support in tej and job submission system: long-running jobs, stop a job (wait for it to finish?), restart a job even though results are cached

=== January 21, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Unified wrapping method discussion [https://github.com/VisTrails/VisTrails/issues/991 #991]
** TE to work on reusable method with intermediate representation, starting with VTK
* [RR] Examples for scikit-learn: JF has an old example using Weka with parameter exploration (not currently in source tree)
** AM's examples are enough
* [AM] scikit-learn package is done, merge it in? [https://github.com/VisTrails/VisTrails/pull/955#issuecomment-70286788 #955]
** RR will merge
* [RR] What should copyright headers say? [https://github.com/VisTrails/VisTrails/pull/994#issuecomment-70173935 #994]
** Let's keep everything in there: Utah/Poly/NYU

=== January 14, 2015 ===
'''Updates'''
* [TE] Working on classifier
* [RR] Scripting integration, work in progress

'''Items to Discuss'''
* [RR] Unified wrapping method discussion ([https://github.com/VisTrails/VisTrails/issues/991 #991])
** Let's talk next week, [AM] and [DK] are not here

=== January 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* make sure that we address critical issues, questions, and pending review branches in a timely manner
* scripting support
** [RR] no issues if we want to just keep annotations in the generated code to allow the link back to a workflow
** [RR] can translate from workflow to script, working on script to workflow
** will work for parameter value changes, structural changes require changes to the annotations
** need to publish best practices here
** would be cool to do looping in scripts (easier interface than with workflows)
* notebook support (convert form notebook to workflow)
** RR will sync with FC on this
* Issue with console in built-from-scratch
** [TC] iPython rearranged some of the completion stuff in 2.2 and 2.3
** binary has old version of iPython -> 1.0.0, should we update?
* [TC] automated wrapping of numpy and scipy
** discovered a bunch of malformed documentation in numpy and scipy
** has github repo for vistrails tools
** example modules wrap a bunch of R stuff (not baked in, just how things are)
** will be pushing wrapping logic up
** port names forbidden (window and domain)
** have an import hook to get from yaml directly to VisTrails Modules
** should work for any python modules with well-formed numpy docstrings.
* [Action] should make it clear in documentation that Constant now means serializable not that the value doesn't change (e.g. List)
* [TC] might be interesting to try to build components of matplotlib and accumulate in figure (long-term project, but thinking about how this might work)
* [TE] build and build scripts
** completely automatic, buildbot
** need to set the build machines for the environment we want for the binary
** would virtualenv work here?
** [TC] anaconda can pin versions, potential path to test different configurations
** Q: upload nightly binary builds? A: makes sense, make sure they are well-labeled
* sourceforge stats: e.g. http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07
* package issues (see Remi's message)
* [TE] Scope of tej
** Support single ssh commands?
** Queue can be used as a remote machine (crawler is using queue.call*)
* SourceForge stats: http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07

== Older meetings ==
* [[Development/2014]]
* [[Development/2013]]
* [[Development/2012]]
* [[Development/2011]]
* [[Development/2010]]

Main Page

2016-05-03T14:41:06Z

Tommy: /* News */

This is the official website for VisTrails, an open-source scientific workflow and provenance management system that supports data exploration and visualization.

VisTrails provides a general infrastructure that can be combined with existing systems and libraries. Official releases come with several packages, including VTK, matplotlib, and ImageMagick. The system is written in Python/Qt and runs on Mac, Unix and Windows.

[[#Downloading VisTrails|Read more >]]

== Downloading VisTrails ==
Current and past releases are available on our [[downloads|download page]].

== News ==
* [2016-05-03] VisTrails 2.2.4 has been released and is available on the [[Downloads]] page.
* [2015-09-11] SAHM VisTrails training course at USGS: http://pubs.usgs.gov/fs/2014/3007/pdf/fs2014-3007.pdf
* [2015-07-10] VisTrails 2.2.2 has been released and is available on the [[Downloads]] page.
* [2015-04-22] VisTrails 2.2 has been released and is available on the [[Downloads]] page.
* [2015-03-21] VisTrails 2.1.5 has been released and is available on the [[Downloads]] page.
* [2014-08-25] VisTrails 2.1.4 has been released and is available on the [[Downloads]] page.
* VisTrails 2.0.3 has been released and is available on the [[Downloads]] page.
* To learn more about how to explore climate data using DV3D and ParaView in UV-CDAT, check out http://www.kitware.com/source/home/post/105
* Comparison of two forecasts of Hurricane Sandy using the DV3D slicer in UV-CDAT http://www.youtube.com/watch?v=BFN0RzN1hSE&feature=em-share_video_user
* Presentation on the use of VisTrails at NASA: VisTrails: Workflow Management System on NEX - https://c3.nasa.gov/nex/static/media/other/Vistrails-Votava.pdf
* VisTrails 2.0 has been released and it is available for download on our [[Downloads]] page. VisTrails is now distributed under the BSD license and its GUI was completely re-designed to make it easier to manage and interact with multiple workflows. It also includes a much improved [http://www.vistrails.org/usersguide Users' Manual]. See the [http://sourceforge.net/projects/vistrails/files/vistrails/v2.0/README/view release notes] for a complete list of changes. Some notable features include:
** the ability to create mashups;
** support for the creation of reproducible papers;
** a provenance viewer;
** support for visual diffs as well as queries over workflows in different vistrails;
** a Control Flow Assistant to simplify the creation of workflows with loops and conditional constructs;
** support for global variables, so that modules deriving from Constant can be used to create variables that are shared among multiple workflows.

[[Image:Screen Shot 2012-01-12 at 2.50.19 PM.png|200px|right]]
* UV-CDAT 1.0.0 has been released. More detailed information and binaries are available at http://uvcdat.llnl.gov
** UV-CDAT was demoed at [http://ipaw2012.bren.ucsb.edu IPAW 2012]
** Video tutorials are available at http://uv-cdat.llnl.gov/wiki/VideoTutorials
** Binaries (Mac/RedHAT6/Ubuntu) or build-from-sources options can be found here: http://uv-cdat.llnl.gov/install/
** Please report any issues you encounter via bugzilla at: http://uv-cdat.llnl.gov/bugzilla/

* [[Older News]]

== VisTrails Overview ==
[[Image:Cosmology_example.png|480px|right]]
VisTrails is an open-source scientific workflow and provenance management system that provides support for simulations, data exploration and visualization. Whereas workflows have been traditionally used to automate repetitive tasks, for applications that are exploratory in nature, such as simulations, data analysis and visualization, very little is repeated---change is the norm. As an engineer or scientist generates and evaluates hypotheses about data under study, a series of different, albeit related, workflows are created while a workflow is adjusted in an interactive process. VisTrails was designed to manage these rapidly-evolving workflows.

A key distinguishing feature of VisTrails is a comprehensive provenance infrastructure that maintains detailed history information about the steps followed and data derived in the course of an exploratory task: VisTrails maintains provenance of data products, of the workflows that derive these products and their executions. This information is persisted as XML files or in a relational database, and it allows users to navigate workflow versions in an intuitive way, to undo changes but not lose any results, to visually compare different workflows and their results, and to examine the actions that led to a result. It also enables a series operations and user interfaces that simplify workflow design and use, including the ability to create and refine workflows by analogy and to query workflows by example.

VisTrails supports the creation and execution of workflows. It allows the combination of loosely-coupled resources, specialized libraries, grid and Web services. The released version comes with support for several packages including, [http://www.vtk.org/ VTK], [http://www.imagemagick.org/script/index.php Image Magick], Web Services, and [http://www.scipy.org/PyLab pylab]. You can also download [[UserContributedPackages|packages contributed by our users]], as well as [http://www.vistrails.org/usersguide/v2.1/html/packages.html create your own packages/modules]. There are also a number of [[Projects using VisTrails|projects extending or building on top of VisTrails]].
Workflows can be run interactively, through the VisTrails GUI, or in batch using a VisTrails server.

VisTrails 1.0 was released in October 2007. Since then, the system has been downloaded thousands of times. VisTrails is written in Python and it uses the multi-platform Qt library for its user interface. It runs on Mac, Linux and Windows. You can download VisTrails from http://www.vistrails.org/index.php/Downloads

=== Publishing Reproducible Results ===
VisTrails 2.0 allows the inclusion of reproducible results in LaTeX/PDF documents. We provide a LaTeX package that allows users to add links to their results in the LaTeX source. For example:

<code>
\usepackage{vistrails}

...

\begin{figure}

\begin{center}

\subfigure[a=0.9]{\vistrail[filename=alps.vt, version=2, pdf]{width=8cm}}

\subfigure[a=0.9]{\vistrail[filename=alps.vt, version=11, pdf,buildalways]{width=8cm}}

\caption{A figure produced by an ALPS VisTrails workflow. Clicking the figure retrieves the workflow used to
create it. Opening that workflow on a machine with VisTrails and ALPS installed lets the reader execute the full calculation.}

\end{center}

\end{figure}
</code>

Once the LaTeX document is compiled, the figure in the PDF becomes active, and when clicked, it will invoke VisTrails and reproduce the result.
You can also upload your results to [http://www.crowdlabs.org CrowdLabs] and export them to Web sites or Wikis, where users can interact with them through a Web browser. See e.g., http://www.crowdlabs.org/vistrails/medleys/details/26/

=== Building Workflows ===
VisTrails supports workflows expressed as dataflows. It can also support functional loops and conditional statements (new in VisTrails 1.3!). In addition, VisTrails is easily extensible; users can quickly create new modules or wrap existing code or libraries for use as modules in VisTrails. Also, the <code>PythonSource</code> module can be used to write one-time translations or test code in a workflow. See the [http://sourceforge.net/projects/vistrails/files/vistrails/vistrails-usersguide-1.3-rev198.pdf/download Users' Guide] for more details on all of these features.

=== Combining VisTrails Provenance with other Tools ===
[[Image:DisplayWall_ipod_screenshot.png|180px|right]]
The VisTrails provenance infrastructure can also be combined with interactive tools. We are developing a series of provenance plugins for different tools, including [https://wci.llnl.gov/codes/visit VisIt] and [http://www.paraview.org/ ParaView]. The [http://www.vistrails.org/index.php/ParaView_Plugin open-source ParaView plugin has been released].

=== Visualizing and Comparing Workflow Results ===
VisTrails provides a ''spreadsheet'' where users can compare the results of multiple workflows, or multiple workflow runs. Besides using a desktop, you can display the results of VisTrails workflows on a display wall or on an iPod. Users can also compare different workflows using the visual difference interface.

=== Querying and Refining Workflows by Example ===
Users can quickly construct expressive queries over a collection of workflows by example, using the same familiar interface they use to build workflows. VisTrails also provides an analogy mechanism whereby users can perform complex modifications to workflows by analogy, without having to directly modify the workflow specifications.

==[[Documentation|System Documentation]]==
If you want to get more information about VisTrails you can consult the Users' Manual or the FAQ (see links below). If you have questions that are not answered in these resources, you can post it to the users' mailing list: http://www.vistrails.org/index.php/MailingLists

To report bugs, please use our bug tracker: https://github.com/VisTrails/VisTrails/issues

=== [[Documentation#Screen Shots|Screen Shots]]===
=== [[Users_Guide|User's Guide]]===
A Web version of the Users Guide is currently under development and can be accessed at http://www.vistrails.org/usersguide.
=== [[FAQ]]===

==[[MailingLists|Mailing Lists]]==
==[[Publications, Tutorials and Presentations]]==
==[[People]]==

== [http://www.vistrails.org/index.php/Projects_using_VisTrails Some Projects using VisTrails] ==

{| class="wikitable"
|-
! USGS Habitat modeling
|-
| [[Image:usgs.png|200px|left]]
|
|}

{| class="wikitable"
|-
! NASA Climate Data Analysis
! DOE CDAT
! ALPS Simulations
|-
| [[Image:nasa.png|200px|left]]
| [[Image:cdat.png|200px|left]]
| [[Image:alps-shot.png|200px|left]]
|
|}

{| class="wikitable"
|-
! NSF STC CMOP
! NSF CDI Wildfire
! NSF DataONE-EVA
|-
| [[Image:cmop-ss.png|200px|left]]
| [[Image:wildfire.png|200px|center]]
| [[Image:eva.png|200px|left]]
|
|}
[http://www.vistrails.org/index.php/Projects_using_VisTrails See other projects]

== [[Vistrails and Teaching]] ==

The VisTrails system has been used a tool to teach different courses, including Scientific Visualization and Digital Media.
For more information on the educational uses of VisTrails see [http://www.vistrails.org/index.php/Vistrails_and_Teaching VisTrails and Teaching]. Our [http://www.cs.utah.edu/~juliana/pub/vistrails-teaching-eurographics2010.pdf paper] describing a provenance-rich teaching methodology received the Best Paper Award at the Eurographics 2010 Education program.

== Sponsors ==

This work has been partially supported by the National Science Foundation under grants
[http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0905385 IIS-0905385],
[http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0844572 IIS-0844572],
[http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0746500 IIS CAREER-0746500],
[http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0751152 CNS-0751152],
[http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0513692 IIS-0513692],
[http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0401498 CCF-0401498],
[http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0541560 CNS-0541560], [http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0405402 OISE-0405402],
[http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0424602 OCE-0424602],
[http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0524096 CNS-0524096],
[http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0534628 IIS-0534628],
the Department of Energy under the SciDAC program
([http://www.scidac.org/compsci/SDM.html SDM]
and
[http://www.scidac.org/viz/VACET.html VACET]) and UV-CDAT,
IBM Faculty Awards (2005, 2006, 2007, and 2008) and a University of Utah Seed Grant.

== Related Sites ==

[[BirdVis]]

[http://www.crowdlabs.org CrowdLabs]

[[RepeatabilityCentral]]

[[ProvenanceAnalytics]]

[[Provenance: potpourri]]

Downloads

2016-05-03T14:33:37Z

Tommy: /* Latest Releases */

== Latest Releases ==

The latest stable version is VisTrails v2.2.4. For the the complete list of enhancements and fixes in this release, please see the [https://sourceforge.net/projects/vistrails/files/vistrails/v2.2.4/README/view release notes].

VisTrails is also available on [https://pypi.python.org/pypi/vistrails PyPI] and [https://binstar.org/vida-nyu/vistrails Anaconda].

=== Source, Binaries and Users' Guide ===
====Latest stable release ====
{| {{Prettytable}}
|-
|{{Hl4}} colspan="4" |'''2.2.4 build 1519abc0ae2b (2016-05-03)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.2.4/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.4/vistrails-setup-2.2.4-1519abc0ae2b.zip
|text=vistrails-setup-2.2.4-1519abc0ae2b.zip}}
|179.5 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.4/vistrails-x64-setup-2.2.4-1519abc0ae2b.zip
|text=vistrails-x64-setup-2.2.4-1519abc0ae2b.zip}}
|230.7 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.4/vistrails-osx-2.2.4-1519abc0ae2b.dmg
|text=vistrails-osx-2.2.4-1519abc0ae2b.dmg}}
|303.6 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.4/vistrails-src-2.2.4-1519abc0ae2b.tar.gz
|text=vistrails-src-2.2.4-1519abc0ae2b.tar.gz}}
|22.7 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.4/VisTrails.pdf
|text=VisTrails.pdf}}
|8.9 MB
|all
|.pdf
|-
|}

=== Older releases ===

{| {{Prettytable}}
|-
|{{Hl4}} colspan="4" |'''2.1.5 build 4fe986148829 (2015-03-21)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.1.5/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.5/vistrails-setup-2.1.5-4fe986148829.zip
|text=vistrails-setup-2.1.5-4fe986148829.zip}}
|120.2 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.5/vistrails-x64-setup-2.1.5-4fe986148829.zip
|text=vistrails-x64-setup-2.1.5-4fe986148829.zip}}
|166.1 MB
|x86_64
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.5/vistrails-mac-10.6-intel-2.1.5-4fe986148829.dmg
|text=vistrails-mac-10.6-intel-2.1.5-4fe986148829.dmg}}
|255.4 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.5/vistrails-src-2.1.5-4fe986148829.tar.gz
|text=vistrails-src-2.1.5-4fe986148829.tar.gz}}
|20.6 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.5/VisTrails.pdf
|text=VisTrails.pdf}}
|8.3 MB
|all
|.pdf
|-
|}

{| {{Prettytable}}
|-
|{{Hl4}} colspan="4" |'''1.7 build 51517a6cdab6 (2011-06-30)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=https://sourceforge.net/projects/vistrails/files/vistrails/v1.7/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.7/vistrails-setup-1.7-51517a6cdab6.zip
|text=vistrails-setup-1.7-51517a6cdab6.zip}}
|111.9 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.7/vistrails-mac-10.5-intel-1.7-51517a6cdab6.dmg
|text=vistrails-mac-10.5-intel-1.7-51517a6cdab6.dmg}}
|211.5 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.7/vistrails-src-1.7-51517a6cdab6.tar.gz
|text=vistrails-src-1.7-51517a6cdab6.tar.gz}}
|19 MB
|all
|Source .tar.gz
|-
|}

=== All releases ===
* [[all_releases|All releases]]

=== Nightly build ===
Every night a tarball and installers for windows and mac are generated from the source trunk of vistrails. Beware that these can be very unstable.
{| {{Prettytable}}
|-
|{{Hl4}}|'''Nightly build'''
|{{Hl4}}|'''Size'''
|{{Hl4}}|'''Architecture'''
|{{Hl4}}|'''Type'''
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/nightly/vistrails-src-nightly.tar.gz
|text=vistrails-src-nightly.tar.gz}}
|~20MB
|all
|.tar.gz Source
|-
|
* [http://downloads.sourceforge.net/project/vistrails/vistrails/nightly/vistrails-setup-nightly.exe vistrails-setup-nightly.exe]
|~170MB
|Windows x86
|.exe Windows
|-
|
* [http://downloads.sourceforge.net/project/vistrails/vistrails/nightly/vistrails-x64-setup-nightly.exe vistrails-x64-setup-nightly.exe]
|~120MB
|Windows x64
|.exe Windows
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/nightly/vistrails-mac-10.6-nightly.dmg
|text=vistrails-mac-10.6-nightly.dmg}}
|~250MB
|OSX 10.6+
|.dmg Mac
|-
|}

==== Data files for Examples ====
If you download the source release you might want to download the data files (they are already included in the binary releases). Just decompress the package to the examples folder.

* {{targz
|link=http://www.vistrails.org/download/download.php?id=data.tar.gz
|text=data.tar.gz}}

== Building from Source ==

Instructions are available for [[Building From Source|building VisTrails from source]] for all supported platforms.

==== Ubuntu Packages ====

VisTrails includes integrated support for checking and installing required packages on Ubuntu. See [[InstallingVisTrailsOnUbuntu|installing VisTrails on Ubuntu]] for more information.

==== VisTrails Module Packages ====

VisTrails makes use of packages of Modules to define and form valid workflows. Some packages are maintained and distributed with the VisTrails itself and are considered part of the core functionality. However, work has also been done on developing user-made and maintained Module Packages. Below are a current list of packages maintained by VisTrails and user packages maintained outside the core source repository. The Package Name field describes the name required by the addPackage() directive in the .vistrails/startup.py file required to load the package.

* [[MainVisTrailsPackages | Packages distributed with VisTrails]]
* [[UserContributedPackages | Packages developed by users]]

== Web Services Demos ==

Some Bioinformatics workflows examples are available [[Web_Services_Examples|here]].

== Mailing List ==

Join the VisTrails [[MailingLists|mailing list]] to receive release announcements as well as post questions.

Downloads

2016-05-03T14:32:55Z

Tommy: /* Latest stable release */

== Latest Releases ==

The latest stable version is VisTrails v2.2.3. For the the complete list of enhancements and fixes in this release, please see the [https://sourceforge.net/projects/vistrails/files/vistrails/v2.2.3/README/view release notes].

VisTrails is also available on [https://pypi.python.org/pypi/vistrails PyPI] and [https://binstar.org/vida-nyu/vistrails Anaconda].

=== Source, Binaries and Users' Guide ===
====Latest stable release ====
{| {{Prettytable}}
|-
|{{Hl4}} colspan="4" |'''2.2.4 build 1519abc0ae2b (2016-05-03)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.2.4/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.4/vistrails-setup-2.2.4-1519abc0ae2b.zip
|text=vistrails-setup-2.2.4-1519abc0ae2b.zip}}
|179.5 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.4/vistrails-x64-setup-2.2.4-1519abc0ae2b.zip
|text=vistrails-x64-setup-2.2.4-1519abc0ae2b.zip}}
|230.7 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.4/vistrails-osx-2.2.4-1519abc0ae2b.dmg
|text=vistrails-osx-2.2.4-1519abc0ae2b.dmg}}
|303.6 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.4/vistrails-src-2.2.4-1519abc0ae2b.tar.gz
|text=vistrails-src-2.2.4-1519abc0ae2b.tar.gz}}
|22.7 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.4/VisTrails.pdf
|text=VisTrails.pdf}}
|8.9 MB
|all
|.pdf
|-
|}

=== Older releases ===

{| {{Prettytable}}
|-
|{{Hl4}} colspan="4" |'''2.1.5 build 4fe986148829 (2015-03-21)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.1.5/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.5/vistrails-setup-2.1.5-4fe986148829.zip
|text=vistrails-setup-2.1.5-4fe986148829.zip}}
|120.2 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.5/vistrails-x64-setup-2.1.5-4fe986148829.zip
|text=vistrails-x64-setup-2.1.5-4fe986148829.zip}}
|166.1 MB
|x86_64
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.5/vistrails-mac-10.6-intel-2.1.5-4fe986148829.dmg
|text=vistrails-mac-10.6-intel-2.1.5-4fe986148829.dmg}}
|255.4 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.5/vistrails-src-2.1.5-4fe986148829.tar.gz
|text=vistrails-src-2.1.5-4fe986148829.tar.gz}}
|20.6 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.5/VisTrails.pdf
|text=VisTrails.pdf}}
|8.3 MB
|all
|.pdf
|-
|}

{| {{Prettytable}}
|-
|{{Hl4}} colspan="4" |'''1.7 build 51517a6cdab6 (2011-06-30)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=https://sourceforge.net/projects/vistrails/files/vistrails/v1.7/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.7/vistrails-setup-1.7-51517a6cdab6.zip
|text=vistrails-setup-1.7-51517a6cdab6.zip}}
|111.9 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.7/vistrails-mac-10.5-intel-1.7-51517a6cdab6.dmg
|text=vistrails-mac-10.5-intel-1.7-51517a6cdab6.dmg}}
|211.5 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.7/vistrails-src-1.7-51517a6cdab6.tar.gz
|text=vistrails-src-1.7-51517a6cdab6.tar.gz}}
|19 MB
|all
|Source .tar.gz
|-
|}

=== All releases ===
* [[all_releases|All releases]]

=== Nightly build ===
Every night a tarball and installers for windows and mac are generated from the source trunk of vistrails. Beware that these can be very unstable.
{| {{Prettytable}}
|-
|{{Hl4}}|'''Nightly build'''
|{{Hl4}}|'''Size'''
|{{Hl4}}|'''Architecture'''
|{{Hl4}}|'''Type'''
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/nightly/vistrails-src-nightly.tar.gz
|text=vistrails-src-nightly.tar.gz}}
|~20MB
|all
|.tar.gz Source
|-
|
* [http://downloads.sourceforge.net/project/vistrails/vistrails/nightly/vistrails-setup-nightly.exe vistrails-setup-nightly.exe]
|~170MB
|Windows x86
|.exe Windows
|-
|
* [http://downloads.sourceforge.net/project/vistrails/vistrails/nightly/vistrails-x64-setup-nightly.exe vistrails-x64-setup-nightly.exe]
|~120MB
|Windows x64
|.exe Windows
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/nightly/vistrails-mac-10.6-nightly.dmg
|text=vistrails-mac-10.6-nightly.dmg}}
|~250MB
|OSX 10.6+
|.dmg Mac
|-
|}

==== Data files for Examples ====
If you download the source release you might want to download the data files (they are already included in the binary releases). Just decompress the package to the examples folder.

* {{targz
|link=http://www.vistrails.org/download/download.php?id=data.tar.gz
|text=data.tar.gz}}

== Building from Source ==

Instructions are available for [[Building From Source|building VisTrails from source]] for all supported platforms.

==== Ubuntu Packages ====

VisTrails includes integrated support for checking and installing required packages on Ubuntu. See [[InstallingVisTrailsOnUbuntu|installing VisTrails on Ubuntu]] for more information.

==== VisTrails Module Packages ====

VisTrails makes use of packages of Modules to define and form valid workflows. Some packages are maintained and distributed with the VisTrails itself and are considered part of the core functionality. However, work has also been done on developing user-made and maintained Module Packages. Below are a current list of packages maintained by VisTrails and user packages maintained outside the core source repository. The Package Name field describes the name required by the addPackage() directive in the .vistrails/startup.py file required to load the package.

* [[MainVisTrailsPackages | Packages distributed with VisTrails]]
* [[UserContributedPackages | Packages developed by users]]

== Web Services Demos ==

Some Bioinformatics workflows examples are available [[Web_Services_Examples|here]].

== Mailing List ==

Join the VisTrails [[MailingLists|mailing list]] to receive release announcements as well as post questions.

All releases

2016-05-03T14:30:52Z

Tommy:

{| {{Prettytable}}
|-
|{{Hl3}}|'''Release date'''
|{{Hl3}}|'''Size (bytes)'''
|{{Hl3}}|'''Architecture'''
|{{Hl3}}|'''Type'''
|-
|{{Hl4}} colspan="4" |'''2.2.4 build 1519abc0ae2b (2016-05-03)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.2.4/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.4/vistrails-setup-2.2.4-1519abc0ae2b.zip
|text=vistrails-setup-2.2.4-1519abc0ae2b.zip}}
|179.5 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.4/vistrails-x64-setup-2.2.4-1519abc0ae2b.zip
|text=vistrails-x64-setup-2.2.4-1519abc0ae2b.zip}}
|230.7 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.4/vistrails-osx-2.2.4-1519abc0ae2b.dmg
|text=vistrails-osx-2.2.4-1519abc0ae2b.dmg}}
|303.6 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.4/vistrails-src-2.2.4-1519abc0ae2b.tar.gz
|text=vistrails-src-2.2.4-1519abc0ae2b.tar.gz}}
|22.7 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.4/VisTrails.pdf
|text=VisTrails.pdf}}
|8.9 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.2.3 build 02ad04a622c4 (2015-09-22)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.2.3/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.3/vistrails-setup-2.2.3-02ad04a622c4.zip
|text=vistrails-setup-2.2.3-02ad04a622c4.zip}}
|178.8 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.3/vistrails-x64-setup-2.2.3-02ad04a622c4.zip
|text=vistrails-x64-setup-2.2.3-02ad04a622c4.zip}}
|230.1 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.3/vistrails-mac-10.6-intel-2.2.3-02ad04a622c4.dmg
|text=vistrails-mac-10.6-intel-2.2.3-02ad04a622c4.dmg}}
|307.3 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.3/vistrails-src-2.2.3-02ad04a622c4.tar.gz
|text=vistrails-src-2.2.3-02ad04a622c4.tar.gz}}
|22.7 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.3/VisTrails.pdf
|text=VisTrails.pdf}}
|9.0 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.2.2 build 358e9a9fc33c (2015-07-10)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.2.2/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.2/vistrails-setup-2.2.2-358e9a9fc33c.zip
|text=vistrails-setup-2.2.2-358e9a9fc33c.zip}}
|178.2 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.2/vistrails-x64-setup-2.2.2-358e9a9fc33c.zip
|text=vistrails-x64-setup-2.2.2-358e9a9fc33c.zip}}
|229.6 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.2/vistrails-mac-10.6-intel-2.2.2-358e9a9fc33c.dmg
|text=vistrails-mac-10.6-intel-2.2.2-358e9a9fc33c.dmg}}
|306.7 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.2/vistrails-src-2.2.2-358e9a9fc33c.tar.gz
|text=vistrails-src-2.2.2-358e9a9fc33c.tar.gz}}
|22.6 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.2/VisTrails.pdf
|text=VisTrails.pdf}}
|8.9 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.2 build 422e1a9bbc1c (2015-04-21)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.2/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2/vistrails-setup-2.2-422e1a9bbc1c.zip
|text=vistrails-setup-2.2-422e1a9bbc1c.zip}}
|173.9 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2/vistrails-x64-setup-2.2-422e1a9bbc1c.zip
|text=vistrails-x64-setup-2.2-422e1a9bbc1c.zip}}
|234.6 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2/vistrails-mac-10.6-intel-2.2-422e1a9bbc1c.dmg
|text=vistrails-mac-10.6-intel-2.2-422e1a9bbc1c.dmg}}
|270.2 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2/vistrails-src-2.2-422e1a9bbc1c.tar.gz
|text=vistrails-src-2.2-422e1a9bbc1c.tar.gz}}
|22.3 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2/VisTrails.pdf
|text=VisTrails.pdf}}
|8.9 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.1.5 build 4fe986148829 (2015-03-21)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.1.5/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.5/vistrails-setup-2.1.5-4fe986148829.zip
|text=vistrails-setup-2.1.5-4fe986148829.zip}}
|120.2 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.5/vistrails-x64-setup-2.1.5-4fe986148829.zip
|text=vistrails-x64-setup-2.1.5-4fe986148829.zip}}
|166.1 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.5/vistrails-mac-10.6-intel-2.1.5-4fe986148829.dmg
|text=vistrails-mac-10.6-intel-2.1.5-4fe986148829.dmg}}
|255.4 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.5/vistrails-src-2.1.5-4fe986148829.tar.gz
|text=vistrails-src-2.1.5-4fe986148829.tar.gz}}
|20.6 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.5/VisTrails.pdf
|text=VisTrails.pdf}}
|8.3 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.1.4 build 269e4808eca3 (2014-08-25)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.1.4/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.4/vistrails-setup-2.1.4-269e4808eca3.zip
|text=vistrails-setup-2.1.4-269e4808eca3.zip}}
|116.3 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.4/vistrails-x64-setup-2.1.4-269e4808eca3.zip
|text=vistrails-x64-setup-2.1.4-269e4808eca3.zip}}
|162.1 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.4/vistrails-mac-10.6-intel-2.1.4-269e4808eca3.dmg
|text=vistrails-mac-10.6-intel-2.1.4-269e4808eca3.dmg}}
|251.3 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.4/vistrails-src-2.1.4-269e4808eca3.tar.gz
|text=vistrails-src-2.1.4-269e4808eca3.tar.gz}}
|20.7 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.4/VisTrails.pdf
|text=VisTrails.pdf}}
|8.3 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.1.3 build 8262f078ed3b (2014-07-14)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.1.3/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.3/vistrails-setup-2.1.3-8262f078ed3b.zip
|text=vistrails-setup-2.1.3-8262f078ed3b.zip}}
|116.3 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.3/vistrails-x64-setup-2.1.3-8262f078ed3b.zip
|text=vistrails-x64-setup-2.1.3-8262f078ed3b.zip}}
|162.1 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.3/vistrails-mac-10.6-intel-2.1.3-8262f078ed3b.dmg
|text=vistrails-mac-10.6-intel-2.1.3-8262f078ed3b.dmg}}
|260.1 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.3/vistrails-src-2.1.3-8262f078ed3b.tar.gz
|text=vistrails-src-2.1.3-8262f078ed3b.tar.gz}}
|35.4 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.3/VisTrails.pdf
|text=VisTrails.pdf}}
|8.3 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.1.2 build 7d8a4ed2feeb (2014-05-14)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.1.2/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.2/vistrails-setup-2.1.2-7d8a4ed2feeb.zip
|text=vistrails-setup-2.1.2-7d8a4ed2feeb.zip}}
|130.4 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.2/vistrails-x64-setup-2.1.2-7d8a4ed2feeb.zip
|text=vistrails-x64-setup-2.1.2-7d8a4ed2feeb.zip}}
|176.4 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.2/vistrails-mac-10.6-intel-2.1.2-7d8a4ed2feeb.dmg
|text=vistrails-mac-10.6-intel-2.1.2-7d8a4ed2feeb.dmg}}
|259.4 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.2/vistrails-src-2.1.2-7d8a4ed2feeb.tar.gz
|text=vistrails-src-2.1.2-7d8a4ed2feeb.tar.gz}}
|35.4 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.2/VisTrails.pdf
|text=VisTrails.pdf}}
|8.3 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.1.1 build 90975fc00211 (2014-01-17)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.1.1/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.1/vistrails-setup-2.1.1-90975fc00211.zip
|text=vistrails-setup-2.1.1-90975fc00211.zip}}
|130.7 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.1/vistrails-x64-setup-2.1.1-90975fc00211.zip
|text=vistrails-x64-setup-2.1.1-90975fc00211.zip}}
|179.1 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.1/vistrails-mac-10.6-intel-2.1.1-90975fc00211.dmg
|text=vistrails-mac-10.6-intel-2.1.1-90975fc00211.dmg}}
|256.4 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.1/vistrails-src-2.1.1-90975fc00211.tar.gz
|text=vistrails-src-2.1.1-90975fc00211.tar.gz}}
|37.1 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.1/VisTrails.pdf
|text=VisTrails.pdf}}
|14.4 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.1 build 179c82045907 (2013-12-31)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.1/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1/vistrails-setup-2.1-179c82045907.zip
|text=vistrails-setup-2.1-179c82045907.zip}}
|130.7 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1/vistrails-x64-setup-2.1-179c82045907.zip
|text=vistrails-x64-setup-2.1-179c82045907.zip}}
|179.1 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1/vistrails-mac-10.6-intel-2.1-179c82045907.dmg
|text=vistrails-mac-10.6-intel-2.1-179c82045907.dmg}}
|256.5 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1/vistrails-src-2.1-179c82045907.tar.gz
|text=vistrails-src-2.1-179c82045907.tar.gz}}
|36.9 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1/VisTrails.pdf
|text=VisTrails.pdf}}
|14.2 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.1 beta2 build 99faabb791a0 (2013-09-23)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.1beta2/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1beta2/vistrails-setup-2.1beta2-99faabb791a0.zip
|text=vistrails-setup-2.1-beta2-99faabb791a0.zip}}
|131.9 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1beta2/vistrails-x64-setup-2.1beta2-99faabb791a0.zip
|text=vistrails-x64-setup-2.1beta2-99faabb791a0.zip}}
|177.7 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1beta2/vistrails-mac-10.6-intel-2.1beta2-99faabb791a0.dmg
|text=vistrails-mac-10.6-intel-2.1beta2-99faabb791a0.dmg}}
|251.1 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1beta2/vistrails-src-2.1beta2-99faabb791a0.tar.gz
|text=vistrails-src-2.1beta2-99faabb791a0.tar.gz}}
|36.4 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1beta2/VisTrails.pdf
|text=VisTrails.pdf}}
|14.0 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.1beta build 16ae99d82468 (2013-08-22)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.1beta/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1beta/vistrails-setup-2.1beta-16ae99d82468.zip
|text=vistrails-setup-2.1beta-16ae99d82468.zip}}
|127.3 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1beta/vistrails-x64-setup-2.1beta-16ae99d82468.zip
|text=vistrails-x64-setup-2.1beta-16ae99d82468.zip}}
|172.9 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1beta/vistrails-mac-10.6-intel-2.1beta-16ae99d82468.dmg
|text=vistrails-mac-10.6-intel-2.1beta-16ae99d82468.dmg}}
|251.1 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1beta/vistrails-src-2.1beta-16ae99d82468.tar.gz
|text=vistrails-src-2.1beta-16ae99d82468.tar.gz}}
|36.3 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1beta/VisTrails.pdf
|text=VisTrails.pdf}}
|13.8 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.0.3 build a6ad79347667 (2013-08-05)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.0.3/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.3/vistrails-setup-2.0.3-a6ad79347667.zip
|text=vistrails-setup-2.0.3-a6ad79347667.zip}}
|120.5 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.3/vistrails-x64-setup-2.0.3-a6ad79347667.zip
|text=vistrails-x64-setup-2.0.3-a6ad79347667.zip}}
|166.0 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.3/vistrails-mac-10.6-intel-2.0.3-a6ad79347667.dmg
|text=vistrails-mac-10.6-intel-2.0.3-a6ad79347667.dmg}}
|242.4 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.3/vistrails-src-2.0.3-a6ad79347667.tar.gz
|text=vistrails-src-2.0.3-a6ad79347667.tar.gz}}
|20.7 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.3/VisTrails.pdf
|text=VisTrails.pdf}}
|8.3 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.0.2 build 3813fdd2573b (2013-04-29)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.0.2/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.2/vistrails-setup-2.0.2-3813fdd2573b.zip
|text=vistrails-setup-2.0.2-3813fdd2573b.zip}}
|118.0 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.2/vistrails-x64-setup-2.0.2-3813fdd2573b.zip
|text=vistrails-x64-setup-2.0.2-3813fdd2573b.zip}}
|164.4 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.2/vistrails-mac-10.6-intel-2.0.2-3813fdd2573b.dmg
|text=vistrails-mac-10.6-intel-2.0.2-3813fdd2573b.dmg}}
|233.3 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.2/vistrails-src-2.0.2-3813fdd2573b.tar.gz
|text=vistrails-src-2.0.2-3813fdd2573b.tar.gz}}
|20.1 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.2/VisTrails.pdf
|text=VisTrails.pdf}}
|7.9 MB
|all
|.pdf
|-
|-
|{{Hl4}} colspan="4" |'''2.0.1 build 5e35e2b83b90 (2012-10-03)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.0.1/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.1/vistrails-setup-2.0.1-5e35e2b83b90.zip
|text=vistrails-setup-2.0.1-5e35e2b83b90.zip}}
|125.0 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.1/vistrails-x64-setup-2.0.1-5e35e2b83b90.zip
|text=vistrails-x64-setup-2.0.1-5e35e2b83b90.zip}}
|152.2 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.1/vistrails-mac-10.5-intel-2.0.1-5e35e2b83b90.dmg
|text=vistrails-mac-10.5-intel-2.0.1-5e35e2b83b90.dmg}}
|199 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.1/vistrails-mac-10.6-intel-2.0.1-5e35e2b83b90.dmg
|text=vistrails-mac-10.6-intel-2.0.1-5e35e2b83b90.dmg}}
|232.1 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.1/vistrails-src-2.0.1-5e35e2b83b90.tar.gz
|text=vistrails-src-2.0.1-5e35e2b83b90.tar.gz}}
|19.4 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.1/VisTrails.pdf
|text=VisTrails.pdf}}
|8.8 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.0 build 240bcab5bbcd (2012-05-24)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.0/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0/vistrails-setup-2.0-240bcab5bbcd.zip
|text=vistrails-setup-2.0-240bcab5bbcd.zip}}
|125.3 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0/vistrails-x64-setup-2.0-240bcab5bbcd.zip
|text=vistrails-x64-setup-2.0-240bcab5bbcd.zip}}
|150 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0/vistrails-mac-10.5-intel-2.0-240bcab5bbcd.dmg
|text=vistrails-mac-10.5-intel-2.0-240bcab5bbcd.dmg}}
|198.8 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0/vistrails-mac-10.6-intel-2.0-240bcab5bbcd.dmg
|text=vistrails-mac-10.6-intel-2.0-240bcab5bbcd.dmg}}
|182.3 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0/vistrails-src-2.0-240bcab5bbcd.tar.gz
|text=vistrails-src-2.0-240bcab5bbcd.tar.gz}}
|19.2 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0/VisTrails.pdf
|text=VisTrails.pdf}}
|8.7 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.0-beta build 2d428fbd26cc (2012-04-05)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.0-beta-3/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta-3/vistrails-setup-2.0-beta-2d428fbd26cc.zip
|text=vistrails-setup-2.0-beta-2d428fbd26cc.zip}}
|124.7 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta-3/vistrails-x64-setup-2.0-beta-2d428fbd26cc.zip
|text=vistrails-x64-setup-2.0-beta-2d428fbd26cc.zip}}
|147.7 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta-3/vistrails-mac-10.5-intel-2.0-beta-2d428fbd26cc.dmg
|text=vistrails-mac-10.5-intel-2.0-beta-2d428fbd26cc.dmg}}
|197.7 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta-3/vistrails-mac-10.6-intel-2.0-beta-2d428fbd26cc.dmg
|text=vistrails-mac-10.6-intel-2.0-beta-2d428fbd26cc.dmg}}
|182.1 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta-3/vistrails-src-2.0-beta-2d428fbd26cc.tar.gz
|text=vistrails-src-2.0-beta-2d428fbd26cc.tar.gz}}
|19.2 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta-3/VisTrails.pdf
|text=VisTrails.pdf}}
|8.7 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.0-beta build 10836452c19a (2012-02-29)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.0-beta-2/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta-2/vistrails-setup-2.0-beta-10836452c19a.zip
|text=vistrails-setup-2.0-beta-10836452c19a.zip}}
|124.7 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta-2/vistrails-x64-setup-2.0-beta-10836452c19a.zip
|text=vistrails-x64-setup-2.0-beta-10836452c19a.zip}}
|147.7 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta-2/vistrails-mac-10.5-intel-2.0-beta-10836452c19a.dmg
|text=vistrails-mac-10.5-intel-2.0-beta-10836452c19a.dmg}}
|197.8 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta-2/vistrails-mac-10.6-intel-2.0-beta-10836452c19a.dmg
|text=vistrails-mac-10.6-intel-2.0-beta-10836452c19a.dmg}}
|182.4 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta-2/vistrails-src-2.0-beta-10836452c19a.tar.gz
|text=vistrails-src-2.0-beta-10836452c19a.tar.gz}}
|19.1 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta-2/VisTrails.pdf
|text=VisTrails.pdf}}
|8.7 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.0-beta build b074d3a4eb44 (2012-02-23)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.0-beta/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta/vistrails-setup-2.0-beta-b074d3a4eb44.zip
|text=vistrails-setup-2.0-beta-b074d3a4eb44.zip}}
|124.7 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta/vistrails-x64-setup-2.0-beta-b074d3a4eb44.zip
|text=vistrails-x64-setup-2.0-beta-b074d3a4eb44.zip}}
|147.7 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta/vistrails-mac-10.5-intel-2.0-beta-b074d3a4eb44.dmg
|text=vistrails-mac-10.5-intel-2.0-beta-b074d3a4eb44.dmg}}
|197.8 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta/vistrails-mac-10.6-intel-2.0-beta-b074d3a4eb44.dmg
|text=vistrails-mac-10.6-intel-2.0-beta-b074d3a4eb44.dmg}}
|182.4 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta/vistrails-src-2.0-beta-b074d3a4eb44.tar.gz
|text=vistrails-src-2.0-beta-b074d3a4eb44.tar.gz}}
|19.1 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta/VisTrails.pdf
|text=VisTrails.pdf}}
|8.7 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.0-alpha build c4e3600b6481 (2011-10-12)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.0-alpha-2/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-alpha-2/vistrails-setup-2.0-alpha-c4e3600b6481.zip
|text=vistrails-setup-2.0-alpha-c4e3600b6481.zip}}
|114.6 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-alpha-2/vistrails-x64-setup-2.0-alpha-c4e3600b6481.zip
|text=vistrails-x64-setup-2.0-alpha-c4e3600b6481.zip}}
|137.1 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-alpha-2/vistrails-mac-10.5-intel-2.0-alpha-c4e3600b6481.dmg
|text=vistrails-mac-10.5-intel-2.0-alpha-c4e3600b6481.dmg}}
|197.5 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-alpha-2/vistrails-mac-10.6-intel-2.0-alpha-c4e3600b6481.dmg
|text=vistrails-mac-10.6-intel-2.0-alpha-c4e3600b6481.dmg}}
|181.6 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-alpha-2/vistrails-src-2.0-alpha-c4e3600b6481.tar.gz
|text=vistrails-src-2.0-alpha-c4e3600b6481.tar.gz}}
|18.9 MB
|all
|Source .tar.gz
|-
|{{Hl4}} colspan="4" |'''2.0-alpha build 1b88c3949efd (2011-09-22)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.0-alpha/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-alpha/vistrails-setup-2.0-alpha-1b88c3949efd.zip
|text=vistrails-setup-2.0-alpha-1b88c3949efd.zip}}
|114.6 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-alpha/vistrails-x64-setup-2.0-alpha-1b88c3949efd.zip
|text=vistrails-x64-setup-2.0-alpha-1b88c3949efd.zip}}
|137 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-alpha/vistrails-mac-10.5-intel-2.0-alpha-1b88c3949efd.dmg
|text=vistrails-mac-10.5-intel-2.0-alpha-1b88c3949efd.dmg}}
|197.5 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-alpha/vistrails-mac-10.6-intel-2.0-alpha-1b88c3949efd.dmg
|text=vistrails-mac-10.6-intel-2.0-alpha-1b88c3949efd.dmg}}
|177 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-alpha/vistrails-src-2.0-alpha-1b88c3949efd.tar.gz
|text=vistrails-src-2.0-alpha-1b88c3949efd.tar.gz}}
|18.9 MB
|all
|Source .tar.gz
|-
|{{Hl4}} colspan="4" |'''1.7 build 51517a6cdab6 (2011-06-30)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=https://sourceforge.net/projects/vistrails/files/vistrails/v1.7/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.7/vistrails-setup-1.7-51517a6cdab6.zip
|text=vistrails-setup-1.7-51517a6cdab6.zip}}
|111.9 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.7/vistrails-mac-10.5-intel-1.7-51517a6cdab6.dmg
|text=vistrails-mac-10.5-intel-1.7-51517a6cdab6.dmg}}
|211.5 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.7/vistrails-src-1.7-51517a6cdab6.tar.gz
|text=vistrails-src-1.7-51517a6cdab6.tar.gz}}
|19 MB
|all
|Source .tar.gz
|-
|{{Hl4}} colspan="4" |'''1.6.2 build af4a69ad566a (2011-04-05)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=https://sourceforge.net/projects/vistrails/files/vistrails/v1.6.2/README.txt/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.6.2/vistrails-setup-1.6.2-af4a69ad566a.zip
|text=vistrails-setup-1.6.2-af4a69ad566a.zip}}
|105.7 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.6.2/vistrails-mac-10.5-intel-1.6.2-af4a69ad566a.dmg
|text=vistrails-mac-10.5-intel-1.6.2-af4a69ad566a.dmg}}
|193.3 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.6.2/vistrails-src-1.6.2-af4a69ad566a.tar.gz
|text=vistrails-src-1.6.2-af4a69ad566a.tar.gz}}
|23 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.6.2/VisTrails.pdf
|text=VisTrails.pdf}}
|9.1 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''1.6.1 build ba9616b413d2 (2011-01-20)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=https://sourceforge.net/projects/vistrails/files/vistrails/v1.6.1/README.txt/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.6.1/vistrails-setup-1.6.1-ba9616b413d2.zip
|text=vistrails-setup-1.6.1-ba9616b413d2.zip}}
|96.7 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.6.1/vistrails-mac-10.5-intel-1.6.1-ba9616b413d2.dmg
|text=vistrails-mac-10.5-intel-1.6.1-ba9616b413d2.dmg}}
|183.7 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.6.1/vistrails-src-1.6.1-ba9616b413d2.tar.gz
|text=vistrails-src-1.6.1-ba9616b413d2.tar.gz}}
|12.4 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.6/vistrails-usersguide-1.6-rev215.pdf
|text=vistrails-usersguide-1.6-rev215.pdf}}
|8.9 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''1.6 build e9f97c5908ac (2011-01-07)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=https://sourceforge.net/projects/vistrails/files/vistrails/v1.6/README.txt/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.6/vistrails-setup-1.6-e9f97c5908ac.zip
|text=vistrails-setup-1.6-e9f97c5908ac.zip}}
|96.7 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.6/vistrails-mac-10.5-intel-1.6-e9f97c5908ac.dmg
|text=vistrails-mac-10.5-intel-1.6-e9f97c5908ac.dmg}}
|183.7 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.6/vistrails-src-1.6-e9f97c5908ac.tar.gz
|text=vistrails-src-1.6-e9f97c5908ac.tar.gz}}
|12.4 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.6/vistrails-usersguide-1.6-rev215.pdf
|text=vistrails-usersguide-1.6-rev215.pdf}}
|8.9 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''1.5.1 revision 1863 (2010-08-25)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=https://sourceforge.net/projects/vistrails/files/vistrails/v1.5.1/releaseNotes.txt/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.5.1/vistrails-setup-1.5.1-rev1863.zip
|text=vistrails-setup-1.5.1-rev1863.zip}}
|84.6 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.5.1/vistrails-mac-10.5-intel-1.5.1-rev1863.dmg
|text=vistrails-mac-10.5-intel-1.5.1-rev1863.dmg}}
|172.7 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.5.1/vistrails-src-1.5.1-rev1863.tar.gz
|text=vistrails-src-1.5.1-rev1863.tar.gz}}
|7.9 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://sourceforge.net/projects/vistrails/files/vistrails/vistrails-usersguide-1.3-rev198.pdf
|text=vistrails-usersguide-1.3-rev198.pdf}}
|8.5 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''1.5 revision 1832 (2010-07-12 14:30)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=https://sourceforge.net/projects/vistrails/files/vistrails/v1.5/releaseNotes.txt/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.5/vistrails-setup-1.5-rev1832.zip
|text=vistrails-setup-1.5-rev1832.zip}}
|80.29 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.5/vistrails-mac-10.5-intel-1.5-rev1832.dmg
|text=vistrails-mac-10.5-intel-1.5-rev1832.dmg}}
|168.14 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.5/vistrails-src-1.5-rev1832.tar.gz
|text=vistrails-src-1.5-rev1832.tar.gz}}
|7.12 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://sourceforge.net/projects/vistrails/files/vistrails/vistrails-usersguide-1.3-rev198.pdf
|text=vistrails-usersguide-1.3-rev198.pdf}}
|8.5 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''1.4.2 revision 1736 (2010-03-03 22:30)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=https://sourceforge.net/projects/vistrails/files/vistrails/v1.4.2/releaseNotes.txt/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.4.2/vistrails-setup-1.4.2-rev1736.zip
|text=vistrails-setup-1.4.2-rev1736.zip}}
|98.05 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.4.2/vistrails-mac-10.5-intel-1.4.2-rev1736.dmg
|text=vistrails-mac-10.5-intel-1.4.2-rev1736.dmg}}
|164.37 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.4.2/vistrails-src-1.4.2-rev1736.tar.gz
|text=vistrails-src-1.4.2-rev1736.tar.gz}}
|4.75 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://sourceforge.net/projects/vistrails/files/vistrails/vistrails-usersguide-1.3-rev198.pdf
|text=vistrails-usersguide-1.3-rev198.pdf}}
|8.5 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''1.4.1 revision 1693 (2010-01-28 14:00)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=https://sourceforge.net/projects/vistrails/files/vistrails/v1.4.1/releaseNotes.txt/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.4.1/vistrails-setup-1.4.1-rev1693.zip
|text=vistrails-setup-1.4.1-rev1693.zip}}
|102.8 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.4.1/vistrails-mac-10.5-intel-1.4.1-rev1693.dmg
|text=vistrails-mac-10.5-intel-1.4.1-rev1693.dmg}}
|172.3 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.4.1/vistrails-src-1.4.1-rev1693.tar.gz
|text=vistrails-src-1.4.1-rev1693.tar.gz}}
|5.0 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://sourceforge.net/projects/vistrails/files/vistrails/vistrails-usersguide-1.3-rev198.pdf
|text=vistrails-usersguide-1.3-rev198.pdf}}
|8.5 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''1.4.0 revision 1682 (2010-01-12 12:15)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=https://sourceforge.net/projects/vistrails/files/vistrails/v1.4/releaseNotes.txt/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.4/vistrails-setup-1.4-rev1682.zip
|text=vistrails-setup-1.4-rev1682.zip}}
|102.8 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.4/vistrails-mac-10.5-intel-1.4-rev1682.dmg
|text=vistrails-mac-10.5-intel-1.4-rev1682.dmg}}
|172.3 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.4/vistrails-src-1.4-rev1682.tar.gz
|text=vistrails-src-1.4-rev1682.tar.gz}}
|5.0 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://sourceforge.net/projects/vistrails/files/vistrails/vistrails-usersguide-1.3-rev198.pdf
|text=vistrails-usersguide-1.3-rev198.pdf}}
|8.5 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''1.3.0 revision 1559 (2009-07-03 12:00)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=http://sourceforge.net/project/shownotes.php?group_id=188281&release_id=694515}}
|-
|
* {{zip
|link=http://sourceforge.net/projects/vistrails/files/vistrails/vistrails-setup-1.3-rev1561.zip
|text=vistrails-setup-1.3rev1561.zip}}
|85.2 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://sourceforge.net/projects/vistrails/files/vistrails/vistrails-mac-10.5-intel-1.3-rev1559.dmg
|text=vistrails-mac-10.5-intel-1.3-rev1559.dmg}}
|151.6 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://sourceforge.net/projects/vistrails/files/vistrails/vistrails-src-1.3-rev1559.tar.gz
|text=vistrails-src-1.3-rev1559.tar.gz}}
|4.3 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://sourceforge.net/projects/vistrails/files/vistrails/vistrails-usersguide-1.3-rev198.pdf
|text=vistrails-usersguide-1.3-rev198.pdf}}
|8.5 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''1.2.2 revision 1559 (2009-07-03 12:00)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=http://sourceforge.net/project/shownotes.php?group_id=188281&release_id=694510}}
|-
|
* {{zip
|link=http://sourceforge.net/projects/vistrails/files/vistrails/vistrails-setup-1.2.2rev1559.zip
|text=vistrails-setup-1.2.2rev1559.zip}}
|83.3 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://sourceforge.net/projects/vistrails/files/vistrails/vistrails-mac-10.5-intel-1.2.2-rev1559.dmg
|text=vistrails-mac-10.5-intel-1.2.2-rev1559.dmg}}
|149.6 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://sourceforge.net/projects/vistrails/files/vistrails/vistrails-src-1.2.2-rev1559.tar.gz
|text=vistrails-src-1.2.2-rev1559.tar.gz}}
|2.6 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://sourceforge.net/projects/vistrails/files/vistrails/vistrails-usersguide-1.2.1-rev194.pdf
|text=vistrails-usersguide-1.2.1-rev194.pdf}}
|7.2 MB6
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''1.2.1 revision 1336 (2008-09-12 16:31)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=http://sourceforge.net/project/shownotes.php?release_id=625946&group_id=188281}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/vistrails/vistrails-setup-1.2.1rev1336.zip
|text=vistrails-setup-1.2.1rev1336.zip}}
|103097941
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/vistrails/vistrails-mac-10.5-intel-1.2.1-rev1336.dmg
|text=vistrails-mac-10.5-intel-1.2.1-rev1336.dmg}}
|99743897
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/vistrails/vistrails-mac-10.4-ppc-1.2.1-rev1336.dmg
|text=vistrails-mac-10.4-ppc-1.2.1-rev1336.dmg}}
|112887425
|Mac OS X 10.4+ PPC
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/vistrails/vistrails-src-1.2.1-rev1337.tar.gz
|text=vistrails-src-1.2.1-rev1337.tar.gz}}
|2693391
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/vistrails/vistrails-usersguide-1.2.1-rev194.pdf
|text=vistrails-usersguide-1.2.1-rev194.pdf}}
|7559476
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''1.2 revision 1263 (2008-07-14 22:07)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=http://sourceforge.net/project/shownotes.php?release_id=613557&group_id=188281}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/vistrails/vistrails-setup-1.2rev1263.zip
|text=vistrails-setup-1.2rev1263.zip}}
|102993463
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/vistrails/vistrails-mac-10.4-intel-1.2-rev1263.dmg
|text=vistrails-mac-10.4-intel-1.2-rev1263.dmg}}
|75365217
|Mac OS X 10.4+ x86
|.dmg (Mac bundle)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/vistrails/vistrails-mac-10.4-ppc-1.2-rev1263.dmg
|text=vistrails-mac-10.4-ppc-1.2-rev1263.dmg}}
|83796717
|Mac OS X 10.4+ PPC
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/vistrails/vistrails-src-1.2-rev1263.tar.gz
|text=vistrails-src-1.2-rev1263.tar.gz}}
|2631897
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/vistrails/vistrails-usersguide-1.2-rev191.pdf
|text=vistrails-usersguide-1.2-rev191.pdf}}
|7448866
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''1.1 revision 1143 (2008-05-16 04:00)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=http://sourceforge.net/project/shownotes.php?release_id=599542&group_id=188281}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/vistrails/vistrails-setup-1.1rev1143.zip
|text=vistrails-setup-1.1rev1143.zip}}
|71441727
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/vistrails/vistrails-mac-10.4-intel-1.1-rev1143.dmg
|text=vistrails-mac-10.4-intel-1.1-rev1143.dmg}}
|77722240
|Mac OS X 10.4+ x86
|.dmg (Mac bundle)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/vistrails/vistrails-mac-10.4-ppc-1.1-rev1143.dmg
|text=vistrails-mac-10.4-ppc-1.1-rev1143.dmg}}
|85666619
|Mac OS X 10.4+ PPC
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/vistrails/vistrails-src-1.1-rev1143.tar.gz
|text=vistrails-src-1.1-rev1143.tar.gz}}
|2513281
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/vistrails/vistrails-usersguide-rev119.pdf
|text=vistrails-usersguide-rev119.pdf}}
|5645174
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''1.0.1 revision 1063 (2008-02-04 11:00)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=http://sourceforge.net/project/shownotes.php?group_id=188281&release_id=574150}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/vistrails/vistrails-setup-1.0.1rev1063.zip
|text=vistrails-setup-1.0.1rev1063.zip}}
|76897930
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/vistrails/vistrails-mac-10.4-intel-1.0.1-rev1063.dmg
|text=vistrails-mac-10.4-intel-1.0.1-rev1063.dmg}}
|70667465
|Mac OS X 10.4+ x86
|.dmg (Mac bundle)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/vistrails/vistrails-mac-10.4-ppc-1.0.1-rev1063.dmg
|text=vistrails-mac-10.4-ppc-1.0.1-rev1063.dmg}}
|79972743
|Mac OS X 10.4+ PPC
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/vistrails/vistrails-src-1.0.1-rev1063.tar.gz
|text=vistrails-src-1.0.1-rev1063.tar.gz}}
|1894895
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/vistrails/vistrails-usersguide-rev119.pdf
|text=vistrails-usersguide-rev119.pdf}}
|5645174
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''1.0 revision 1024 (2007-10-30 01:02)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=http://sourceforge.net/project/shownotes.php?release_id=550532&group_id=188281}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/vistrails/vistrails-setup-1.0rev1024.zip
|text=vistrails-setup-1.0rev1024.zip}}
|69230325
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/vistrails/vistrails-mac-intel-bundle-1.0-rev1024.dmg
|text=vistrails-mac-intel-bundle-1.0-rev1024.dmg}}
|71493980
|Mac x86
|.dmg (Mac bundle)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/vistrails/vistrails-mac-ppc-bundle-1.0-rev1024.dmg
|text=vistrails-mac-ppc-bundle-1.0-rev91024.dmg}}
|80206647
|Mac PPC
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/vistrails/vistrails-src-1.0b-rev954.tar.gz
|text=vistrails-src-1.0b-rev954.tar.gz}}
|1823015
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/vistrails/vistrails-usersguide-rev119.pdf
|text=vistrails-usersguide-rev119.pdf}}
|5645174
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''1.0 beta revision 954 (2007-09-20 23:17)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=http://sourceforge.net/project/shownotes.php?release_id=541053&group_id=188281}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/vistrails/vistrails-setup-1.0brev954.zip
|text=vistrails-setup-1.0brev954.zip}}
|68915527
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/vistrails/vistrails-mac-intel-bundle-1.0b-rev954.dmg
|text=vistrails-mac-intel-bundle-1.0b-rev954.dmg}}
|70281100
|Mac x86
|.dmg (Mac bundle)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/vistrails/vistrails-mac-ppc-bundle-1.0b-rev954.dmg
|text=vistrails-mac-ppc-bundle-1.0b-rev954.dmg}}
|80254395
|Mac PPC
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/vistrails/vistrails-src-1.0b-rev954.tar.gz
|text=vistrails-src-1.0b-rev954.tar.gz}}
|1584022
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/vistrails/vistrails-usersguide-rev119.pdf
|text=vistrails-usersguide-rev119.pdf}}
|5645174
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''Revision 674 (2007-04-23 17:00)''' [[known_issues|Known Issues]] {{ReleaseNotes
|rev=674}}
|-
|
* {{zip
|link=http://www.vistrails.org/download/download.php?id=vistrails-setup-rev674.zip
|text=vistrails-setup-rev674.zip}}
|64792987
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://www.vistrails.org/download/download.php?id=vistrails-mac-intel-bundle-rev674.dmg
|text=vistrails-mac-intel-bundle-rev674.dmg}}
|67225726
|Mac x86
|.dmg (Mac bundle)
|-
|
* {{dmg
|link=http://www.vistrails.org/download/download.php?id=vistrails-mac-ppc-bundle-rev674.dmg
|text=vistrails-mac-ppc-bundle-rev674.dmg}}
|60761458
|Mac PPC
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://www.vistrails.org/download/download.php?id=vistrails-src-rev674.tar.gz
|text=vistrails-src-rev674.tar.gz}}
|1116138
|all
|Source .tar.gz
|-
|{{Hl4}} colspan="4" |'''Revision 606 (2007-04-04 01:00)''' {{ReleaseNotes
|rev=606}}
|-
|
* {{zip
|link=http://www.vistrails.org/download/download.php?id=vistrails-setup-rev606.zip
|text=vistrails-setup-rev606.zip}}
|64770646
|i586
|.zip (32-bit Windows)
|-
|
* {{targz
|link=http://www.vistrails.org/download/download.php?id=vistrails-src-rev606.tar.gz
|text=vistrails-src-rev606.tar.gz}}
|1097551
|all
|Source .tar.gz
|-
|{{Hl4}} colspan="4" |'''Revision 559 (2007-03-09 16:00)''' [[known_issues|Known Issues]] {{ReleaseNotes
|rev=559}}
|-
|
* {{zip
|link=http://www.vistrails.org/download/download.php?id=vistrails-setup-rev559.zip
|text=vistrails-setup-rev559.zip}}
|62571080
|i586
|.zip (32-bit Windows)
|-
|
* {{targz
|link=http://www.vistrails.org/download/download.php?id=vistrails-src-rev559.tar.gz
|text=vistrails-src-rev559.tar.gz}}
|941311
|all
|Source .tar.gz
|-
|{{Hl4}} colspan="4" |'''Revision 502 (2007-03-02 19:30)''' {{ReleaseNotes
|rev=502}}
|-
|
* {{zip
|link=http://www.vistrails.org/download/download.php?id=vistrails-setup-rev502.zip
|text=vistrails-setup-rev502.zip}}
|62543626
|i586
|.zip (32-bit Windows)
|-
|
* {{targz
|link=http://www.vistrails.org/download/download.php?id=vistrails-src-rev502.tar.gz
|text=vistrails-src-rev502.tar.gz}}
|922032
|all
|Source .tar.gz
|-
|{{Hl4}} colspan="4" |'''Revision 444 (2007-02-23 18:00)--Last Stable Binary Release''' {{ReleaseNotes
|rev=444}}
|-
|
* {{zip
|link=http://www.vistrails.org/download/download.php?id=vistrails-setup-rev444.zip
|text=vistrails-setup-rev444.zip}}
|62408276
|i586
|.zip (32-bit Windows)
|-
|
* {{targz
|link=http://www.vistrails.org/download/download.php?id=vistrails-src-rev444.tar.gz
|text=vistrails-src-rev444.tar.gz}}
|869346
|all
|Source .tar.gz
|-
|{{Hl4}} colspan="4" |'''Revision 389 (2007-02-09 15:00)''' {{ReleaseNotes
|rev=389}}
|-
|
* {{zip
|link=http://www.vistrails.org/download/download.php?id=vistrails-setup-rev389.zip
|text=vistrails-setup-rev389.zip}}
|42277520
|i586
|.zip (32-bit Windows)
|-
|
* {{targz
|link=http://www.vistrails.org/download/download.php?id=vistrails-src-rev389.tar.gz
|text=vistrails-src-rev389.tar.gz}}
|830470
|all
|Source .tar.gz
|-
|{{Hl4}} colspan="4" |'''Revision 370 (2007-02-03 13:00)''' {{ReleaseNotes
|rev=370}}
|-
|
* {{zip
|link=http://www.vistrails.org/download/download.php?id=vistrails-setup-rev370.zip
|text=vistrails-setup-rev370.zip}}
|41462264
|i586
|.zip (32-bit Windows)
|-
|
* {{targz
|link=http://www.vistrails.org/download/download.php?id=vistrails-src-rev370.tar.gz
|text=vistrails-src-rev370.tar.gz}}
|827902
|all
|Source .tar.gz
|-
|{{Hl4}} colspan="4" |'''Revision 288 (2007-01-26 17:00)''' {{ReleaseNotes
|rev=288}}
|-
|
* {{zip
|link=http://www.vistrails.org/download/download.php?id=vistrails-setup-rev288.zip
|text=vistrails-setup-rev288.zip}}
|41432327
|i586
|.zip (32-bit Windows)
|-
|
* {{targz
|link=http://www.vistrails.org/download/download.php?id=vistrails-src-rev288.tar.gz
|text=vistrails-src-rev288.tar.gz}}
|803897
|all
|Source .tar.gz
|-
|{{Hl4}} colspan="4"|'''Revision 213 (2007-01-12 12:00)'''
|-
|
* {{zip
|link=http://www.vistrails.org/download/download.php?id=vistrails-setup-rev213.zip
|text=vistrails-setup-rev213.zip}}
|41454430
|i586
|.zip (32-bit Windows)
|-
|
* {{targz
|link=http://www.vistrails.org/download/download.php?id=vistrails-src-rev213.tar.gz
|text=vistrails-src-rev213.tar.gz}}
|762510
|all
|Source .tar.gz

|}

All releases

2016-05-03T14:29:13Z

Tommy:

{| {{Prettytable}}
|-
|{{Hl3}}|'''Release date'''
|{{Hl3}}|'''Size (bytes)'''
|{{Hl3}}|'''Architecture'''
|{{Hl3}}|'''Type'''
|-
|{{Hl4}} colspan="4" |'''2.2.4 build 1519abc0ae2b (2016-05-03)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.2.4/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.4/vistrails-setup-2.2.4-1519abc0ae2b.zip
|text=vistrails-setup-2.2.4-1519abc0ae2b.zip}}
|179.5 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.4/vistrails-x64-setup-2.2.4-1519abc0ae2b.zip
|text=vistrails-x64-setup-2.2.4-1519abc0ae2b.zip}}
|230.7 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.4/vistrails-mac-10.6-intel-2.2.4-1519abc0ae2b.dmg
|text=vistrails-mac-10.6-intel-2.2.4-1519abc0ae2b.dmg}}
|303.6 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.4/vistrails-src-2.2.4-1519abc0ae2b.tar.gz
|text=vistrails-src-2.2.4-1519abc0ae2b.tar.gz}}
|22.7 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.4/VisTrails.pdf
|text=VisTrails.pdf}}
|8.9 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.2.3 build 02ad04a622c4 (2015-09-22)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.2.3/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.3/vistrails-setup-2.2.3-02ad04a622c4.zip
|text=vistrails-setup-2.2.3-02ad04a622c4.zip}}
|178.8 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.3/vistrails-x64-setup-2.2.3-02ad04a622c4.zip
|text=vistrails-x64-setup-2.2.3-02ad04a622c4.zip}}
|230.1 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.3/vistrails-mac-10.6-intel-2.2.3-02ad04a622c4.dmg
|text=vistrails-mac-10.6-intel-2.2.3-02ad04a622c4.dmg}}
|307.3 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.3/vistrails-src-2.2.3-02ad04a622c4.tar.gz
|text=vistrails-src-2.2.3-02ad04a622c4.tar.gz}}
|22.7 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.3/VisTrails.pdf
|text=VisTrails.pdf}}
|9.0 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.2.2 build 358e9a9fc33c (2015-07-10)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.2.2/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.2/vistrails-setup-2.2.2-358e9a9fc33c.zip
|text=vistrails-setup-2.2.2-358e9a9fc33c.zip}}
|178.2 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.2/vistrails-x64-setup-2.2.2-358e9a9fc33c.zip
|text=vistrails-x64-setup-2.2.2-358e9a9fc33c.zip}}
|229.6 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.2/vistrails-mac-10.6-intel-2.2.2-358e9a9fc33c.dmg
|text=vistrails-mac-10.6-intel-2.2.2-358e9a9fc33c.dmg}}
|306.7 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.2/vistrails-src-2.2.2-358e9a9fc33c.tar.gz
|text=vistrails-src-2.2.2-358e9a9fc33c.tar.gz}}
|22.6 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2.2/VisTrails.pdf
|text=VisTrails.pdf}}
|8.9 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.2 build 422e1a9bbc1c (2015-04-21)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.2/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2/vistrails-setup-2.2-422e1a9bbc1c.zip
|text=vistrails-setup-2.2-422e1a9bbc1c.zip}}
|173.9 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2/vistrails-x64-setup-2.2-422e1a9bbc1c.zip
|text=vistrails-x64-setup-2.2-422e1a9bbc1c.zip}}
|234.6 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2/vistrails-mac-10.6-intel-2.2-422e1a9bbc1c.dmg
|text=vistrails-mac-10.6-intel-2.2-422e1a9bbc1c.dmg}}
|270.2 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2/vistrails-src-2.2-422e1a9bbc1c.tar.gz
|text=vistrails-src-2.2-422e1a9bbc1c.tar.gz}}
|22.3 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.2/VisTrails.pdf
|text=VisTrails.pdf}}
|8.9 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.1.5 build 4fe986148829 (2015-03-21)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.1.5/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.5/vistrails-setup-2.1.5-4fe986148829.zip
|text=vistrails-setup-2.1.5-4fe986148829.zip}}
|120.2 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.5/vistrails-x64-setup-2.1.5-4fe986148829.zip
|text=vistrails-x64-setup-2.1.5-4fe986148829.zip}}
|166.1 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.5/vistrails-mac-10.6-intel-2.1.5-4fe986148829.dmg
|text=vistrails-mac-10.6-intel-2.1.5-4fe986148829.dmg}}
|255.4 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.5/vistrails-src-2.1.5-4fe986148829.tar.gz
|text=vistrails-src-2.1.5-4fe986148829.tar.gz}}
|20.6 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.5/VisTrails.pdf
|text=VisTrails.pdf}}
|8.3 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.1.4 build 269e4808eca3 (2014-08-25)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.1.4/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.4/vistrails-setup-2.1.4-269e4808eca3.zip
|text=vistrails-setup-2.1.4-269e4808eca3.zip}}
|116.3 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.4/vistrails-x64-setup-2.1.4-269e4808eca3.zip
|text=vistrails-x64-setup-2.1.4-269e4808eca3.zip}}
|162.1 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.4/vistrails-mac-10.6-intel-2.1.4-269e4808eca3.dmg
|text=vistrails-mac-10.6-intel-2.1.4-269e4808eca3.dmg}}
|251.3 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.4/vistrails-src-2.1.4-269e4808eca3.tar.gz
|text=vistrails-src-2.1.4-269e4808eca3.tar.gz}}
|20.7 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.4/VisTrails.pdf
|text=VisTrails.pdf}}
|8.3 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.1.3 build 8262f078ed3b (2014-07-14)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.1.3/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.3/vistrails-setup-2.1.3-8262f078ed3b.zip
|text=vistrails-setup-2.1.3-8262f078ed3b.zip}}
|116.3 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.3/vistrails-x64-setup-2.1.3-8262f078ed3b.zip
|text=vistrails-x64-setup-2.1.3-8262f078ed3b.zip}}
|162.1 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.3/vistrails-mac-10.6-intel-2.1.3-8262f078ed3b.dmg
|text=vistrails-mac-10.6-intel-2.1.3-8262f078ed3b.dmg}}
|260.1 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.3/vistrails-src-2.1.3-8262f078ed3b.tar.gz
|text=vistrails-src-2.1.3-8262f078ed3b.tar.gz}}
|35.4 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.3/VisTrails.pdf
|text=VisTrails.pdf}}
|8.3 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.1.2 build 7d8a4ed2feeb (2014-05-14)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.1.2/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.2/vistrails-setup-2.1.2-7d8a4ed2feeb.zip
|text=vistrails-setup-2.1.2-7d8a4ed2feeb.zip}}
|130.4 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.2/vistrails-x64-setup-2.1.2-7d8a4ed2feeb.zip
|text=vistrails-x64-setup-2.1.2-7d8a4ed2feeb.zip}}
|176.4 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.2/vistrails-mac-10.6-intel-2.1.2-7d8a4ed2feeb.dmg
|text=vistrails-mac-10.6-intel-2.1.2-7d8a4ed2feeb.dmg}}
|259.4 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.2/vistrails-src-2.1.2-7d8a4ed2feeb.tar.gz
|text=vistrails-src-2.1.2-7d8a4ed2feeb.tar.gz}}
|35.4 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.2/VisTrails.pdf
|text=VisTrails.pdf}}
|8.3 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.1.1 build 90975fc00211 (2014-01-17)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.1.1/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.1/vistrails-setup-2.1.1-90975fc00211.zip
|text=vistrails-setup-2.1.1-90975fc00211.zip}}
|130.7 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.1/vistrails-x64-setup-2.1.1-90975fc00211.zip
|text=vistrails-x64-setup-2.1.1-90975fc00211.zip}}
|179.1 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.1/vistrails-mac-10.6-intel-2.1.1-90975fc00211.dmg
|text=vistrails-mac-10.6-intel-2.1.1-90975fc00211.dmg}}
|256.4 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.1/vistrails-src-2.1.1-90975fc00211.tar.gz
|text=vistrails-src-2.1.1-90975fc00211.tar.gz}}
|37.1 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1.1/VisTrails.pdf
|text=VisTrails.pdf}}
|14.4 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.1 build 179c82045907 (2013-12-31)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.1/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1/vistrails-setup-2.1-179c82045907.zip
|text=vistrails-setup-2.1-179c82045907.zip}}
|130.7 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1/vistrails-x64-setup-2.1-179c82045907.zip
|text=vistrails-x64-setup-2.1-179c82045907.zip}}
|179.1 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1/vistrails-mac-10.6-intel-2.1-179c82045907.dmg
|text=vistrails-mac-10.6-intel-2.1-179c82045907.dmg}}
|256.5 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1/vistrails-src-2.1-179c82045907.tar.gz
|text=vistrails-src-2.1-179c82045907.tar.gz}}
|36.9 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1/VisTrails.pdf
|text=VisTrails.pdf}}
|14.2 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.1 beta2 build 99faabb791a0 (2013-09-23)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.1beta2/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1beta2/vistrails-setup-2.1beta2-99faabb791a0.zip
|text=vistrails-setup-2.1-beta2-99faabb791a0.zip}}
|131.9 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1beta2/vistrails-x64-setup-2.1beta2-99faabb791a0.zip
|text=vistrails-x64-setup-2.1beta2-99faabb791a0.zip}}
|177.7 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1beta2/vistrails-mac-10.6-intel-2.1beta2-99faabb791a0.dmg
|text=vistrails-mac-10.6-intel-2.1beta2-99faabb791a0.dmg}}
|251.1 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1beta2/vistrails-src-2.1beta2-99faabb791a0.tar.gz
|text=vistrails-src-2.1beta2-99faabb791a0.tar.gz}}
|36.4 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1beta2/VisTrails.pdf
|text=VisTrails.pdf}}
|14.0 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.1beta build 16ae99d82468 (2013-08-22)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.1beta/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1beta/vistrails-setup-2.1beta-16ae99d82468.zip
|text=vistrails-setup-2.1beta-16ae99d82468.zip}}
|127.3 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1beta/vistrails-x64-setup-2.1beta-16ae99d82468.zip
|text=vistrails-x64-setup-2.1beta-16ae99d82468.zip}}
|172.9 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1beta/vistrails-mac-10.6-intel-2.1beta-16ae99d82468.dmg
|text=vistrails-mac-10.6-intel-2.1beta-16ae99d82468.dmg}}
|251.1 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1beta/vistrails-src-2.1beta-16ae99d82468.tar.gz
|text=vistrails-src-2.1beta-16ae99d82468.tar.gz}}
|36.3 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.1beta/VisTrails.pdf
|text=VisTrails.pdf}}
|13.8 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.0.3 build a6ad79347667 (2013-08-05)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.0.3/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.3/vistrails-setup-2.0.3-a6ad79347667.zip
|text=vistrails-setup-2.0.3-a6ad79347667.zip}}
|120.5 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.3/vistrails-x64-setup-2.0.3-a6ad79347667.zip
|text=vistrails-x64-setup-2.0.3-a6ad79347667.zip}}
|166.0 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.3/vistrails-mac-10.6-intel-2.0.3-a6ad79347667.dmg
|text=vistrails-mac-10.6-intel-2.0.3-a6ad79347667.dmg}}
|242.4 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.3/vistrails-src-2.0.3-a6ad79347667.tar.gz
|text=vistrails-src-2.0.3-a6ad79347667.tar.gz}}
|20.7 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.3/VisTrails.pdf
|text=VisTrails.pdf}}
|8.3 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.0.2 build 3813fdd2573b (2013-04-29)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.0.2/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.2/vistrails-setup-2.0.2-3813fdd2573b.zip
|text=vistrails-setup-2.0.2-3813fdd2573b.zip}}
|118.0 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.2/vistrails-x64-setup-2.0.2-3813fdd2573b.zip
|text=vistrails-x64-setup-2.0.2-3813fdd2573b.zip}}
|164.4 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.2/vistrails-mac-10.6-intel-2.0.2-3813fdd2573b.dmg
|text=vistrails-mac-10.6-intel-2.0.2-3813fdd2573b.dmg}}
|233.3 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.2/vistrails-src-2.0.2-3813fdd2573b.tar.gz
|text=vistrails-src-2.0.2-3813fdd2573b.tar.gz}}
|20.1 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.2/VisTrails.pdf
|text=VisTrails.pdf}}
|7.9 MB
|all
|.pdf
|-
|-
|{{Hl4}} colspan="4" |'''2.0.1 build 5e35e2b83b90 (2012-10-03)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.0.1/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.1/vistrails-setup-2.0.1-5e35e2b83b90.zip
|text=vistrails-setup-2.0.1-5e35e2b83b90.zip}}
|125.0 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.1/vistrails-x64-setup-2.0.1-5e35e2b83b90.zip
|text=vistrails-x64-setup-2.0.1-5e35e2b83b90.zip}}
|152.2 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.1/vistrails-mac-10.5-intel-2.0.1-5e35e2b83b90.dmg
|text=vistrails-mac-10.5-intel-2.0.1-5e35e2b83b90.dmg}}
|199 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.1/vistrails-mac-10.6-intel-2.0.1-5e35e2b83b90.dmg
|text=vistrails-mac-10.6-intel-2.0.1-5e35e2b83b90.dmg}}
|232.1 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.1/vistrails-src-2.0.1-5e35e2b83b90.tar.gz
|text=vistrails-src-2.0.1-5e35e2b83b90.tar.gz}}
|19.4 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0.1/VisTrails.pdf
|text=VisTrails.pdf}}
|8.8 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.0 build 240bcab5bbcd (2012-05-24)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.0/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0/vistrails-setup-2.0-240bcab5bbcd.zip
|text=vistrails-setup-2.0-240bcab5bbcd.zip}}
|125.3 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0/vistrails-x64-setup-2.0-240bcab5bbcd.zip
|text=vistrails-x64-setup-2.0-240bcab5bbcd.zip}}
|150 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0/vistrails-mac-10.5-intel-2.0-240bcab5bbcd.dmg
|text=vistrails-mac-10.5-intel-2.0-240bcab5bbcd.dmg}}
|198.8 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0/vistrails-mac-10.6-intel-2.0-240bcab5bbcd.dmg
|text=vistrails-mac-10.6-intel-2.0-240bcab5bbcd.dmg}}
|182.3 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0/vistrails-src-2.0-240bcab5bbcd.tar.gz
|text=vistrails-src-2.0-240bcab5bbcd.tar.gz}}
|19.2 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0/VisTrails.pdf
|text=VisTrails.pdf}}
|8.7 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.0-beta build 2d428fbd26cc (2012-04-05)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.0-beta-3/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta-3/vistrails-setup-2.0-beta-2d428fbd26cc.zip
|text=vistrails-setup-2.0-beta-2d428fbd26cc.zip}}
|124.7 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta-3/vistrails-x64-setup-2.0-beta-2d428fbd26cc.zip
|text=vistrails-x64-setup-2.0-beta-2d428fbd26cc.zip}}
|147.7 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta-3/vistrails-mac-10.5-intel-2.0-beta-2d428fbd26cc.dmg
|text=vistrails-mac-10.5-intel-2.0-beta-2d428fbd26cc.dmg}}
|197.7 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta-3/vistrails-mac-10.6-intel-2.0-beta-2d428fbd26cc.dmg
|text=vistrails-mac-10.6-intel-2.0-beta-2d428fbd26cc.dmg}}
|182.1 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta-3/vistrails-src-2.0-beta-2d428fbd26cc.tar.gz
|text=vistrails-src-2.0-beta-2d428fbd26cc.tar.gz}}
|19.2 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta-3/VisTrails.pdf
|text=VisTrails.pdf}}
|8.7 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.0-beta build 10836452c19a (2012-02-29)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.0-beta-2/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta-2/vistrails-setup-2.0-beta-10836452c19a.zip
|text=vistrails-setup-2.0-beta-10836452c19a.zip}}
|124.7 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta-2/vistrails-x64-setup-2.0-beta-10836452c19a.zip
|text=vistrails-x64-setup-2.0-beta-10836452c19a.zip}}
|147.7 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta-2/vistrails-mac-10.5-intel-2.0-beta-10836452c19a.dmg
|text=vistrails-mac-10.5-intel-2.0-beta-10836452c19a.dmg}}
|197.8 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta-2/vistrails-mac-10.6-intel-2.0-beta-10836452c19a.dmg
|text=vistrails-mac-10.6-intel-2.0-beta-10836452c19a.dmg}}
|182.4 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta-2/vistrails-src-2.0-beta-10836452c19a.tar.gz
|text=vistrails-src-2.0-beta-10836452c19a.tar.gz}}
|19.1 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta-2/VisTrails.pdf
|text=VisTrails.pdf}}
|8.7 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.0-beta build b074d3a4eb44 (2012-02-23)''' [[known_issues|Known Issues]] {{SFReleaseNotes |link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.0-beta/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta/vistrails-setup-2.0-beta-b074d3a4eb44.zip
|text=vistrails-setup-2.0-beta-b074d3a4eb44.zip}}
|124.7 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta/vistrails-x64-setup-2.0-beta-b074d3a4eb44.zip
|text=vistrails-x64-setup-2.0-beta-b074d3a4eb44.zip}}
|147.7 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta/vistrails-mac-10.5-intel-2.0-beta-b074d3a4eb44.dmg
|text=vistrails-mac-10.5-intel-2.0-beta-b074d3a4eb44.dmg}}
|197.8 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta/vistrails-mac-10.6-intel-2.0-beta-b074d3a4eb44.dmg
|text=vistrails-mac-10.6-intel-2.0-beta-b074d3a4eb44.dmg}}
|182.4 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta/vistrails-src-2.0-beta-b074d3a4eb44.tar.gz
|text=vistrails-src-2.0-beta-b074d3a4eb44.tar.gz}}
|19.1 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-beta/VisTrails.pdf
|text=VisTrails.pdf}}
|8.7 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''2.0-alpha build c4e3600b6481 (2011-10-12)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.0-alpha-2/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-alpha-2/vistrails-setup-2.0-alpha-c4e3600b6481.zip
|text=vistrails-setup-2.0-alpha-c4e3600b6481.zip}}
|114.6 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-alpha-2/vistrails-x64-setup-2.0-alpha-c4e3600b6481.zip
|text=vistrails-x64-setup-2.0-alpha-c4e3600b6481.zip}}
|137.1 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-alpha-2/vistrails-mac-10.5-intel-2.0-alpha-c4e3600b6481.dmg
|text=vistrails-mac-10.5-intel-2.0-alpha-c4e3600b6481.dmg}}
|197.5 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-alpha-2/vistrails-mac-10.6-intel-2.0-alpha-c4e3600b6481.dmg
|text=vistrails-mac-10.6-intel-2.0-alpha-c4e3600b6481.dmg}}
|181.6 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-alpha-2/vistrails-src-2.0-alpha-c4e3600b6481.tar.gz
|text=vistrails-src-2.0-alpha-c4e3600b6481.tar.gz}}
|18.9 MB
|all
|Source .tar.gz
|-
|{{Hl4}} colspan="4" |'''2.0-alpha build 1b88c3949efd (2011-09-22)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=https://sourceforge.net/projects/vistrails/files/vistrails/v2.0-alpha/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-alpha/vistrails-setup-2.0-alpha-1b88c3949efd.zip
|text=vistrails-setup-2.0-alpha-1b88c3949efd.zip}}
|114.6 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-alpha/vistrails-x64-setup-2.0-alpha-1b88c3949efd.zip
|text=vistrails-x64-setup-2.0-alpha-1b88c3949efd.zip}}
|137 MB
|i586
|.zip (64-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-alpha/vistrails-mac-10.5-intel-2.0-alpha-1b88c3949efd.dmg
|text=vistrails-mac-10.5-intel-2.0-alpha-1b88c3949efd.dmg}}
|197.5 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-alpha/vistrails-mac-10.6-intel-2.0-alpha-1b88c3949efd.dmg
|text=vistrails-mac-10.6-intel-2.0-alpha-1b88c3949efd.dmg}}
|177 MB
|Mac OS X 10.6+ x64
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v2.0-alpha/vistrails-src-2.0-alpha-1b88c3949efd.tar.gz
|text=vistrails-src-2.0-alpha-1b88c3949efd.tar.gz}}
|18.9 MB
|all
|Source .tar.gz
|-
|{{Hl4}} colspan="4" |'''1.7 build 51517a6cdab6 (2011-06-30)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=https://sourceforge.net/projects/vistrails/files/vistrails/v1.7/README/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.7/vistrails-setup-1.7-51517a6cdab6.zip
|text=vistrails-setup-1.7-51517a6cdab6.zip}}
|111.9 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.7/vistrails-mac-10.5-intel-1.7-51517a6cdab6.dmg
|text=vistrails-mac-10.5-intel-1.7-51517a6cdab6.dmg}}
|211.5 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.7/vistrails-src-1.7-51517a6cdab6.tar.gz
|text=vistrails-src-1.7-51517a6cdab6.tar.gz}}
|19 MB
|all
|Source .tar.gz
|-
|{{Hl4}} colspan="4" |'''1.6.2 build af4a69ad566a (2011-04-05)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=https://sourceforge.net/projects/vistrails/files/vistrails/v1.6.2/README.txt/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.6.2/vistrails-setup-1.6.2-af4a69ad566a.zip
|text=vistrails-setup-1.6.2-af4a69ad566a.zip}}
|105.7 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.6.2/vistrails-mac-10.5-intel-1.6.2-af4a69ad566a.dmg
|text=vistrails-mac-10.5-intel-1.6.2-af4a69ad566a.dmg}}
|193.3 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.6.2/vistrails-src-1.6.2-af4a69ad566a.tar.gz
|text=vistrails-src-1.6.2-af4a69ad566a.tar.gz}}
|23 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.6.2/VisTrails.pdf
|text=VisTrails.pdf}}
|9.1 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''1.6.1 build ba9616b413d2 (2011-01-20)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=https://sourceforge.net/projects/vistrails/files/vistrails/v1.6.1/README.txt/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.6.1/vistrails-setup-1.6.1-ba9616b413d2.zip
|text=vistrails-setup-1.6.1-ba9616b413d2.zip}}
|96.7 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.6.1/vistrails-mac-10.5-intel-1.6.1-ba9616b413d2.dmg
|text=vistrails-mac-10.5-intel-1.6.1-ba9616b413d2.dmg}}
|183.7 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.6.1/vistrails-src-1.6.1-ba9616b413d2.tar.gz
|text=vistrails-src-1.6.1-ba9616b413d2.tar.gz}}
|12.4 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.6/vistrails-usersguide-1.6-rev215.pdf
|text=vistrails-usersguide-1.6-rev215.pdf}}
|8.9 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''1.6 build e9f97c5908ac (2011-01-07)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=https://sourceforge.net/projects/vistrails/files/vistrails/v1.6/README.txt/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.6/vistrails-setup-1.6-e9f97c5908ac.zip
|text=vistrails-setup-1.6-e9f97c5908ac.zip}}
|96.7 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.6/vistrails-mac-10.5-intel-1.6-e9f97c5908ac.dmg
|text=vistrails-mac-10.5-intel-1.6-e9f97c5908ac.dmg}}
|183.7 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.6/vistrails-src-1.6-e9f97c5908ac.tar.gz
|text=vistrails-src-1.6-e9f97c5908ac.tar.gz}}
|12.4 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.6/vistrails-usersguide-1.6-rev215.pdf
|text=vistrails-usersguide-1.6-rev215.pdf}}
|8.9 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''1.5.1 revision 1863 (2010-08-25)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=https://sourceforge.net/projects/vistrails/files/vistrails/v1.5.1/releaseNotes.txt/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.5.1/vistrails-setup-1.5.1-rev1863.zip
|text=vistrails-setup-1.5.1-rev1863.zip}}
|84.6 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.5.1/vistrails-mac-10.5-intel-1.5.1-rev1863.dmg
|text=vistrails-mac-10.5-intel-1.5.1-rev1863.dmg}}
|172.7 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.5.1/vistrails-src-1.5.1-rev1863.tar.gz
|text=vistrails-src-1.5.1-rev1863.tar.gz}}
|7.9 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://sourceforge.net/projects/vistrails/files/vistrails/vistrails-usersguide-1.3-rev198.pdf
|text=vistrails-usersguide-1.3-rev198.pdf}}
|8.5 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''1.5 revision 1832 (2010-07-12 14:30)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=https://sourceforge.net/projects/vistrails/files/vistrails/v1.5/releaseNotes.txt/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.5/vistrails-setup-1.5-rev1832.zip
|text=vistrails-setup-1.5-rev1832.zip}}
|80.29 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.5/vistrails-mac-10.5-intel-1.5-rev1832.dmg
|text=vistrails-mac-10.5-intel-1.5-rev1832.dmg}}
|168.14 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.5/vistrails-src-1.5-rev1832.tar.gz
|text=vistrails-src-1.5-rev1832.tar.gz}}
|7.12 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://sourceforge.net/projects/vistrails/files/vistrails/vistrails-usersguide-1.3-rev198.pdf
|text=vistrails-usersguide-1.3-rev198.pdf}}
|8.5 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''1.4.2 revision 1736 (2010-03-03 22:30)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=https://sourceforge.net/projects/vistrails/files/vistrails/v1.4.2/releaseNotes.txt/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.4.2/vistrails-setup-1.4.2-rev1736.zip
|text=vistrails-setup-1.4.2-rev1736.zip}}
|98.05 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.4.2/vistrails-mac-10.5-intel-1.4.2-rev1736.dmg
|text=vistrails-mac-10.5-intel-1.4.2-rev1736.dmg}}
|164.37 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.4.2/vistrails-src-1.4.2-rev1736.tar.gz
|text=vistrails-src-1.4.2-rev1736.tar.gz}}
|4.75 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://sourceforge.net/projects/vistrails/files/vistrails/vistrails-usersguide-1.3-rev198.pdf
|text=vistrails-usersguide-1.3-rev198.pdf}}
|8.5 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''1.4.1 revision 1693 (2010-01-28 14:00)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=https://sourceforge.net/projects/vistrails/files/vistrails/v1.4.1/releaseNotes.txt/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.4.1/vistrails-setup-1.4.1-rev1693.zip
|text=vistrails-setup-1.4.1-rev1693.zip}}
|102.8 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.4.1/vistrails-mac-10.5-intel-1.4.1-rev1693.dmg
|text=vistrails-mac-10.5-intel-1.4.1-rev1693.dmg}}
|172.3 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.4.1/vistrails-src-1.4.1-rev1693.tar.gz
|text=vistrails-src-1.4.1-rev1693.tar.gz}}
|5.0 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://sourceforge.net/projects/vistrails/files/vistrails/vistrails-usersguide-1.3-rev198.pdf
|text=vistrails-usersguide-1.3-rev198.pdf}}
|8.5 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''1.4.0 revision 1682 (2010-01-12 12:15)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=https://sourceforge.net/projects/vistrails/files/vistrails/v1.4/releaseNotes.txt/view}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.4/vistrails-setup-1.4-rev1682.zip
|text=vistrails-setup-1.4-rev1682.zip}}
|102.8 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.4/vistrails-mac-10.5-intel-1.4-rev1682.dmg
|text=vistrails-mac-10.5-intel-1.4-rev1682.dmg}}
|172.3 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/project/vistrails/vistrails/v1.4/vistrails-src-1.4-rev1682.tar.gz
|text=vistrails-src-1.4-rev1682.tar.gz}}
|5.0 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://sourceforge.net/projects/vistrails/files/vistrails/vistrails-usersguide-1.3-rev198.pdf
|text=vistrails-usersguide-1.3-rev198.pdf}}
|8.5 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''1.3.0 revision 1559 (2009-07-03 12:00)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=http://sourceforge.net/project/shownotes.php?group_id=188281&release_id=694515}}
|-
|
* {{zip
|link=http://sourceforge.net/projects/vistrails/files/vistrails/vistrails-setup-1.3-rev1561.zip
|text=vistrails-setup-1.3rev1561.zip}}
|85.2 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://sourceforge.net/projects/vistrails/files/vistrails/vistrails-mac-10.5-intel-1.3-rev1559.dmg
|text=vistrails-mac-10.5-intel-1.3-rev1559.dmg}}
|151.6 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://sourceforge.net/projects/vistrails/files/vistrails/vistrails-src-1.3-rev1559.tar.gz
|text=vistrails-src-1.3-rev1559.tar.gz}}
|4.3 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://sourceforge.net/projects/vistrails/files/vistrails/vistrails-usersguide-1.3-rev198.pdf
|text=vistrails-usersguide-1.3-rev198.pdf}}
|8.5 MB
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''1.2.2 revision 1559 (2009-07-03 12:00)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=http://sourceforge.net/project/shownotes.php?group_id=188281&release_id=694510}}
|-
|
* {{zip
|link=http://sourceforge.net/projects/vistrails/files/vistrails/vistrails-setup-1.2.2rev1559.zip
|text=vistrails-setup-1.2.2rev1559.zip}}
|83.3 MB
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://sourceforge.net/projects/vistrails/files/vistrails/vistrails-mac-10.5-intel-1.2.2-rev1559.dmg
|text=vistrails-mac-10.5-intel-1.2.2-rev1559.dmg}}
|149.6 MB
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://sourceforge.net/projects/vistrails/files/vistrails/vistrails-src-1.2.2-rev1559.tar.gz
|text=vistrails-src-1.2.2-rev1559.tar.gz}}
|2.6 MB
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://sourceforge.net/projects/vistrails/files/vistrails/vistrails-usersguide-1.2.1-rev194.pdf
|text=vistrails-usersguide-1.2.1-rev194.pdf}}
|7.2 MB6
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''1.2.1 revision 1336 (2008-09-12 16:31)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=http://sourceforge.net/project/shownotes.php?release_id=625946&group_id=188281}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/vistrails/vistrails-setup-1.2.1rev1336.zip
|text=vistrails-setup-1.2.1rev1336.zip}}
|103097941
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/vistrails/vistrails-mac-10.5-intel-1.2.1-rev1336.dmg
|text=vistrails-mac-10.5-intel-1.2.1-rev1336.dmg}}
|99743897
|Mac OS X 10.5+ x86
|.dmg (Mac bundle)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/vistrails/vistrails-mac-10.4-ppc-1.2.1-rev1336.dmg
|text=vistrails-mac-10.4-ppc-1.2.1-rev1336.dmg}}
|112887425
|Mac OS X 10.4+ PPC
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/vistrails/vistrails-src-1.2.1-rev1337.tar.gz
|text=vistrails-src-1.2.1-rev1337.tar.gz}}
|2693391
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/vistrails/vistrails-usersguide-1.2.1-rev194.pdf
|text=vistrails-usersguide-1.2.1-rev194.pdf}}
|7559476
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''1.2 revision 1263 (2008-07-14 22:07)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=http://sourceforge.net/project/shownotes.php?release_id=613557&group_id=188281}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/vistrails/vistrails-setup-1.2rev1263.zip
|text=vistrails-setup-1.2rev1263.zip}}
|102993463
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/vistrails/vistrails-mac-10.4-intel-1.2-rev1263.dmg
|text=vistrails-mac-10.4-intel-1.2-rev1263.dmg}}
|75365217
|Mac OS X 10.4+ x86
|.dmg (Mac bundle)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/vistrails/vistrails-mac-10.4-ppc-1.2-rev1263.dmg
|text=vistrails-mac-10.4-ppc-1.2-rev1263.dmg}}
|83796717
|Mac OS X 10.4+ PPC
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/vistrails/vistrails-src-1.2-rev1263.tar.gz
|text=vistrails-src-1.2-rev1263.tar.gz}}
|2631897
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/vistrails/vistrails-usersguide-1.2-rev191.pdf
|text=vistrails-usersguide-1.2-rev191.pdf}}
|7448866
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''1.1 revision 1143 (2008-05-16 04:00)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=http://sourceforge.net/project/shownotes.php?release_id=599542&group_id=188281}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/vistrails/vistrails-setup-1.1rev1143.zip
|text=vistrails-setup-1.1rev1143.zip}}
|71441727
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/vistrails/vistrails-mac-10.4-intel-1.1-rev1143.dmg
|text=vistrails-mac-10.4-intel-1.1-rev1143.dmg}}
|77722240
|Mac OS X 10.4+ x86
|.dmg (Mac bundle)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/vistrails/vistrails-mac-10.4-ppc-1.1-rev1143.dmg
|text=vistrails-mac-10.4-ppc-1.1-rev1143.dmg}}
|85666619
|Mac OS X 10.4+ PPC
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/vistrails/vistrails-src-1.1-rev1143.tar.gz
|text=vistrails-src-1.1-rev1143.tar.gz}}
|2513281
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/vistrails/vistrails-usersguide-rev119.pdf
|text=vistrails-usersguide-rev119.pdf}}
|5645174
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''1.0.1 revision 1063 (2008-02-04 11:00)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=http://sourceforge.net/project/shownotes.php?group_id=188281&release_id=574150}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/vistrails/vistrails-setup-1.0.1rev1063.zip
|text=vistrails-setup-1.0.1rev1063.zip}}
|76897930
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/vistrails/vistrails-mac-10.4-intel-1.0.1-rev1063.dmg
|text=vistrails-mac-10.4-intel-1.0.1-rev1063.dmg}}
|70667465
|Mac OS X 10.4+ x86
|.dmg (Mac bundle)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/vistrails/vistrails-mac-10.4-ppc-1.0.1-rev1063.dmg
|text=vistrails-mac-10.4-ppc-1.0.1-rev1063.dmg}}
|79972743
|Mac OS X 10.4+ PPC
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/vistrails/vistrails-src-1.0.1-rev1063.tar.gz
|text=vistrails-src-1.0.1-rev1063.tar.gz}}
|1894895
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/vistrails/vistrails-usersguide-rev119.pdf
|text=vistrails-usersguide-rev119.pdf}}
|5645174
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''1.0 revision 1024 (2007-10-30 01:02)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=http://sourceforge.net/project/shownotes.php?release_id=550532&group_id=188281}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/vistrails/vistrails-setup-1.0rev1024.zip
|text=vistrails-setup-1.0rev1024.zip}}
|69230325
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/vistrails/vistrails-mac-intel-bundle-1.0-rev1024.dmg
|text=vistrails-mac-intel-bundle-1.0-rev1024.dmg}}
|71493980
|Mac x86
|.dmg (Mac bundle)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/vistrails/vistrails-mac-ppc-bundle-1.0-rev1024.dmg
|text=vistrails-mac-ppc-bundle-1.0-rev91024.dmg}}
|80206647
|Mac PPC
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/vistrails/vistrails-src-1.0b-rev954.tar.gz
|text=vistrails-src-1.0b-rev954.tar.gz}}
|1823015
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/vistrails/vistrails-usersguide-rev119.pdf
|text=vistrails-usersguide-rev119.pdf}}
|5645174
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''1.0 beta revision 954 (2007-09-20 23:17)''' [[known_issues|Known Issues]] {{SFReleaseNotes
|link=http://sourceforge.net/project/shownotes.php?release_id=541053&group_id=188281}}
|-
|
* {{zip
|link=http://downloads.sourceforge.net/vistrails/vistrails-setup-1.0brev954.zip
|text=vistrails-setup-1.0brev954.zip}}
|68915527
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/vistrails/vistrails-mac-intel-bundle-1.0b-rev954.dmg
|text=vistrails-mac-intel-bundle-1.0b-rev954.dmg}}
|70281100
|Mac x86
|.dmg (Mac bundle)
|-
|
* {{dmg
|link=http://downloads.sourceforge.net/vistrails/vistrails-mac-ppc-bundle-1.0b-rev954.dmg
|text=vistrails-mac-ppc-bundle-1.0b-rev954.dmg}}
|80254395
|Mac PPC
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://downloads.sourceforge.net/vistrails/vistrails-src-1.0b-rev954.tar.gz
|text=vistrails-src-1.0b-rev954.tar.gz}}
|1584022
|all
|Source .tar.gz
|-
|
* {{Pdf
|link=http://downloads.sourceforge.net/vistrails/vistrails-usersguide-rev119.pdf
|text=vistrails-usersguide-rev119.pdf}}
|5645174
|all
|.pdf
|-
|{{Hl4}} colspan="4" |'''Revision 674 (2007-04-23 17:00)''' [[known_issues|Known Issues]] {{ReleaseNotes
|rev=674}}
|-
|
* {{zip
|link=http://www.vistrails.org/download/download.php?id=vistrails-setup-rev674.zip
|text=vistrails-setup-rev674.zip}}
|64792987
|i586
|.zip (32-bit Windows)
|-
|
* {{dmg
|link=http://www.vistrails.org/download/download.php?id=vistrails-mac-intel-bundle-rev674.dmg
|text=vistrails-mac-intel-bundle-rev674.dmg}}
|67225726
|Mac x86
|.dmg (Mac bundle)
|-
|
* {{dmg
|link=http://www.vistrails.org/download/download.php?id=vistrails-mac-ppc-bundle-rev674.dmg
|text=vistrails-mac-ppc-bundle-rev674.dmg}}
|60761458
|Mac PPC
|.dmg (Mac bundle)
|-
|
* {{targz
|link=http://www.vistrails.org/download/download.php?id=vistrails-src-rev674.tar.gz
|text=vistrails-src-rev674.tar.gz}}
|1116138
|all
|Source .tar.gz
|-
|{{Hl4}} colspan="4" |'''Revision 606 (2007-04-04 01:00)''' {{ReleaseNotes
|rev=606}}
|-
|
* {{zip
|link=http://www.vistrails.org/download/download.php?id=vistrails-setup-rev606.zip
|text=vistrails-setup-rev606.zip}}
|64770646
|i586
|.zip (32-bit Windows)
|-
|
* {{targz
|link=http://www.vistrails.org/download/download.php?id=vistrails-src-rev606.tar.gz
|text=vistrails-src-rev606.tar.gz}}
|1097551
|all
|Source .tar.gz
|-
|{{Hl4}} colspan="4" |'''Revision 559 (2007-03-09 16:00)''' [[known_issues|Known Issues]] {{ReleaseNotes
|rev=559}}
|-
|
* {{zip
|link=http://www.vistrails.org/download/download.php?id=vistrails-setup-rev559.zip
|text=vistrails-setup-rev559.zip}}
|62571080
|i586
|.zip (32-bit Windows)
|-
|
* {{targz
|link=http://www.vistrails.org/download/download.php?id=vistrails-src-rev559.tar.gz
|text=vistrails-src-rev559.tar.gz}}
|941311
|all
|Source .tar.gz
|-
|{{Hl4}} colspan="4" |'''Revision 502 (2007-03-02 19:30)''' {{ReleaseNotes
|rev=502}}
|-
|
* {{zip
|link=http://www.vistrails.org/download/download.php?id=vistrails-setup-rev502.zip
|text=vistrails-setup-rev502.zip}}
|62543626
|i586
|.zip (32-bit Windows)
|-
|
* {{targz
|link=http://www.vistrails.org/download/download.php?id=vistrails-src-rev502.tar.gz
|text=vistrails-src-rev502.tar.gz}}
|922032
|all
|Source .tar.gz
|-
|{{Hl4}} colspan="4" |'''Revision 444 (2007-02-23 18:00)--Last Stable Binary Release''' {{ReleaseNotes
|rev=444}}
|-
|
* {{zip
|link=http://www.vistrails.org/download/download.php?id=vistrails-setup-rev444.zip
|text=vistrails-setup-rev444.zip}}
|62408276
|i586
|.zip (32-bit Windows)
|-
|
* {{targz
|link=http://www.vistrails.org/download/download.php?id=vistrails-src-rev444.tar.gz
|text=vistrails-src-rev444.tar.gz}}
|869346
|all
|Source .tar.gz
|-
|{{Hl4}} colspan="4" |'''Revision 389 (2007-02-09 15:00)''' {{ReleaseNotes
|rev=389}}
|-
|
* {{zip
|link=http://www.vistrails.org/download/download.php?id=vistrails-setup-rev389.zip
|text=vistrails-setup-rev389.zip}}
|42277520
|i586
|.zip (32-bit Windows)
|-
|
* {{targz
|link=http://www.vistrails.org/download/download.php?id=vistrails-src-rev389.tar.gz
|text=vistrails-src-rev389.tar.gz}}
|830470
|all
|Source .tar.gz
|-
|{{Hl4}} colspan="4" |'''Revision 370 (2007-02-03 13:00)''' {{ReleaseNotes
|rev=370}}
|-
|
* {{zip
|link=http://www.vistrails.org/download/download.php?id=vistrails-setup-rev370.zip
|text=vistrails-setup-rev370.zip}}
|41462264
|i586
|.zip (32-bit Windows)
|-
|
* {{targz
|link=http://www.vistrails.org/download/download.php?id=vistrails-src-rev370.tar.gz
|text=vistrails-src-rev370.tar.gz}}
|827902
|all
|Source .tar.gz
|-
|{{Hl4}} colspan="4" |'''Revision 288 (2007-01-26 17:00)''' {{ReleaseNotes
|rev=288}}
|-
|
* {{zip
|link=http://www.vistrails.org/download/download.php?id=vistrails-setup-rev288.zip
|text=vistrails-setup-rev288.zip}}
|41432327
|i586
|.zip (32-bit Windows)
|-
|
* {{targz
|link=http://www.vistrails.org/download/download.php?id=vistrails-src-rev288.tar.gz
|text=vistrails-src-rev288.tar.gz}}
|803897
|all
|Source .tar.gz
|-
|{{Hl4}} colspan="4"|'''Revision 213 (2007-01-12 12:00)'''
|-
|
* {{zip
|link=http://www.vistrails.org/download/download.php?id=vistrails-setup-rev213.zip
|text=vistrails-setup-rev213.zip}}
|41454430
|i586
|.zip (32-bit Windows)
|-
|
* {{targz
|link=http://www.vistrails.org/download/download.php?id=vistrails-src-rev213.tar.gz
|text=vistrails-src-rev213.tar.gz}}
|762510
|all
|Source .tar.gz

|}

Development

2016-04-27T14:56:23Z

Tommy: /* April 27, 2016 */

<div class="nonumtoc toclimit-1">
__TOC__
</div>

See also the [https://github.com/VisTrails/VisTrails/wiki/Development Github wiki]

== 2016 ==

=== April 27, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Wrapping Bokeh
** New method type "operation"
*** Transforms Figure->Glyph->Output into Glyph->Figure->Output
**** Glyph sets function name and arguments as output
***** Not serializable, but should always be computed together with the subject of the operation.
**** Figure applies Glyph operation on itself
*** Useful for matplotlib?
**** matplotlib currently find actors by searching upstream?
**** But this is more difficult since matplotlib is not function-based.
** New "union" port type
*** Turns "x(float), x(list)" into "x (float, list)" and uses first set value
**** Uses only first value in tuple
**** Bokeh have many properties that support (list, string, Float)
*** Does not work with depth=1 types (e.g. Float of depth 1)
**** Turn Depth 1 types with known type into lists?

* [TE] New bugfix release
** Finalize survey

=== April 20, 2016 ===
'''Updates'''
* Merged upgrade fixes
** Now has infinite loop test
** loop test now correctly loops 5 times
*** remap_module used wrong (current) package version when creating ModuleDescriptor
* Fixed multi-step group upgrades (PR: [https://github.com/VisTrails/VisTrails/issues/1168 #1168])

'''Items to Discuss'''
* New bugfix release
** Merge usagestats
** Need to finalize survey

=== April 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Chaining upgrades done ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Replace "Upgrade" description annotation with "upgraded_from" annotation to identify which tags to hide?

* [TE] Iterating handle_invalid_pipeline ([https://github.com/VisTrails/VisTrails/pull/1165 #1165])
** Not based on [https://github.com/VisTrails/VisTrails/tree/chain-upgrades-loop chain-upgrades-loop]
** Cherry-pick test to preserve source?
** Need maxPipelineFixAttempts option?
*** The code is now smarter about recursion, so max attempts will "probably" never be reached.
** Need [https://github.com/VisTrails/VisTrails/commit/0ef0667426937eddb1d1c1e397f0657ffec039a9 debug messages]?
*** Would need to be moved into handle_invalid_pipeline

=== April 6, 2016 ===
'''Updates'''
* [TE] Query View improvements
** Done except for displaying "Version Info" and #1164
* [RR] Working on finishing new interpreter (finally!)

'''Items to Discuss'''
* [TE] Chaining upgrades ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Try latest upgrade first, then previous.
** If all fail, select latest upgrade?

=== March 30, 2016 ===
'''Updates'''

'''Items to Discuss'''

* [TE] Query View improvements
** Unified do_version_switch and get_upgrades as validate_version()
** Problems with query view using its own controller
*** Fixed module info not being displayed for query results
*** Still no version info for query results
*** Still an issue with version query view not being updated

=== March 23, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Usage reporting almost ready to go
** Need to record whether specific features are used: paramexpore, mashup, query
*** [DK] Record if LaTeX extension is used? But hard to distinguish from direct batch invocation
** How to record size of vistrail?
*** [DK] IdScope already walks over vistrail, use that
*** but total number of modules and versions doesn't give an idea of average size of individual pipelines

=== March 16, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Upgrades in Query Mode
** Now using code similar to do_version_switch
*** Uses handle_invalid_pipeline
*** Differences: Not using current_pipeline, flushes changes
*** New controller method get_pipeline optimized using cached pipelines (but not current_pipeline)
*** Integrate to avoid repeated code?
*** Use this for query mode?
* [TE] VisTrails 2.2.4 ready for release?
** tej package updated. Others?
* [JF] upgrades and the version tree
* [JF] provenance in Jupyter
* [DK] bundles: [https://github.com/VisTrails/VisTrails/pull/1092 #1092]

=== March 9, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixing search mode
** String query now matches all by default
*** This caused pipeline queries to never match
** String query can search: User/Notes/Tagname/Time/Module name
*** Should we search module names by default? (Disabled by default because it is expensive)
*** Fixed notes search
** '>' parameter queries in documentation but has been removed
** Fixed module matches for upgraded pipelines (By not upgrading pipeline)
*** Upgrades still a problem
*** Add "Upgrade all menu option?" (Or upgrade all on open when `hideUpgrades`)
*** [JF] Allow search on past tags

* [TE] Create new bugfix release
** Finish querying
** Path issue on windows

* [DK] Look into sqlalchemy and new bundle branches

=== March 2, 2016 ===
'''Updates'''
* [TE] Fixed cache bug with port specs
* [TE] VisTrails Next
** Most packages now work
** No qgis for Python 3

'''Items to Discuss'''
** Always dereference symlinks? [https://github.com/VisTrails/VisTrails/issues/1146 #1146]

=== February 23, 2016 ===
'''Updates'''
* [TE] Fixed PythonSource 100% CPU bug
* [TE] VisTrails Next
** Updated [http://opendap.co-ops.nos.noaa.gov/axis/webservices/wind/ NOAA Web Service] examples
*** Now uses REST service, tabledata, and Google Maps
*** Web Service replaced with DownloadFile

'''Items to Discuss'''
* [RR] Couple of fixes are in for API, and tej&reprounzip on the Mac binary. Also new release of tej, and working on anonymous usage reports.
** New 2.2 release soon?
* [RR] Anonymous usage reports
** Sends out info like number of modules & versions, packages used, Python & libs versions, execution time, specific features [https://github.com/VisTrails/VisTrails/pull/1154 #1154]
* [JF] Bring in noWorkflow to track variable dependencies, for the considered Jupyter integration?
* noWorkflow - provenance for python scripts
** Recent work on tracking dependencies
* Also integrates ReproZip with Jupyter
** [http://mybinder.org mybinder]
*** Use with ReproZip to automatically build Jupyter notebook interfaces
* Daves comments on Jupyter integration
** It is possible to identify cell order on the server side
** Not trivial to track order of cells on client side
* How does Galaxy workflows relate to VisTrails?
** Packaging in Galaxy is hard
** Galaxy for biomedical workflows, difficulty making it general
* Action items
** How difficult to track cell dependencies in Jupyter notebooks?
** Use noWorkflow to track cell dependencies?
** How difficult to modify mybinder to use ReproZip packages?

=== February 17, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixed Group memory usage
** Modules in groups are supposed to be freed when done executing
*** Prevented by logger that stored references to the modules (fixed, now using id(module))
*** Prevented by list iterator bug that stored list of modules on the 'self' port bug (fixed)
* [TE] VisTrails Next
** Removed deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** PythonSources will be upgraded
*** Fixes for Python < 3
*** fixes for VTK < 6
** TODOs
*** Remove RemoteQ
**** Port Hadoop to tej (Already have pbs)
*** Merge package wrapper
*** Finish SQLAlchemy branch
*** Finish new bundle branch
** [JF] Will contact Jeff and Matthias about moving to Python 3
* [JF] Query by Example is broken
* [JF] VisTrails Data Cleaning Project
** Use VisTrails to process and explore task-specific data while keeping provenance.
** Remi's Idea
*** Use VisTrails as the backend in a Jupyter notebook
*** Overcome problems with executing cells in random order
**** Interesting research topic, but little interest has yet been noted
*** Interesting to study how such a notebook would be used (Is there notebook usage data available?)
*** Impose restrictions to notebook cell boundaries
*** It will only work for functional operations
*** Can we fix, or detect, non-functional (mutating) operations?
*** Analyse code and data flow and see if it mutates data in unexpected ways?
*** Mutable operations can be created in many ways in Python
* Next meeting Tuesday 11:30

=== February 10, 2016 ===
'''Updates'''

'''Items to Discuss'''
* VisTrails Next
** Test suite passes
*** Python 3 less deterministic, module upgrade order random.
** [RR] updating packages: Reprounzip (pushed), tej, persistent_archive, ...
** All of our packages should run fine :)
** VTK thumbnail comparison works
*** Rendering bug on some systems
**** QVTKCell now inherits QGLWidget
*** Old thumbnails had wrong height due to spreadsheetwindow being too small
**** Fixed by regenerating thumbnails
*** Silenced deprecation messages when generating modules
*** Many new classes in VTK 7
** Remove deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** Will break existing PythonSources
**** Try to upgrade?
*** Old-style packages
**** Or only allow a new style, like __init__.py renamed to info.py? (merge with identifiers.py?)
***** Read info.py without importing package?
*** Fixes for Python < 3
*** Fixes for Qt < 5
*** fixes for VTK < 7
*** Remove self port?

=== February 3, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] [http://lists.vistrails.org/pipermail/vistrails-users/2016-January/000402.html Rendering a .pvd (ParaView) file?]

* VisTrails Next
** All tests but thumbnail comparison passes
** Still issues with gui and more packages needs to be tested
** PythonSource and MplSource upgraded with lib2to3
** Keep contrib packages? Update?
** [https://blog.kitware.com/vtk-7-0-0/ VTK 7 is released]
*** Supports Python 3
*** Will hopefully get into conda and others soon
*** Deprecates a bunch of modules

* [https://travis-ci.org/VisTrails/VisTrails/builds/106743348 Travis builder] for VisTrails Next
** Runs!
** Uses conda
*** Many levels of requirements
**** apt packages
**** conda packages
**** python packages in requirements.txt
**** python packages in setup.py
*** Can probably drop conda. Default builder does not have Qt5, but beta builder do!
*** But useful if we want to use conda in our own build process.
** Lots of errors I do not get locally?

* [http://goo.gl/forms/Z4HBrwaBWL User Survey]
** Have you used any alternatives to vistrails?
*** Relevant? More options?
** How often do you use any of these particular features in VisTrails?
*** Add/Remove alternatives?
** How important would you rank the following potential improvements to VisTrails?
*** Add alternatives?

=== January 27, 2016 ===
'''Updates'''
* New interpreter
** Working prototype soon
** Looping not completely done (and port combination mode: pairwise/cartesian...)
** Need to integrate with VisTrails
*** Compatibility with existing modules
*** Use log controller
*** Want to cache at multiple levels (whole stream/single element of stream)
*** Non-runtime attributes of modules (cache check, automatic conversion check, constant from/to string)

'''Items to Discuss'''
* User Survey

* ZMQ failing on windows (vistrails-users)

* [TE] [https://github.com/VisTrails/VisTrails/pull/1143 Python 3 branch]
** Testsuite almost passes
*** Failing are unicode filenames, some users guide examples, and thumbnail comparisons.
** Fixed issues
*** Signatures are now bytes (convert to string to show in widget)
*** Cannot compare different types, e.g., (None < 1)
**** PortSpec.depth and min/maxConn could be None. (Backport!)
**** cell.row could be None
*** Lots of unicode/bytes fixes to serializations
**** We have encryption implementations in the code! (keychain)
*** Lots of small fixes to package method differences
** Current issues
*** logging widget empty?
*** version tree signals messed up
*** provenance view legend icons black
*** Text do not fit in some widgets
*** VTK thumbnail comparison fails
**** VTK Cells have some faces in wrong direction?
**** Because running in VM?
** Installing on Ubuntu LTS/Latest Mint
*** Install latest matplotlib from pip
*** Install VTK 7.0.0rc2 from source
*** No QtWebEngine binary (controversial) (Must install sip/PyQt5/Qt5 from source)

=== January 20, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Backporting features from Python 3 + PyQt5 + Qt5
** Merged unicode with master ([https://github.com/VisTrails/VisTrails/tree/unicode unicode])
*** One unicode test failing
*** Problem saving to xml
** Used [http://python-future.org/ python-future] to run futurize stage 1 to update legacy (pre 2.6) code ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized unicode-futurized])
*** Updates print to functions 'from __future__ import print_function'
*** Updates exception calls to use 'as'
*** removes most usages of 'long' (mostly used unnecessarily)
**** Only needed for 32-bit support
*** Fixes relative imports (from __future__ import absolute_import)
** Fixing code that is deprecated in Qt 4.8 and removed in Qt 5 ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized-qt5 unicode-futurized-qt5])
*** Updated all signals to new-style
* If we go 2 to 3, this could break packages
** means we should schedule any package format changes for the same time
** e.g., imports should be unrelated to code path (function to load module from package identifier?) (take them out of vistrails.* [https://github.com/VisTrails/VisTrails/pull/1002 #1002])
** any structural changes (e.g. the __init__ versus init thing) (RR thinks it makes sense, though having both named "init" is unfortunate)
** putting package identifier as xml?
*** Python not so bad, plus some stuff in there is Python code (checking dependencies)
** version the APIs?
*** RR planning on versioning vistrails_module.Module, no point versioning the whole package?
* file formats on 2 to 3:
** no real translation/upgrade, but non-ascii values that work on 3 won't load in 2

=== January 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://gist.github.com/rexissimus/dfd27e466427529c385c Porting to Python 3 / PyQt5]
** Basic GUI and execution works
** Minimal work to support 2to3
** Hard to support both PyQt4 and PyQt5

=== January 6, 2016 ===
'''Updates'''
'''Items to Discuss'''
* Updating VisTrails dependencies
** Successfully built [https://gist.github.com/rexissimus/f1a1aada7de1c00a57c7 Win7-64/Python3/PyQt5/Qt5/WebEngine/VTK7]
*** VTK 7 is the first supporting Python 3 but is only in release candidate phase.
**** Next version of VTK 6 is rumored to support Python 3
**** There is a development branch of VTK 6 supporting Python 3
*** Can travis build this?
**** We can skip tests for WebEngine and VTK if needed
** Python 3 [https://python3wos.appspot.com/ showstoppers]
*** No MySQL-python (sqlalchemy supports mysql through other drivers)
*** No suds (there are active forks but we could also drop support?)
* Options for python2/3 support:
** Interpreter could be python2/python3 based on packages
** six layer works but not the easiest to maintain (e.g. in reprozip)
* Drop support for win-64
* Update copyright headers to 2016

== 2015 ==

=== December 30, 2015 ===
'''Updates'''
* Bokeh package finished
** Can output to Browser/IPython/Spreadsheet (Limited functionality in spreadsheet)
'''Items to Discuss'''
* Updating VisTrails dependencies
** Bokeh needs QWebEngine (Chromium) in Qt5 which requires PyQt5
*** Many plotting libraries only work in browsers
*** But Chromium may be a big and controversial dependency
*** Or create a browser version of the spreadsheet?
** Some users have requested Python 3
** Not backwards compatible?
** Target for VisTrails 3.0 with new interpreter?

=== December 16, 2015 ===
'''Updates'''
'''Items to Discuss'''
* Users list question
* [TE] Wrapping Bokeh
** Added bokeh property parser
*** complements numpydoc parser
*** Not all attributes are available, partially because I am using a pre-release version.
** Wrapped modules
*** bokeh.plotting finished (Backwards like matplotlib: Create plot then draw on it)
*** bokeh.charts mostly done (Missing arguments)
** QWebView mostly works (but no zooming or buttons)
*** It would be better to use external browser or QWebEngineView
** Added improvements to wrapper
*** Generalized port translations (Color/Path to native types)
*** Can use multiple docstring/property parsers simultaneously

=== December 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Looking into wrapper
** Will port TensorFlow
** Doing a pass on the wrapper code & doc
*** UX improvements
** Factorize high-level docstring parsers into core.wrapper? (sphinx, numpy, google)
** Problem with name vs module_name (fails sklearn tests because class_by_name() is broken)
** Looking into compressing specs, lazy registration of modules

=== December 2, 2015 ===
'''Updates'''
* [TE] Package wrapping
** Wrapped most of numpy/scipy using __all__
** Added class attribute and method access for classes (Can add to class or to separate inspector module)
** TODO: Document wrapping procedure

'''Items to Discuss'''

=== November 25, 2015 ===
'''Updates'''
* [RR] New interpreter is coming along
** Everything is a stream
** Task system, eventually work-stealing parallelism
** Streams no longer advance in lock-step
*** Allows for constructions like filter, join, sorted-merge
** depth>1 still to be tested, no current plan to allow this through the module interface
*** Through looping though, can do streams of streams

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapped most numpy functions (no polynomials)
** and half of scipy classes and functions
** Added functions manually from documentation (no parseable lists?)
** Focusing on data flow constructs (no property/method access for classes)
*** Using spec diff (empty for now) and dynamic parser (stores spec in .vistrails/)
** Python class/function wrapper now stable
** Add google doc parser?
*** Is there a parser available?

=== November 18, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Numpy class wrapping works
*** Basic type is List, since most types are array_likes.
*** TODO: More classes and functions
*** Some operations are in-place and some aren't, and docstring not super clear
*** [RR] It seems only methods mutate, and most have a numpy.xx function equivalent; just manually go through the methods and remove the mutating ones?
** Class wrapper is modular
*** Docstring parser and type string parser can be customized
*** Classes can have optional attribute/method ports
**** Inspectors and attribute/method modules can be created separately
** Use PythonCalc as an example
*** Can be re-implemented as a function with a parseable docstring
*** [RR] PythonCalc is just an example, and it might actually make sense to get rid of it, or do a proper math package with scalar operations (as separate modules, no combobox)
** [RR] TensorFlow to use wrapping as well
*** Very simple (only types 'tensor' & 'variable')

=== November 11, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapping numpy's classes using numpydoc (ndarray)
*** Wrapping constructor arguments, attribute getters/setters as module ports
**** Then how to access attributes afterwards?
***** Use input value port to class modules?
*** Wrap methods as modules? E.g., `ndarray.shape`.
*** Function wrapping is almost a subset of class wrapping
**** May be able to use the same parsing/execution methods
** VTK's non-getter/setter methods could be wrapped as modules
*** We could then remove extra logic in interpreter for keeping function order
** Bokeh uses autogenerated docstrings
*** We may be able to read the specification directly

* [RR] [https://github.com/VisTrails/VisTrails/pull/1138 TensorFlow package]
** Basic setup working, can execute the Mandelbrot example
** Will autogenerate the operations

=== November 4, 2015 ===
'''Updates'''
* [RR] Interpreter work requires a fix for [https://github.com/VisTrails/VisTrails/issues/1137 DB issue #1137]
* [DK] Kitware's Resonant [http://www.kitware.com/source/home/post/173]
** [https://github.com/girder/girder Girder]: data management system
** [https://github.com/Kitware/romanesco Romanesco]: execution engine, uses [http://www.celeryproject.org/ Celery] for task management
** Resonant Flow: web app for editing and executing workflows

'''Items to Discuss'''
* [TE] Added OSX Lion (10.7) VM on build machine using vagrant (seems ok with license?)
** New builds works on Lion
** Change the minimum requirement to 10.7?
* [TE] Package wrapping
* Added upgrade suggestions using 2 spec versions ([http://pastebin.com/30XUU8Gp example])
** using name edit distance to find matches
** Could use something better like port similarity for modules, and type similarity for ports
** Should write python upgrade code?
** Added spec to sklearn package
*** Can now diff spec versions and keep the spec static
*** There will be problems with downgrades and package versions

=== October 29, 2015 ===
'''Updates'''
* [TE] nightly-build-mac fixed (Needed to approve xcode license)

'''Items to Discuss'''
* [TE] matplotlib wrapper
** ported to general spec
** Diff can be used on general spec
*** Only needed minor changes
*** Fixed indexing bug that corrupted specs
*** Can now move diff tools to core/wrapper
** Add new plots?
*** New plots in mpl 1.3: eventplot
*** New plots in mpl 1.4: angle_spectrum, magnitude_spectrum, phase_spectrum', violinplot
*** No new plots in mpl 1.5 (from looking at boilerplate.py)

=== October 21, 2015 ===
'''Updates'''
* [RR] Alexis has arrived, will be working with [RR] on a more efficient interpreter

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package]
** Supporting multiple package versions
*** Check which version can be loaded [https://github.com/VisTrails/VisTrails/pull/1135 #1135]
*** We cannot show version requirements in the list of packages because old packages are loaded when importing the codepath
** Visual diff does not work well, but we can use the spec differ to see differences.
** Unifying vtk and matplotlib wrapping specs (WIP)
*** And porting matplotlibs spec differ to work on the general spec
*** Spec differ can then be used on vtk and other packages in the future
*** Will enable automatic upgrade generation
* [RR] Rework interpreter
** restore abstraction between interpreter/module code
** build looping, streaming, caching into the interpreter
** rework cache
** look into parallelism once basic functionality is there

=== October 14, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package] (adding numpydoc parser)

=== October 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/tree/fix-matplotlib-parser New matplotlib parser] (adding numpydoc parser)
** Added numpydoc attribute parser for plots.
*** TODO: Need better port spec reconciliation with call signature parser.
*** We can create a general numpydoc parser, but attribute types are unique to matplotlib.
** Needs package versioning
*** New spec will not support matplotlib < v1.4 due to changed path to axes classes.
*** Load spec version corresponding to installed matplotlib version?
*** Need version downgrades?

=== September 30, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Updating Matplotlib parser
** Matplotlib docstring parser fails on numpy docstrings
** I have [https://github.com/VisTrails/VisTrails/commit/eae8b0c16260810587e47c41cab53552cbb3cf0a added basic numpydoc parsing]
*** Only used by a few docstrings so far
*** Parsing uses many sources (class tables, signatures, ACCEPTS, method docstrings, definition parsing).
** Caswell said they were thinking about moving to traitlets, but this is not ready yet

=== September 23, 2015 ===
'''Updates'''
* [TE] VisTrails 2.2.3 released
** Also have pushed to PyPI, binstar, etc.
** Sourceforge vs. GitHub
*** should be able to host releases on GitHub
*** nightly binaries pushed to sf each night
*** old binaries?
* [TE] Re-wrapping MatPlotlib
** Keep static generation - Docstrings are brittle beween matplotlib versions
** Keep generating the executable classes - but create functions, not vistrails Modules
*** Why is there so much patching?
** Re-implemented Alternate PortSpec for InputPortSpec
*** It will now inherit specs from parent (No need to reimplement)
** Module upgrades?

'''Items to Discuss'''

=== September 16, 2015 ===
'''Updates'''
* [TE] Job Monitor tests and documentation done
** OK to leave document package in packages directory?

'''Items to Discuss'''
* [TE] Library wrapping: How to do code patching? [https://docs.google.com/drawings/d/1Sh3eOXot6v2y880jHKQrqXqAwr-0aoqYligg3z8G8MY/edit?usp=sharing Wrapping diagram]
** Insert code into module template (Old VTK code)
** Patch the library that is called (New VTK code)
** Somehow store code in spec and apply when executed?
*** Executed code needs at a minimum access to inputs, outputs, current class
*** Use standard input/output dict and obj reference that the code operates on?
*** Can this be done while keeping the execution abstract?

* Do new release now?

=== September 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* New release?
** [RR] wants reprounzip
** tej changes & doc
** job monitor & jobmixin fixes
** mongodb
** reprounzip
** warning: MplFigure type is int
** tabledata: add Reshape, DictoToTable & ListToTable, fix ListToTable with numpy arrays
** PythonSource can have same name for an input & output
** don't show spreadsheet at exit

=== September 2, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Limit autosaves? [https://github.com/VisTrails/VisTrails/pull/1126 #1126]

=== August 26, 2015 ===
'''Updates'''
* [TE] Added Job support to Parameter Explorations (Requested by Colin), and Mashups
** specify job ids, need to specify different ids for parameter explorations since they have the same version id
** how to deal with parameters passed in on command line
* [General] provenance: should be creating a new version when we execute workflow with changed parameters?
** currently, custom_params annotation stores this in provenance currently
** [RR] API doesn't record provenance if passing in parameters: http://git.io/vsAA5
'''Items to Discuss'''

=== August 19, 2015 ===
'''Updates'''
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [TE] Working on Job Monitor documentation

'''Items to Discuss'''
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [TE] Stop testing VisTrails 2.0?

=== August 12, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Build broken on Travis; because of IPython 4 released today? ([https://travis-ci.org/VisTrails/VisTrails/builds/75279795 build 992]; [https://github.com/VisTrails/VisTrails/issues/1123 #1123])

=== August 5, 2015 ===
'''Updates'''
* [TE] Fixes to Jobs
** Could not delete jobs
** Could not run job in group
** Job not reset when calling ModuleSuspended
** Added deleting job from context menu
* [RR] Writing documentation for everything [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

'''Items to Discuss'''

=== July 29, 2015 ===
'''Updates'''
* RR still looking into new interpreter thing
** Goal is to take out scheduling logic from Module so it can be split in multiple processes, and so that smarter strategies can be added in time
** This means some work on packages
** Spreadsheet can live in kernel process? Still some UI stuff that will take work (changing configuration, persistent archive's viewer, ...)
* [TE] Problems running examples [https://github.com/VisTrails/VisTrails/pull/1111 #1111]
** Testing of more examples requires additional packages on the test machines.
** Fixed faulty line-ending in PythonSource:s failing on Python 2.6.
** Test suite now testing SUDSWebServices (If web service is down, test suite will fail)
** preferences.py test failed reloading 'dialogs' package, switched to using 'URL'.

'''Items to Discuss'''

=== July 22, 2015 ===
'''Updates'''
* [TE] mailing lists back online
* [TE] Working on [https://github.com/VisTrails/VisTrails/issues/1107 #1107]
* [RR] Working on ReproZip package

'''Items to Discuss'''
* [RR] MongoDB package [https://github.com/VisTrails/VisTrails/pull/1106 #1106]
* [RR] Example for tej docs? [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

=== July 15, 2015 ===
'''Updates'''
* 2.2.2 released

'''Items to Discuss'''
* RR is considering executing everything in an IPython kernel (i.e. separate Python interpreter, like the one spawned for a notebook)
** It's a separate process that we can restart without restarting the app/gui
** We can isolate the execution environment (e.g. for the server)
** We can run the whole thing remotely (if your data is elsewhere, just run VisTrails locally and the pipeline elsewhere)
** Pipeline execution no longer makes the interface hang, it just makes the kernel hang (but that's fine)
** We can use notebooks as modules (probably way nicer than the PythonSource module)
** We can run multiple kernels so long as the ports carry things that are serializable
*** meaning we can put the multithreaded-interpreter without all the hacky parts it has now
*** we can run IPython kernels in all the languages IPython supports, [https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages currently 46]

=== July 8, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Buildbot github hook not working after IP address change
* [TE] No reference to VistrailsApplication ([https://github.com/VisTrails/VisTrails/issues/1103 #1103])
** [RR] Added PR [https://github.com/VisTrails/VisTrails/pull/1104 #1104]
* [TE] Reopening VT file after saving with bundled subworkflow won't offer subworkflow upgrade ([https://github.com/VisTrails/VisTrails/issues/1102 #1102])
** allow manual delete to fix right now
** fix this on top of the use-uuid branch
* [TE] Release VisTrails 2.2.1? ([https://github.com/VisTrails/VisTrails/blob/v2.2/CHANGELOG CHANGELOG])
** [https://github.com/VisTrails/VisTrails/pull/1093 output-modules-use-global-dir]
** [https://github.com/VisTrails/VisTrails/milestones/version%202.2 Current issues for 2.2]

=== July 1, 2015 ===
'''Updates'''
* [TE] PROV fixed
* [TE] Working on subworkflow issues
* [RR] Considering reworking the controller (log vs exception problem, retained upgrades causing interferences) and also the interpreter (IPython?)

'''Items to Discuss'''

=== June 24, 2015 ===
'''Updates'''

'''Items to Discuss'''
* UV-CDAT
* [TE] Can a cyclic workflow be valid? ([https://github.com/VisTrails/VisTrails/issues/1097 #1097])
** focus on disabling the ability to create cyclic pipelines because more things break than just this with a cyclic pipeline
* [RR] Relative paths ([https://github.com/VisTrails/VisTrails/pull/1057 #1057])
** This interacts with the new bundle; how do handle packing files inside the VT bundle?

=== June 17, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] current_version and reusing existing upgrades are broken ([https://github.com/VisTrails/VisTrails/issues/1095 ticket #1095])
** Could be that export to PROV is using an unflushed upgrade pipeline?
** current_version would then be correct.
** It may work to flush the actions before exporting?

=== June 10, 2015 ===
'''Updates'''
* DAT: fixed VTK issue on Linux and Mac
* Still crashes on Windows. Need help! Reminder: this works in the VisTrails spreadsheet (QCellPresenter), although no widget get changed there during a drag
** Is it a VTK bug?
** Is it simply impossible to change widgets during the drag, should we do it a different way?
** Did I miss something that is done in VisTrails but somehow not in DAT?
** Low prio, UV-CDAT doesn't run on Windows anyway

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 Updated pull request])
* Single instance code and batch mode

=== June 3, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 pr])
** Requires fixes to command line parameters, Output modules, and batch mode
** How to test this
** Updated missing/outdated flags
** Fixed view issues when generating graphs
* [TE] batch mode
** SpreadsheetOutput not enabled in batch mode. Should we check is_running_gui instead?
** Other instance setting flags from caller
** Is graphsAsPdf replacing spreadsheetDumpPdf?
** graphsAsPdf true by Default?
** Batch mode executing by default (Not needed when generating graphs)
** Re-added workflowInfo as withWorkflowInfo for writing graph and xml workflow
** [DK] batch mode should be outputting to files or stdout, shouldn't always trigger SpreadsheetMode
** execute flag, maybe make execution the default and allow a "--no-execute" if you only want to capture graphs, for example

=== May 27, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] API question
** http://lists.vistrails.org/pipermail/vistrails-users/2015-May/000357.html
* Status of DAT
** Can add VCS plot to DAT but need to work on configuration windows
** Documentation for graphics templates for UV-CDAT/vcs?
* Qt support?

=== May 20, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Reviving the DAT, integrating scripting & porting UV-CDAT!
** On [https://github.com/VisTrails/DAT GitHub] ([https://github.com/VisTrails/DAT/issues issues])
** Merging 2 years of development taking longer than expected, but getting there. The plan is to get the patches in VisTrails and never fork again, we never want to get in UV-CDAT's situation (and don't need to).
** VTK cell works fine on Linux but there was flickering on Mac & Windows before; still issues on Mac (Windows status unknown)
** Can get a VCS plot soon (but will need VTK cell fix)
** Integrate in UV-CDAT's build system (so we have cdms, VCS, ...) -> RR can do this, low priority
** How do we integrate scripting?
*** We want to be able to seamlessly make changes to a plot by changing Python code
*** Define new plots by entering Python code without writing modules/packages?
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 13, 2015 ===
'''Updates'''
* [RR] Test skipping whitelist ([https://github.com/VisTrails/VisTrails/pull/1069 #1069]) -- low priority
* [RR] Custom matplotlib modules can't be compatible with both 2.1 and 2.2 ([https://github.com/VisTrails/VisTrails/issues/1067 #1067]); should be fixed for ALPS ([https://github.com/VisTrails/VisTrails/issues/1070 #1070])

'''Items to Discuss'''
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 7, 2015 ===
'''Updates'''
* [RR] Export/import workflow to Python working!

'''Items to Discuss'''
* [Claudio] UV-CDAT
** The UV-CDAT project is the biggest user base of VisTrails
** VisTrails package management provides a lot of friction towards people plugging in their code
** Need to make it easy to integrate your random Python scripts in the system without having to deal with all the boilerplate, at least in the first step
** [RR] argues that modules are still good; UV-CDAT shouldn't move towards a purely script-based backend
** [RR] export/import with Python could reduce a lot of that friction by allowing 1) to edit workflow as Python 2) to open up boxes automatically if needed code doesn't match actual modules
** ...

=== April 29, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] <strike>Abstractions</strike> subworkflows status ([https://github.com/VisTrails/VisTrails/labels/subworkflows tickets])
* [RR] matplotlib compatibility (2.1 & 2.2), [https://github.com/VisTrails/VisTrails/issues/1067 #1067]
** RR to try and fix ALPS matplotlib modules

=== April 22, 2015 ===
'''Updates'''
* 2.2.0 has been released!
* Windows issue (via email from Ryan)
** issue with manifest file (may be a new file in VTK6?)
** Tommy has regenerated new Windows builds
* Binaries, pypi, and conda released
* [RR] Export as script
* Python sources using VTK need to switch to SetInputData (users should be aware of this)

=== April 15, 2015 ===
'''Updates'''
* Ready for 2.2.0 (apart from binary/deps issues)
** Missing some libs (scikit-learn, tej, tdparser, SQLAlchemy+connectors
** Windows: runvistrails.py is no longer used, so the PATH is wrong
** Windows: pip is broken, but it probably wouldn't work anyway because of permission issues (disable this?)
* Queries, upgrades and getPipeline() usage ([https://github.com/VisTrails/VisTrails/issues/1054 #1054])
** Getting a pipeline with getPipeline() is not safe: it might return an invalid pipeline
** This is used in many places throughout the code, like queries
** Upgrading would require going through the controller, but that creates new actions
* [TC] Avoid copying a module's output if it's used as input by exactly one downstream module ([https://github.com/VisTrails/VisTrails/issues/1060 #1060]) (useful for big numpy arrays you can update in-place)

=== April 8, 2015 ===
'''Updates'''
* [DK] Merged RR's changes for output modules (1012 and 1013)
** RR will merge remaining changes, then create v2.2 branch!

'''Items to Discuss'''
* BNL need numpy array to VTK image
** Looks like VTK has some helpers for this
** We will help if issues arise
** Will contribute back to VisTrails package
* Upgrade issue: [https://github.com/VisTrails/VisTrails/issues/1017 #1017]
** Automatic upgrades should happen between versions of provided upgrades
** Our existing upgrades work around this so it doesn't need to be 2.2.0
* Corner-case VTK modules
** No longer need VTKCell input port, so don't interfere with registry and API anymore
** Still work weirdly, people probably shouldn't use them
** But we have lots of clunky modules since we wrap the whole of VTK; some people might rely on this and know how to use them, let's keep them anyway
** Ready for 2.2.0

=== April 1, 2015 ===
'''Updates'''
* [RR] UV-CDAT: bugfixing for 2.2, long-term plans: implement scripting import/export in VisTrails, port to UV-CDAT
* Possibly, try to move to regular VisTrails to use new features

'''Items to Discuss'''
* 2.2 release: nothing much is pending anymore, release next week?
** [TE] vtkExporter classes [https://github.com/VisTrails/VisTrails/issues/1032 #1032]
** [RR] Hiding upgrades in version tree might make it (or might be 2.2.1 so we can test it out) [https://github.com/VisTrails/VisTrails/issues/949 #949]
** Output modules changes to go in
* add note to documentation about order of parameters in VTK
* add issue about exporter upgrades if not already there

=== March 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* 2.2 release
** Checklist on Github: https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist
** Review output modules
** RR has a couple more issues to fix
** Ready to go -- sign app package for OSX? [https://github.com/VisTrails/VisTrails/issues/984 #984] We need access to the Apple Membership team

=== March 18, 2015 ===
'''Updates'''
* [TE] VTK6 works

'''Items to Discuss'''
* [RR] Release v2.1.5 with backported tabledata?
** MTA example needs updated tabledata (for JoinTables)
** Google Maps package still not available
* [RR] Work torward v2.2.0?
** changes:
*** new persistence
*** API changes
*** output module changes (upgrades?), maintain cells but try to upgrade
*** not wrapping stuff
*** VTK6? yes
*** JobSubmission stuff?
*** relabeling for upgrades [https://github.com/VisTrails/VisTrails/issues/949 #949]
** makes sense, needs the tree view code to be updated, check selection
** See [https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist 2.2 checklist]
* Discussion of [https://github.com/VisTrails/VisTrails/issues/1016 #1016]
** plumbing between outputs and output modes, how to define a mode that works for many outputs without writing for each output?

=== March 11, 2015 ===
'''Updates'''
* [RR] persistent_archive done; merge? ([https://github.com/VisTrails/VisTrails/pull/755 #755])
** note about the focus events for widgets
** TE be aware of file_archive for future binaries that include persistent_archive
* [TE] [https://github.com/VisTrails/VisTrails/pull/998 New VTK package] finished

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails? (see last week; decision needed)
** RR email to JF about this
** yes; email sent to Github
* [RR] Switching order of output ports ([https://github.com/VisTrails/VisTrails/pull/1006 #1006])
** added port specs are sorted at a separate spot (Module.*_port_specs properties) than those in the registry (which are sorted in the registry), but those two lists are just combined without respect to sort keys
** need to determine whether the two lists should be merged or remain distinct
** should make sure that order of input ports and output ports makes parallel connections for things with same order
** DK suggests breaking backward compatibility here: workflows still run, can fix easily if a problem in an existing package.
* [RR] Question about output modes ([https://github.com/VisTrails/VisTrails/pull/1007 #1007]), how to integrate in API ([https://github.com/VisTrails/VisTrails/pull/24 #24])
** Should ImageFileMode be removed? ("image" is not a mode, "file" is)
** ImageOutput missing?
** Feel free to change how formats works
* [TE] Test suite segfaults on Fedora 17 virtualbox. Install newer version? (Support ended in 2013)

=== March 4, 2015 ===
'''Updates'''
* [TE] VTK wrapper
** Works on VTK 5.10
** Still need to test VTK 6
** New general wrappers for python functions and classes

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails?
** When [http://i.imgur.com/UTY2qfg.png filing a pull request] from UV-CDAT/VisTrails, VisTrails/VisTrails is selected by default
** People keep forgetting to change the default ([https://github.com/VisTrails/VisTrails/pull/956 #956] [https://github.com/VisTrails/VisTrails/pull/968 #968] [https://github.com/VisTrails/VisTrails/pull/999 #999] [https://github.com/VisTrails/VisTrails/pull/1000 #1000] [https://github.com/VisTrails/VisTrails/pull/1003 #1003] [https://github.com/VisTrails/VisTrails/pull/1004 #1004] [https://github.com/VisTrails/VisTrails/pull/1005 #1005])
** Only way to change that is to not have it marked as a fork of VisTrails/VisTrails
** Github staff [https://gist.github.com/remram44/b364c24ef1e462ce6e2f can make that change for us]; should we do it?
** Juliana: comments on this? visibility vs. convenience/annoyance for developers
* [RR] What about [https://github.com/VisTrails/VisTrails/issues/991 #991]?

=== February 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] vtkviewcell for infovis support, can we unify with VTKCell?
** need to test this
* [TE] vtk wrapping
** Mostly finished
** VTK 5.10 produce incorrect results with old wrapping
*** Old wrapper is based mostly on VTK 4
*** Most vtk_examples affected
*** [http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Replacement_of_SetInput]
*** should be able to upgrade from SetInput to SetInputData (need to drop GetOutput and replace with self ports)
*** can we change vtkInstance to just return self and not wrap things
** terminator example not working under 5.8?
* How does VTK wrapping fit into general wrapping framework?
* [RR] new persistence package

=== February 18, 2015 ===
'''Updates'''
* [RR] New VisTrails API and IPython integration ([https://github.com/VisTrails/VisTrails/pull/24 #24])

'''Items to Discuss'''
* [TE] VTK wrapping
** [https://gist.github.com/rexissimus/16b74693545b5e7c1035 Benchmarking vtk package]
*** Old: 24.7 seconds
*** New: 10.5 seconds (Except first time that adds 8 sec)
**** The parsing that calls is_abstract (that tries to instanciate all vtk classes) is now only run the first time.
**** get_items_from_sigstring takes 2 seconds, maybe we can use a lookup dict for already computed sigstrings?
** Now using a general python function wrapper
*** VTK classes are wrapped into python function that does not depend on vistrails
*** VTK functions can be executed without vistrails
*** The spec maps functions into vistrails modules, but can also describe wrapping
*** A general python function wrapper that supports
**** kwarg inputs
**** single, list, dict outputs
**** callback for progress reporting
**** temporary file generator for using FilePool
**** optional output generation
*** Creating specs:
***** Create spec by hand
***** Auto-create spec outline (TODO) and manually finish it
***** Dynamically create spec (VTK)
***** Implement documentation wrappers (Can use scikitlearn wrapper to wrap numpydoc) (TODO)
***** Classes as bad functions needs to be wrapped in new functions before they are wrapped. This is different for each package.
****** Classes is hard: Like VTK, and matplotlib. Scikit-learn does still not wrap classes
***** Spec diffing and patching could be done using code from matplotlib.
** Still needs upgrades from old VTK package
*** Is it possible to dynamically wrap functions, e.g, you see a SetFunc and just remove the 'Set' prefix. Or do you need to create a complete mapping?

=== February 11, 2015 ===
'''Updates'''
* Update from Friday's meeting
** discussed VisTrails internals
** discussed wrapping
*** xml discussion, hard to modify because tied to db code
*** TE has made it possible to add the schema-defined attributes to the intermediate representation
*** higher-level operations on the port specs
** make sure the simple case works
*** [JF] take a simple package with documentation and figure out what the base case for wrapping is

'''Items to Discuss'''
* [TE] VTK wrapping
** Dynamic loading works
** Reading XML is fast enough, but [https://gist.github.com/rexissimus/8272d3c776ccfa115d82 unserializing data is slow]
** Working on patterns for patching
** Matplotlib has many advanced patterns like argument ordering, nested arguments, alternateSpecs, output types.
*** Having all this in a general wrapper might confuse users?
** [RR] Delay module (except for identifiers) until you need it---e.g. don't deal with port specs, etc. until necessary
* Scripting Support [https://github.com/VisTrails/VisTrails/pull/950 #950]
** [RR] Issue with getting code from modules
** Design a simple solution
** [JF] Couldn't you use modules as black boxes without conversion, just to call into modules/subworkflows easily from e.g. IPython?
*** [RR] This is a job for the API, and a very separate use case. See [https://github.com/VisTrails/VisTrails/pull/24 #24]

=== February 4, 2015 ===
'''Updates'''

'''Items to Discuss'''
* Wrapping
** Format to use? Currently XML (like current matplotlib)
*** JSON and YAML have simple "to python dictionary" methods
*** But don't stream
*** YAML a lot easier for humans
** [DK] vtk-new-package also changes parameter names, creates enumerations
*** intermediate schema needs to be extensible
*** packages will want to store there specific infos for compute() method generation
*** also might have specs-altering info, like matplotlib's alternateSpec
** representation to code , registry already has schema for some aspects
** [RR] We might want to see if Module subclasses can be created lazily
*** no need to create all the classes just to register them in the registry and never actually use most of them
*** future effort
* [RR] Where should VisTrails packages live?
** tej installs as 'vistrailspkg.tej', TE installed it as 'userpackages.tej'
** Currently, standard packages are 'vistrails.packages.', user packages are 'userpackages.' and packages loaded through pkg_resources might be anything
** [RR] Use 'vistrailspkg.' everywhere?
** Long-term effort to simplify package distribution/installation (and have VisTrails get them automatically?)

=== January 28, 2015 ===
'''Updates'''
* T. Caswell to come visit on Fri 6 to discuss wrapping work

'''Items to Discuss'''
* [TE] New VTK wrapping
** Current code by DK seems a good deal faster
** Generates XML that can be patched/tweaked, generates Python code from it, VisTrails only loads generated Python code
** RR would rather have VisTrails load intermediate representation (= XML) directly, wants to make sure this is not slower
** The goal is to turn the intermediate step into something generic that would be used for every wrapped package (vtk, numpy, matplotlib, sklearn, java) instead of each having its own
** TC has its own code at [https://github.com/Nikea/VTTools/blob/master/vttools/wrap_lib.py github:VTTools] which parses numpy docstrings and generates modules, doesn't yet handle classes or persist anything
* Web crawler
** Right now, TE starts jobs for "start crawler", "stop crawler", "install classifier"
** RR would rather have the crawling be a job as far as VisTrails and tej are concerned
** The whole thing would be one pipeline: load examples, train classifier, start crawler [check for job, kill previous one, upload model, start processes], get snapshot, visualize
*** Need some support in tej and job submission system: long-running jobs, stop a job (wait for it to finish?), restart a job even though results are cached

=== January 21, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Unified wrapping method discussion [https://github.com/VisTrails/VisTrails/issues/991 #991]
** TE to work on reusable method with intermediate representation, starting with VTK
* [RR] Examples for scikit-learn: JF has an old example using Weka with parameter exploration (not currently in source tree)
** AM's examples are enough
* [AM] scikit-learn package is done, merge it in? [https://github.com/VisTrails/VisTrails/pull/955#issuecomment-70286788 #955]
** RR will merge
* [RR] What should copyright headers say? [https://github.com/VisTrails/VisTrails/pull/994#issuecomment-70173935 #994]
** Let's keep everything in there: Utah/Poly/NYU

=== January 14, 2015 ===
'''Updates'''
* [TE] Working on classifier
* [RR] Scripting integration, work in progress

'''Items to Discuss'''
* [RR] Unified wrapping method discussion ([https://github.com/VisTrails/VisTrails/issues/991 #991])
** Let's talk next week, [AM] and [DK] are not here

=== January 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* make sure that we address critical issues, questions, and pending review branches in a timely manner
* scripting support
** [RR] no issues if we want to just keep annotations in the generated code to allow the link back to a workflow
** [RR] can translate from workflow to script, working on script to workflow
** will work for parameter value changes, structural changes require changes to the annotations
** need to publish best practices here
** would be cool to do looping in scripts (easier interface than with workflows)
* notebook support (convert form notebook to workflow)
** RR will sync with FC on this
* Issue with console in built-from-scratch
** [TC] iPython rearranged some of the completion stuff in 2.2 and 2.3
** binary has old version of iPython -> 1.0.0, should we update?
* [TC] automated wrapping of numpy and scipy
** discovered a bunch of malformed documentation in numpy and scipy
** has github repo for vistrails tools
** example modules wrap a bunch of R stuff (not baked in, just how things are)
** will be pushing wrapping logic up
** port names forbidden (window and domain)
** have an import hook to get from yaml directly to VisTrails Modules
** should work for any python modules with well-formed numpy docstrings.
* [Action] should make it clear in documentation that Constant now means serializable not that the value doesn't change (e.g. List)
* [TC] might be interesting to try to build components of matplotlib and accumulate in figure (long-term project, but thinking about how this might work)
* [TE] build and build scripts
** completely automatic, buildbot
** need to set the build machines for the environment we want for the binary
** would virtualenv work here?
** [TC] anaconda can pin versions, potential path to test different configurations
** Q: upload nightly binary builds? A: makes sense, make sure they are well-labeled
* sourceforge stats: e.g. http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07
* package issues (see Remi's message)
* [TE] Scope of tej
** Support single ssh commands?
** Queue can be used as a remote machine (crawler is using queue.call*)
* SourceForge stats: http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07

== Older meetings ==
* [[Development/2014]]
* [[Development/2013]]
* [[Development/2012]]
* [[Development/2011]]
* [[Development/2010]]

Development

2016-04-27T14:00:25Z

Tommy: /* April 20, 2016 */

<div class="nonumtoc toclimit-1">
__TOC__
</div>

See also the [https://github.com/VisTrails/VisTrails/wiki/Development Github wiki]

== 2016 ==

=== April 27, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Wrapping Bokeh
** New method type "operation"
*** Transforms Figure->Glyph->Output into Glyph->Figure->Output
**** Glyph sets function name and arguments as output
**** Figure applies Glyph operation on itself
*** Useful for matplotlib?
**** matplotlib currently find actors by searching upstream?
**** But this is more difficult since matplotlib is not function-based.
** New "union" port type
*** Turns "x(float), x(list)" into "x (float, list)" and uses first set value
**** Uses only first value in tuple
**** Bokeh have many properties that support (list, string, )
*** Does not work with depth=1 types (e.g. Float of depth 1)
**** Turn Depth 1 types with known type into lists?

* [TE] New bugfix release
** Finalize survey

=== April 20, 2016 ===
'''Updates'''
* Merged upgrade fixes
** Now has infinite loop test
** loop test now correctly loops 5 times
*** remap_module used wrong (current) package version when creating ModuleDescriptor
* Fixed multi-step group upgrades (PR: [https://github.com/VisTrails/VisTrails/issues/1168 #1168])

'''Items to Discuss'''
* New bugfix release
** Merge usagestats
** Need to finalize survey

=== April 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Chaining upgrades done ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Replace "Upgrade" description annotation with "upgraded_from" annotation to identify which tags to hide?

* [TE] Iterating handle_invalid_pipeline ([https://github.com/VisTrails/VisTrails/pull/1165 #1165])
** Not based on [https://github.com/VisTrails/VisTrails/tree/chain-upgrades-loop chain-upgrades-loop]
** Cherry-pick test to preserve source?
** Need maxPipelineFixAttempts option?
*** The code is now smarter about recursion, so max attempts will "probably" never be reached.
** Need [https://github.com/VisTrails/VisTrails/commit/0ef0667426937eddb1d1c1e397f0657ffec039a9 debug messages]?
*** Would need to be moved into handle_invalid_pipeline

=== April 6, 2016 ===
'''Updates'''
* [TE] Query View improvements
** Done except for displaying "Version Info" and #1164
* [RR] Working on finishing new interpreter (finally!)

'''Items to Discuss'''
* [TE] Chaining upgrades ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Try latest upgrade first, then previous.
** If all fail, select latest upgrade?

=== March 30, 2016 ===
'''Updates'''

'''Items to Discuss'''

* [TE] Query View improvements
** Unified do_version_switch and get_upgrades as validate_version()
** Problems with query view using its own controller
*** Fixed module info not being displayed for query results
*** Still no version info for query results
*** Still an issue with version query view not being updated

=== March 23, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Usage reporting almost ready to go
** Need to record whether specific features are used: paramexpore, mashup, query
*** [DK] Record if LaTeX extension is used? But hard to distinguish from direct batch invocation
** How to record size of vistrail?
*** [DK] IdScope already walks over vistrail, use that
*** but total number of modules and versions doesn't give an idea of average size of individual pipelines

=== March 16, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Upgrades in Query Mode
** Now using code similar to do_version_switch
*** Uses handle_invalid_pipeline
*** Differences: Not using current_pipeline, flushes changes
*** New controller method get_pipeline optimized using cached pipelines (but not current_pipeline)
*** Integrate to avoid repeated code?
*** Use this for query mode?
* [TE] VisTrails 2.2.4 ready for release?
** tej package updated. Others?
* [JF] upgrades and the version tree
* [JF] provenance in Jupyter
* [DK] bundles: [https://github.com/VisTrails/VisTrails/pull/1092 #1092]

=== March 9, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixing search mode
** String query now matches all by default
*** This caused pipeline queries to never match
** String query can search: User/Notes/Tagname/Time/Module name
*** Should we search module names by default? (Disabled by default because it is expensive)
*** Fixed notes search
** '>' parameter queries in documentation but has been removed
** Fixed module matches for upgraded pipelines (By not upgrading pipeline)
*** Upgrades still a problem
*** Add "Upgrade all menu option?" (Or upgrade all on open when `hideUpgrades`)
*** [JF] Allow search on past tags

* [TE] Create new bugfix release
** Finish querying
** Path issue on windows

* [DK] Look into sqlalchemy and new bundle branches

=== March 2, 2016 ===
'''Updates'''
* [TE] Fixed cache bug with port specs
* [TE] VisTrails Next
** Most packages now work
** No qgis for Python 3

'''Items to Discuss'''
** Always dereference symlinks? [https://github.com/VisTrails/VisTrails/issues/1146 #1146]

=== February 23, 2016 ===
'''Updates'''
* [TE] Fixed PythonSource 100% CPU bug
* [TE] VisTrails Next
** Updated [http://opendap.co-ops.nos.noaa.gov/axis/webservices/wind/ NOAA Web Service] examples
*** Now uses REST service, tabledata, and Google Maps
*** Web Service replaced with DownloadFile

'''Items to Discuss'''
* [RR] Couple of fixes are in for API, and tej&reprounzip on the Mac binary. Also new release of tej, and working on anonymous usage reports.
** New 2.2 release soon?
* [RR] Anonymous usage reports
** Sends out info like number of modules & versions, packages used, Python & libs versions, execution time, specific features [https://github.com/VisTrails/VisTrails/pull/1154 #1154]
* [JF] Bring in noWorkflow to track variable dependencies, for the considered Jupyter integration?
* noWorkflow - provenance for python scripts
** Recent work on tracking dependencies
* Also integrates ReproZip with Jupyter
** [http://mybinder.org mybinder]
*** Use with ReproZip to automatically build Jupyter notebook interfaces
* Daves comments on Jupyter integration
** It is possible to identify cell order on the server side
** Not trivial to track order of cells on client side
* How does Galaxy workflows relate to VisTrails?
** Packaging in Galaxy is hard
** Galaxy for biomedical workflows, difficulty making it general
* Action items
** How difficult to track cell dependencies in Jupyter notebooks?
** Use noWorkflow to track cell dependencies?
** How difficult to modify mybinder to use ReproZip packages?

=== February 17, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixed Group memory usage
** Modules in groups are supposed to be freed when done executing
*** Prevented by logger that stored references to the modules (fixed, now using id(module))
*** Prevented by list iterator bug that stored list of modules on the 'self' port bug (fixed)
* [TE] VisTrails Next
** Removed deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** PythonSources will be upgraded
*** Fixes for Python < 3
*** fixes for VTK < 6
** TODOs
*** Remove RemoteQ
**** Port Hadoop to tej (Already have pbs)
*** Merge package wrapper
*** Finish SQLAlchemy branch
*** Finish new bundle branch
** [JF] Will contact Jeff and Matthias about moving to Python 3
* [JF] Query by Example is broken
* [JF] VisTrails Data Cleaning Project
** Use VisTrails to process and explore task-specific data while keeping provenance.
** Remi's Idea
*** Use VisTrails as the backend in a Jupyter notebook
*** Overcome problems with executing cells in random order
**** Interesting research topic, but little interest has yet been noted
*** Interesting to study how such a notebook would be used (Is there notebook usage data available?)
*** Impose restrictions to notebook cell boundaries
*** It will only work for functional operations
*** Can we fix, or detect, non-functional (mutating) operations?
*** Analyse code and data flow and see if it mutates data in unexpected ways?
*** Mutable operations can be created in many ways in Python
* Next meeting Tuesday 11:30

=== February 10, 2016 ===
'''Updates'''

'''Items to Discuss'''
* VisTrails Next
** Test suite passes
*** Python 3 less deterministic, module upgrade order random.
** [RR] updating packages: Reprounzip (pushed), tej, persistent_archive, ...
** All of our packages should run fine :)
** VTK thumbnail comparison works
*** Rendering bug on some systems
**** QVTKCell now inherits QGLWidget
*** Old thumbnails had wrong height due to spreadsheetwindow being too small
**** Fixed by regenerating thumbnails
*** Silenced deprecation messages when generating modules
*** Many new classes in VTK 7
** Remove deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** Will break existing PythonSources
**** Try to upgrade?
*** Old-style packages
**** Or only allow a new style, like __init__.py renamed to info.py? (merge with identifiers.py?)
***** Read info.py without importing package?
*** Fixes for Python < 3
*** Fixes for Qt < 5
*** fixes for VTK < 7
*** Remove self port?

=== February 3, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] [http://lists.vistrails.org/pipermail/vistrails-users/2016-January/000402.html Rendering a .pvd (ParaView) file?]

* VisTrails Next
** All tests but thumbnail comparison passes
** Still issues with gui and more packages needs to be tested
** PythonSource and MplSource upgraded with lib2to3
** Keep contrib packages? Update?
** [https://blog.kitware.com/vtk-7-0-0/ VTK 7 is released]
*** Supports Python 3
*** Will hopefully get into conda and others soon
*** Deprecates a bunch of modules

* [https://travis-ci.org/VisTrails/VisTrails/builds/106743348 Travis builder] for VisTrails Next
** Runs!
** Uses conda
*** Many levels of requirements
**** apt packages
**** conda packages
**** python packages in requirements.txt
**** python packages in setup.py
*** Can probably drop conda. Default builder does not have Qt5, but beta builder do!
*** But useful if we want to use conda in our own build process.
** Lots of errors I do not get locally?

* [http://goo.gl/forms/Z4HBrwaBWL User Survey]
** Have you used any alternatives to vistrails?
*** Relevant? More options?
** How often do you use any of these particular features in VisTrails?
*** Add/Remove alternatives?
** How important would you rank the following potential improvements to VisTrails?
*** Add alternatives?

=== January 27, 2016 ===
'''Updates'''
* New interpreter
** Working prototype soon
** Looping not completely done (and port combination mode: pairwise/cartesian...)
** Need to integrate with VisTrails
*** Compatibility with existing modules
*** Use log controller
*** Want to cache at multiple levels (whole stream/single element of stream)
*** Non-runtime attributes of modules (cache check, automatic conversion check, constant from/to string)

'''Items to Discuss'''
* User Survey

* ZMQ failing on windows (vistrails-users)

* [TE] [https://github.com/VisTrails/VisTrails/pull/1143 Python 3 branch]
** Testsuite almost passes
*** Failing are unicode filenames, some users guide examples, and thumbnail comparisons.
** Fixed issues
*** Signatures are now bytes (convert to string to show in widget)
*** Cannot compare different types, e.g., (None < 1)
**** PortSpec.depth and min/maxConn could be None. (Backport!)
**** cell.row could be None
*** Lots of unicode/bytes fixes to serializations
**** We have encryption implementations in the code! (keychain)
*** Lots of small fixes to package method differences
** Current issues
*** logging widget empty?
*** version tree signals messed up
*** provenance view legend icons black
*** Text do not fit in some widgets
*** VTK thumbnail comparison fails
**** VTK Cells have some faces in wrong direction?
**** Because running in VM?
** Installing on Ubuntu LTS/Latest Mint
*** Install latest matplotlib from pip
*** Install VTK 7.0.0rc2 from source
*** No QtWebEngine binary (controversial) (Must install sip/PyQt5/Qt5 from source)

=== January 20, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Backporting features from Python 3 + PyQt5 + Qt5
** Merged unicode with master ([https://github.com/VisTrails/VisTrails/tree/unicode unicode])
*** One unicode test failing
*** Problem saving to xml
** Used [http://python-future.org/ python-future] to run futurize stage 1 to update legacy (pre 2.6) code ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized unicode-futurized])
*** Updates print to functions 'from __future__ import print_function'
*** Updates exception calls to use 'as'
*** removes most usages of 'long' (mostly used unnecessarily)
**** Only needed for 32-bit support
*** Fixes relative imports (from __future__ import absolute_import)
** Fixing code that is deprecated in Qt 4.8 and removed in Qt 5 ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized-qt5 unicode-futurized-qt5])
*** Updated all signals to new-style
* If we go 2 to 3, this could break packages
** means we should schedule any package format changes for the same time
** e.g., imports should be unrelated to code path (function to load module from package identifier?) (take them out of vistrails.* [https://github.com/VisTrails/VisTrails/pull/1002 #1002])
** any structural changes (e.g. the __init__ versus init thing) (RR thinks it makes sense, though having both named "init" is unfortunate)
** putting package identifier as xml?
*** Python not so bad, plus some stuff in there is Python code (checking dependencies)
** version the APIs?
*** RR planning on versioning vistrails_module.Module, no point versioning the whole package?
* file formats on 2 to 3:
** no real translation/upgrade, but non-ascii values that work on 3 won't load in 2

=== January 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://gist.github.com/rexissimus/dfd27e466427529c385c Porting to Python 3 / PyQt5]
** Basic GUI and execution works
** Minimal work to support 2to3
** Hard to support both PyQt4 and PyQt5

=== January 6, 2016 ===
'''Updates'''
'''Items to Discuss'''
* Updating VisTrails dependencies
** Successfully built [https://gist.github.com/rexissimus/f1a1aada7de1c00a57c7 Win7-64/Python3/PyQt5/Qt5/WebEngine/VTK7]
*** VTK 7 is the first supporting Python 3 but is only in release candidate phase.
**** Next version of VTK 6 is rumored to support Python 3
**** There is a development branch of VTK 6 supporting Python 3
*** Can travis build this?
**** We can skip tests for WebEngine and VTK if needed
** Python 3 [https://python3wos.appspot.com/ showstoppers]
*** No MySQL-python (sqlalchemy supports mysql through other drivers)
*** No suds (there are active forks but we could also drop support?)
* Options for python2/3 support:
** Interpreter could be python2/python3 based on packages
** six layer works but not the easiest to maintain (e.g. in reprozip)
* Drop support for win-64
* Update copyright headers to 2016

== 2015 ==

=== December 30, 2015 ===
'''Updates'''
* Bokeh package finished
** Can output to Browser/IPython/Spreadsheet (Limited functionality in spreadsheet)
'''Items to Discuss'''
* Updating VisTrails dependencies
** Bokeh needs QWebEngine (Chromium) in Qt5 which requires PyQt5
*** Many plotting libraries only work in browsers
*** But Chromium may be a big and controversial dependency
*** Or create a browser version of the spreadsheet?
** Some users have requested Python 3
** Not backwards compatible?
** Target for VisTrails 3.0 with new interpreter?

=== December 16, 2015 ===
'''Updates'''
'''Items to Discuss'''
* Users list question
* [TE] Wrapping Bokeh
** Added bokeh property parser
*** complements numpydoc parser
*** Not all attributes are available, partially because I am using a pre-release version.
** Wrapped modules
*** bokeh.plotting finished (Backwards like matplotlib: Create plot then draw on it)
*** bokeh.charts mostly done (Missing arguments)
** QWebView mostly works (but no zooming or buttons)
*** It would be better to use external browser or QWebEngineView
** Added improvements to wrapper
*** Generalized port translations (Color/Path to native types)
*** Can use multiple docstring/property parsers simultaneously

=== December 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Looking into wrapper
** Will port TensorFlow
** Doing a pass on the wrapper code & doc
*** UX improvements
** Factorize high-level docstring parsers into core.wrapper? (sphinx, numpy, google)
** Problem with name vs module_name (fails sklearn tests because class_by_name() is broken)
** Looking into compressing specs, lazy registration of modules

=== December 2, 2015 ===
'''Updates'''
* [TE] Package wrapping
** Wrapped most of numpy/scipy using __all__
** Added class attribute and method access for classes (Can add to class or to separate inspector module)
** TODO: Document wrapping procedure

'''Items to Discuss'''

=== November 25, 2015 ===
'''Updates'''
* [RR] New interpreter is coming along
** Everything is a stream
** Task system, eventually work-stealing parallelism
** Streams no longer advance in lock-step
*** Allows for constructions like filter, join, sorted-merge
** depth>1 still to be tested, no current plan to allow this through the module interface
*** Through looping though, can do streams of streams

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapped most numpy functions (no polynomials)
** and half of scipy classes and functions
** Added functions manually from documentation (no parseable lists?)
** Focusing on data flow constructs (no property/method access for classes)
*** Using spec diff (empty for now) and dynamic parser (stores spec in .vistrails/)
** Python class/function wrapper now stable
** Add google doc parser?
*** Is there a parser available?

=== November 18, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Numpy class wrapping works
*** Basic type is List, since most types are array_likes.
*** TODO: More classes and functions
*** Some operations are in-place and some aren't, and docstring not super clear
*** [RR] It seems only methods mutate, and most have a numpy.xx function equivalent; just manually go through the methods and remove the mutating ones?
** Class wrapper is modular
*** Docstring parser and type string parser can be customized
*** Classes can have optional attribute/method ports
**** Inspectors and attribute/method modules can be created separately
** Use PythonCalc as an example
*** Can be re-implemented as a function with a parseable docstring
*** [RR] PythonCalc is just an example, and it might actually make sense to get rid of it, or do a proper math package with scalar operations (as separate modules, no combobox)
** [RR] TensorFlow to use wrapping as well
*** Very simple (only types 'tensor' & 'variable')

=== November 11, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapping numpy's classes using numpydoc (ndarray)
*** Wrapping constructor arguments, attribute getters/setters as module ports
**** Then how to access attributes afterwards?
***** Use input value port to class modules?
*** Wrap methods as modules? E.g., `ndarray.shape`.
*** Function wrapping is almost a subset of class wrapping
**** May be able to use the same parsing/execution methods
** VTK's non-getter/setter methods could be wrapped as modules
*** We could then remove extra logic in interpreter for keeping function order
** Bokeh uses autogenerated docstrings
*** We may be able to read the specification directly

* [RR] [https://github.com/VisTrails/VisTrails/pull/1138 TensorFlow package]
** Basic setup working, can execute the Mandelbrot example
** Will autogenerate the operations

=== November 4, 2015 ===
'''Updates'''
* [RR] Interpreter work requires a fix for [https://github.com/VisTrails/VisTrails/issues/1137 DB issue #1137]
* [DK] Kitware's Resonant [http://www.kitware.com/source/home/post/173]
** [https://github.com/girder/girder Girder]: data management system
** [https://github.com/Kitware/romanesco Romanesco]: execution engine, uses [http://www.celeryproject.org/ Celery] for task management
** Resonant Flow: web app for editing and executing workflows

'''Items to Discuss'''
* [TE] Added OSX Lion (10.7) VM on build machine using vagrant (seems ok with license?)
** New builds works on Lion
** Change the minimum requirement to 10.7?
* [TE] Package wrapping
* Added upgrade suggestions using 2 spec versions ([http://pastebin.com/30XUU8Gp example])
** using name edit distance to find matches
** Could use something better like port similarity for modules, and type similarity for ports
** Should write python upgrade code?
** Added spec to sklearn package
*** Can now diff spec versions and keep the spec static
*** There will be problems with downgrades and package versions

=== October 29, 2015 ===
'''Updates'''
* [TE] nightly-build-mac fixed (Needed to approve xcode license)

'''Items to Discuss'''
* [TE] matplotlib wrapper
** ported to general spec
** Diff can be used on general spec
*** Only needed minor changes
*** Fixed indexing bug that corrupted specs
*** Can now move diff tools to core/wrapper
** Add new plots?
*** New plots in mpl 1.3: eventplot
*** New plots in mpl 1.4: angle_spectrum, magnitude_spectrum, phase_spectrum', violinplot
*** No new plots in mpl 1.5 (from looking at boilerplate.py)

=== October 21, 2015 ===
'''Updates'''
* [RR] Alexis has arrived, will be working with [RR] on a more efficient interpreter

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package]
** Supporting multiple package versions
*** Check which version can be loaded [https://github.com/VisTrails/VisTrails/pull/1135 #1135]
*** We cannot show version requirements in the list of packages because old packages are loaded when importing the codepath
** Visual diff does not work well, but we can use the spec differ to see differences.
** Unifying vtk and matplotlib wrapping specs (WIP)
*** And porting matplotlibs spec differ to work on the general spec
*** Spec differ can then be used on vtk and other packages in the future
*** Will enable automatic upgrade generation
* [RR] Rework interpreter
** restore abstraction between interpreter/module code
** build looping, streaming, caching into the interpreter
** rework cache
** look into parallelism once basic functionality is there

=== October 14, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package] (adding numpydoc parser)

=== October 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/tree/fix-matplotlib-parser New matplotlib parser] (adding numpydoc parser)
** Added numpydoc attribute parser for plots.
*** TODO: Need better port spec reconciliation with call signature parser.
*** We can create a general numpydoc parser, but attribute types are unique to matplotlib.
** Needs package versioning
*** New spec will not support matplotlib < v1.4 due to changed path to axes classes.
*** Load spec version corresponding to installed matplotlib version?
*** Need version downgrades?

=== September 30, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Updating Matplotlib parser
** Matplotlib docstring parser fails on numpy docstrings
** I have [https://github.com/VisTrails/VisTrails/commit/eae8b0c16260810587e47c41cab53552cbb3cf0a added basic numpydoc parsing]
*** Only used by a few docstrings so far
*** Parsing uses many sources (class tables, signatures, ACCEPTS, method docstrings, definition parsing).
** Caswell said they were thinking about moving to traitlets, but this is not ready yet

=== September 23, 2015 ===
'''Updates'''
* [TE] VisTrails 2.2.3 released
** Also have pushed to PyPI, binstar, etc.
** Sourceforge vs. GitHub
*** should be able to host releases on GitHub
*** nightly binaries pushed to sf each night
*** old binaries?
* [TE] Re-wrapping MatPlotlib
** Keep static generation - Docstrings are brittle beween matplotlib versions
** Keep generating the executable classes - but create functions, not vistrails Modules
*** Why is there so much patching?
** Re-implemented Alternate PortSpec for InputPortSpec
*** It will now inherit specs from parent (No need to reimplement)
** Module upgrades?

'''Items to Discuss'''

=== September 16, 2015 ===
'''Updates'''
* [TE] Job Monitor tests and documentation done
** OK to leave document package in packages directory?

'''Items to Discuss'''
* [TE] Library wrapping: How to do code patching? [https://docs.google.com/drawings/d/1Sh3eOXot6v2y880jHKQrqXqAwr-0aoqYligg3z8G8MY/edit?usp=sharing Wrapping diagram]
** Insert code into module template (Old VTK code)
** Patch the library that is called (New VTK code)
** Somehow store code in spec and apply when executed?
*** Executed code needs at a minimum access to inputs, outputs, current class
*** Use standard input/output dict and obj reference that the code operates on?
*** Can this be done while keeping the execution abstract?

* Do new release now?

=== September 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* New release?
** [RR] wants reprounzip
** tej changes & doc
** job monitor & jobmixin fixes
** mongodb
** reprounzip
** warning: MplFigure type is int
** tabledata: add Reshape, DictoToTable & ListToTable, fix ListToTable with numpy arrays
** PythonSource can have same name for an input & output
** don't show spreadsheet at exit

=== September 2, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Limit autosaves? [https://github.com/VisTrails/VisTrails/pull/1126 #1126]

=== August 26, 2015 ===
'''Updates'''
* [TE] Added Job support to Parameter Explorations (Requested by Colin), and Mashups
** specify job ids, need to specify different ids for parameter explorations since they have the same version id
** how to deal with parameters passed in on command line
* [General] provenance: should be creating a new version when we execute workflow with changed parameters?
** currently, custom_params annotation stores this in provenance currently
** [RR] API doesn't record provenance if passing in parameters: http://git.io/vsAA5
'''Items to Discuss'''

=== August 19, 2015 ===
'''Updates'''
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [TE] Working on Job Monitor documentation

'''Items to Discuss'''
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [TE] Stop testing VisTrails 2.0?

=== August 12, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Build broken on Travis; because of IPython 4 released today? ([https://travis-ci.org/VisTrails/VisTrails/builds/75279795 build 992]; [https://github.com/VisTrails/VisTrails/issues/1123 #1123])

=== August 5, 2015 ===
'''Updates'''
* [TE] Fixes to Jobs
** Could not delete jobs
** Could not run job in group
** Job not reset when calling ModuleSuspended
** Added deleting job from context menu
* [RR] Writing documentation for everything [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

'''Items to Discuss'''

=== July 29, 2015 ===
'''Updates'''
* RR still looking into new interpreter thing
** Goal is to take out scheduling logic from Module so it can be split in multiple processes, and so that smarter strategies can be added in time
** This means some work on packages
** Spreadsheet can live in kernel process? Still some UI stuff that will take work (changing configuration, persistent archive's viewer, ...)
* [TE] Problems running examples [https://github.com/VisTrails/VisTrails/pull/1111 #1111]
** Testing of more examples requires additional packages on the test machines.
** Fixed faulty line-ending in PythonSource:s failing on Python 2.6.
** Test suite now testing SUDSWebServices (If web service is down, test suite will fail)
** preferences.py test failed reloading 'dialogs' package, switched to using 'URL'.

'''Items to Discuss'''

=== July 22, 2015 ===
'''Updates'''
* [TE] mailing lists back online
* [TE] Working on [https://github.com/VisTrails/VisTrails/issues/1107 #1107]
* [RR] Working on ReproZip package

'''Items to Discuss'''
* [RR] MongoDB package [https://github.com/VisTrails/VisTrails/pull/1106 #1106]
* [RR] Example for tej docs? [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

=== July 15, 2015 ===
'''Updates'''
* 2.2.2 released

'''Items to Discuss'''
* RR is considering executing everything in an IPython kernel (i.e. separate Python interpreter, like the one spawned for a notebook)
** It's a separate process that we can restart without restarting the app/gui
** We can isolate the execution environment (e.g. for the server)
** We can run the whole thing remotely (if your data is elsewhere, just run VisTrails locally and the pipeline elsewhere)
** Pipeline execution no longer makes the interface hang, it just makes the kernel hang (but that's fine)
** We can use notebooks as modules (probably way nicer than the PythonSource module)
** We can run multiple kernels so long as the ports carry things that are serializable
*** meaning we can put the multithreaded-interpreter without all the hacky parts it has now
*** we can run IPython kernels in all the languages IPython supports, [https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages currently 46]

=== July 8, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Buildbot github hook not working after IP address change
* [TE] No reference to VistrailsApplication ([https://github.com/VisTrails/VisTrails/issues/1103 #1103])
** [RR] Added PR [https://github.com/VisTrails/VisTrails/pull/1104 #1104]
* [TE] Reopening VT file after saving with bundled subworkflow won't offer subworkflow upgrade ([https://github.com/VisTrails/VisTrails/issues/1102 #1102])
** allow manual delete to fix right now
** fix this on top of the use-uuid branch
* [TE] Release VisTrails 2.2.1? ([https://github.com/VisTrails/VisTrails/blob/v2.2/CHANGELOG CHANGELOG])
** [https://github.com/VisTrails/VisTrails/pull/1093 output-modules-use-global-dir]
** [https://github.com/VisTrails/VisTrails/milestones/version%202.2 Current issues for 2.2]

=== July 1, 2015 ===
'''Updates'''
* [TE] PROV fixed
* [TE] Working on subworkflow issues
* [RR] Considering reworking the controller (log vs exception problem, retained upgrades causing interferences) and also the interpreter (IPython?)

'''Items to Discuss'''

=== June 24, 2015 ===
'''Updates'''

'''Items to Discuss'''
* UV-CDAT
* [TE] Can a cyclic workflow be valid? ([https://github.com/VisTrails/VisTrails/issues/1097 #1097])
** focus on disabling the ability to create cyclic pipelines because more things break than just this with a cyclic pipeline
* [RR] Relative paths ([https://github.com/VisTrails/VisTrails/pull/1057 #1057])
** This interacts with the new bundle; how do handle packing files inside the VT bundle?

=== June 17, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] current_version and reusing existing upgrades are broken ([https://github.com/VisTrails/VisTrails/issues/1095 ticket #1095])
** Could be that export to PROV is using an unflushed upgrade pipeline?
** current_version would then be correct.
** It may work to flush the actions before exporting?

=== June 10, 2015 ===
'''Updates'''
* DAT: fixed VTK issue on Linux and Mac
* Still crashes on Windows. Need help! Reminder: this works in the VisTrails spreadsheet (QCellPresenter), although no widget get changed there during a drag
** Is it a VTK bug?
** Is it simply impossible to change widgets during the drag, should we do it a different way?
** Did I miss something that is done in VisTrails but somehow not in DAT?
** Low prio, UV-CDAT doesn't run on Windows anyway

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 Updated pull request])
* Single instance code and batch mode

=== June 3, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 pr])
** Requires fixes to command line parameters, Output modules, and batch mode
** How to test this
** Updated missing/outdated flags
** Fixed view issues when generating graphs
* [TE] batch mode
** SpreadsheetOutput not enabled in batch mode. Should we check is_running_gui instead?
** Other instance setting flags from caller
** Is graphsAsPdf replacing spreadsheetDumpPdf?
** graphsAsPdf true by Default?
** Batch mode executing by default (Not needed when generating graphs)
** Re-added workflowInfo as withWorkflowInfo for writing graph and xml workflow
** [DK] batch mode should be outputting to files or stdout, shouldn't always trigger SpreadsheetMode
** execute flag, maybe make execution the default and allow a "--no-execute" if you only want to capture graphs, for example

=== May 27, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] API question
** http://lists.vistrails.org/pipermail/vistrails-users/2015-May/000357.html
* Status of DAT
** Can add VCS plot to DAT but need to work on configuration windows
** Documentation for graphics templates for UV-CDAT/vcs?
* Qt support?

=== May 20, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Reviving the DAT, integrating scripting & porting UV-CDAT!
** On [https://github.com/VisTrails/DAT GitHub] ([https://github.com/VisTrails/DAT/issues issues])
** Merging 2 years of development taking longer than expected, but getting there. The plan is to get the patches in VisTrails and never fork again, we never want to get in UV-CDAT's situation (and don't need to).
** VTK cell works fine on Linux but there was flickering on Mac & Windows before; still issues on Mac (Windows status unknown)
** Can get a VCS plot soon (but will need VTK cell fix)
** Integrate in UV-CDAT's build system (so we have cdms, VCS, ...) -> RR can do this, low priority
** How do we integrate scripting?
*** We want to be able to seamlessly make changes to a plot by changing Python code
*** Define new plots by entering Python code without writing modules/packages?
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 13, 2015 ===
'''Updates'''
* [RR] Test skipping whitelist ([https://github.com/VisTrails/VisTrails/pull/1069 #1069]) -- low priority
* [RR] Custom matplotlib modules can't be compatible with both 2.1 and 2.2 ([https://github.com/VisTrails/VisTrails/issues/1067 #1067]); should be fixed for ALPS ([https://github.com/VisTrails/VisTrails/issues/1070 #1070])

'''Items to Discuss'''
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 7, 2015 ===
'''Updates'''
* [RR] Export/import workflow to Python working!

'''Items to Discuss'''
* [Claudio] UV-CDAT
** The UV-CDAT project is the biggest user base of VisTrails
** VisTrails package management provides a lot of friction towards people plugging in their code
** Need to make it easy to integrate your random Python scripts in the system without having to deal with all the boilerplate, at least in the first step
** [RR] argues that modules are still good; UV-CDAT shouldn't move towards a purely script-based backend
** [RR] export/import with Python could reduce a lot of that friction by allowing 1) to edit workflow as Python 2) to open up boxes automatically if needed code doesn't match actual modules
** ...

=== April 29, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] <strike>Abstractions</strike> subworkflows status ([https://github.com/VisTrails/VisTrails/labels/subworkflows tickets])
* [RR] matplotlib compatibility (2.1 & 2.2), [https://github.com/VisTrails/VisTrails/issues/1067 #1067]
** RR to try and fix ALPS matplotlib modules

=== April 22, 2015 ===
'''Updates'''
* 2.2.0 has been released!
* Windows issue (via email from Ryan)
** issue with manifest file (may be a new file in VTK6?)
** Tommy has regenerated new Windows builds
* Binaries, pypi, and conda released
* [RR] Export as script
* Python sources using VTK need to switch to SetInputData (users should be aware of this)

=== April 15, 2015 ===
'''Updates'''
* Ready for 2.2.0 (apart from binary/deps issues)
** Missing some libs (scikit-learn, tej, tdparser, SQLAlchemy+connectors
** Windows: runvistrails.py is no longer used, so the PATH is wrong
** Windows: pip is broken, but it probably wouldn't work anyway because of permission issues (disable this?)
* Queries, upgrades and getPipeline() usage ([https://github.com/VisTrails/VisTrails/issues/1054 #1054])
** Getting a pipeline with getPipeline() is not safe: it might return an invalid pipeline
** This is used in many places throughout the code, like queries
** Upgrading would require going through the controller, but that creates new actions
* [TC] Avoid copying a module's output if it's used as input by exactly one downstream module ([https://github.com/VisTrails/VisTrails/issues/1060 #1060]) (useful for big numpy arrays you can update in-place)

=== April 8, 2015 ===
'''Updates'''
* [DK] Merged RR's changes for output modules (1012 and 1013)
** RR will merge remaining changes, then create v2.2 branch!

'''Items to Discuss'''
* BNL need numpy array to VTK image
** Looks like VTK has some helpers for this
** We will help if issues arise
** Will contribute back to VisTrails package
* Upgrade issue: [https://github.com/VisTrails/VisTrails/issues/1017 #1017]
** Automatic upgrades should happen between versions of provided upgrades
** Our existing upgrades work around this so it doesn't need to be 2.2.0
* Corner-case VTK modules
** No longer need VTKCell input port, so don't interfere with registry and API anymore
** Still work weirdly, people probably shouldn't use them
** But we have lots of clunky modules since we wrap the whole of VTK; some people might rely on this and know how to use them, let's keep them anyway
** Ready for 2.2.0

=== April 1, 2015 ===
'''Updates'''
* [RR] UV-CDAT: bugfixing for 2.2, long-term plans: implement scripting import/export in VisTrails, port to UV-CDAT
* Possibly, try to move to regular VisTrails to use new features

'''Items to Discuss'''
* 2.2 release: nothing much is pending anymore, release next week?
** [TE] vtkExporter classes [https://github.com/VisTrails/VisTrails/issues/1032 #1032]
** [RR] Hiding upgrades in version tree might make it (or might be 2.2.1 so we can test it out) [https://github.com/VisTrails/VisTrails/issues/949 #949]
** Output modules changes to go in
* add note to documentation about order of parameters in VTK
* add issue about exporter upgrades if not already there

=== March 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* 2.2 release
** Checklist on Github: https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist
** Review output modules
** RR has a couple more issues to fix
** Ready to go -- sign app package for OSX? [https://github.com/VisTrails/VisTrails/issues/984 #984] We need access to the Apple Membership team

=== March 18, 2015 ===
'''Updates'''
* [TE] VTK6 works

'''Items to Discuss'''
* [RR] Release v2.1.5 with backported tabledata?
** MTA example needs updated tabledata (for JoinTables)
** Google Maps package still not available
* [RR] Work torward v2.2.0?
** changes:
*** new persistence
*** API changes
*** output module changes (upgrades?), maintain cells but try to upgrade
*** not wrapping stuff
*** VTK6? yes
*** JobSubmission stuff?
*** relabeling for upgrades [https://github.com/VisTrails/VisTrails/issues/949 #949]
** makes sense, needs the tree view code to be updated, check selection
** See [https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist 2.2 checklist]
* Discussion of [https://github.com/VisTrails/VisTrails/issues/1016 #1016]
** plumbing between outputs and output modes, how to define a mode that works for many outputs without writing for each output?

=== March 11, 2015 ===
'''Updates'''
* [RR] persistent_archive done; merge? ([https://github.com/VisTrails/VisTrails/pull/755 #755])
** note about the focus events for widgets
** TE be aware of file_archive for future binaries that include persistent_archive
* [TE] [https://github.com/VisTrails/VisTrails/pull/998 New VTK package] finished

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails? (see last week; decision needed)
** RR email to JF about this
** yes; email sent to Github
* [RR] Switching order of output ports ([https://github.com/VisTrails/VisTrails/pull/1006 #1006])
** added port specs are sorted at a separate spot (Module.*_port_specs properties) than those in the registry (which are sorted in the registry), but those two lists are just combined without respect to sort keys
** need to determine whether the two lists should be merged or remain distinct
** should make sure that order of input ports and output ports makes parallel connections for things with same order
** DK suggests breaking backward compatibility here: workflows still run, can fix easily if a problem in an existing package.
* [RR] Question about output modes ([https://github.com/VisTrails/VisTrails/pull/1007 #1007]), how to integrate in API ([https://github.com/VisTrails/VisTrails/pull/24 #24])
** Should ImageFileMode be removed? ("image" is not a mode, "file" is)
** ImageOutput missing?
** Feel free to change how formats works
* [TE] Test suite segfaults on Fedora 17 virtualbox. Install newer version? (Support ended in 2013)

=== March 4, 2015 ===
'''Updates'''
* [TE] VTK wrapper
** Works on VTK 5.10
** Still need to test VTK 6
** New general wrappers for python functions and classes

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails?
** When [http://i.imgur.com/UTY2qfg.png filing a pull request] from UV-CDAT/VisTrails, VisTrails/VisTrails is selected by default
** People keep forgetting to change the default ([https://github.com/VisTrails/VisTrails/pull/956 #956] [https://github.com/VisTrails/VisTrails/pull/968 #968] [https://github.com/VisTrails/VisTrails/pull/999 #999] [https://github.com/VisTrails/VisTrails/pull/1000 #1000] [https://github.com/VisTrails/VisTrails/pull/1003 #1003] [https://github.com/VisTrails/VisTrails/pull/1004 #1004] [https://github.com/VisTrails/VisTrails/pull/1005 #1005])
** Only way to change that is to not have it marked as a fork of VisTrails/VisTrails
** Github staff [https://gist.github.com/remram44/b364c24ef1e462ce6e2f can make that change for us]; should we do it?
** Juliana: comments on this? visibility vs. convenience/annoyance for developers
* [RR] What about [https://github.com/VisTrails/VisTrails/issues/991 #991]?

=== February 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] vtkviewcell for infovis support, can we unify with VTKCell?
** need to test this
* [TE] vtk wrapping
** Mostly finished
** VTK 5.10 produce incorrect results with old wrapping
*** Old wrapper is based mostly on VTK 4
*** Most vtk_examples affected
*** [http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Replacement_of_SetInput]
*** should be able to upgrade from SetInput to SetInputData (need to drop GetOutput and replace with self ports)
*** can we change vtkInstance to just return self and not wrap things
** terminator example not working under 5.8?
* How does VTK wrapping fit into general wrapping framework?
* [RR] new persistence package

=== February 18, 2015 ===
'''Updates'''
* [RR] New VisTrails API and IPython integration ([https://github.com/VisTrails/VisTrails/pull/24 #24])

'''Items to Discuss'''
* [TE] VTK wrapping
** [https://gist.github.com/rexissimus/16b74693545b5e7c1035 Benchmarking vtk package]
*** Old: 24.7 seconds
*** New: 10.5 seconds (Except first time that adds 8 sec)
**** The parsing that calls is_abstract (that tries to instanciate all vtk classes) is now only run the first time.
**** get_items_from_sigstring takes 2 seconds, maybe we can use a lookup dict for already computed sigstrings?
** Now using a general python function wrapper
*** VTK classes are wrapped into python function that does not depend on vistrails
*** VTK functions can be executed without vistrails
*** The spec maps functions into vistrails modules, but can also describe wrapping
*** A general python function wrapper that supports
**** kwarg inputs
**** single, list, dict outputs
**** callback for progress reporting
**** temporary file generator for using FilePool
**** optional output generation
*** Creating specs:
***** Create spec by hand
***** Auto-create spec outline (TODO) and manually finish it
***** Dynamically create spec (VTK)
***** Implement documentation wrappers (Can use scikitlearn wrapper to wrap numpydoc) (TODO)
***** Classes as bad functions needs to be wrapped in new functions before they are wrapped. This is different for each package.
****** Classes is hard: Like VTK, and matplotlib. Scikit-learn does still not wrap classes
***** Spec diffing and patching could be done using code from matplotlib.
** Still needs upgrades from old VTK package
*** Is it possible to dynamically wrap functions, e.g, you see a SetFunc and just remove the 'Set' prefix. Or do you need to create a complete mapping?

=== February 11, 2015 ===
'''Updates'''
* Update from Friday's meeting
** discussed VisTrails internals
** discussed wrapping
*** xml discussion, hard to modify because tied to db code
*** TE has made it possible to add the schema-defined attributes to the intermediate representation
*** higher-level operations on the port specs
** make sure the simple case works
*** [JF] take a simple package with documentation and figure out what the base case for wrapping is

'''Items to Discuss'''
* [TE] VTK wrapping
** Dynamic loading works
** Reading XML is fast enough, but [https://gist.github.com/rexissimus/8272d3c776ccfa115d82 unserializing data is slow]
** Working on patterns for patching
** Matplotlib has many advanced patterns like argument ordering, nested arguments, alternateSpecs, output types.
*** Having all this in a general wrapper might confuse users?
** [RR] Delay module (except for identifiers) until you need it---e.g. don't deal with port specs, etc. until necessary
* Scripting Support [https://github.com/VisTrails/VisTrails/pull/950 #950]
** [RR] Issue with getting code from modules
** Design a simple solution
** [JF] Couldn't you use modules as black boxes without conversion, just to call into modules/subworkflows easily from e.g. IPython?
*** [RR] This is a job for the API, and a very separate use case. See [https://github.com/VisTrails/VisTrails/pull/24 #24]

=== February 4, 2015 ===
'''Updates'''

'''Items to Discuss'''
* Wrapping
** Format to use? Currently XML (like current matplotlib)
*** JSON and YAML have simple "to python dictionary" methods
*** But don't stream
*** YAML a lot easier for humans
** [DK] vtk-new-package also changes parameter names, creates enumerations
*** intermediate schema needs to be extensible
*** packages will want to store there specific infos for compute() method generation
*** also might have specs-altering info, like matplotlib's alternateSpec
** representation to code , registry already has schema for some aspects
** [RR] We might want to see if Module subclasses can be created lazily
*** no need to create all the classes just to register them in the registry and never actually use most of them
*** future effort
* [RR] Where should VisTrails packages live?
** tej installs as 'vistrailspkg.tej', TE installed it as 'userpackages.tej'
** Currently, standard packages are 'vistrails.packages.', user packages are 'userpackages.' and packages loaded through pkg_resources might be anything
** [RR] Use 'vistrailspkg.' everywhere?
** Long-term effort to simplify package distribution/installation (and have VisTrails get them automatically?)

=== January 28, 2015 ===
'''Updates'''
* T. Caswell to come visit on Fri 6 to discuss wrapping work

'''Items to Discuss'''
* [TE] New VTK wrapping
** Current code by DK seems a good deal faster
** Generates XML that can be patched/tweaked, generates Python code from it, VisTrails only loads generated Python code
** RR would rather have VisTrails load intermediate representation (= XML) directly, wants to make sure this is not slower
** The goal is to turn the intermediate step into something generic that would be used for every wrapped package (vtk, numpy, matplotlib, sklearn, java) instead of each having its own
** TC has its own code at [https://github.com/Nikea/VTTools/blob/master/vttools/wrap_lib.py github:VTTools] which parses numpy docstrings and generates modules, doesn't yet handle classes or persist anything
* Web crawler
** Right now, TE starts jobs for "start crawler", "stop crawler", "install classifier"
** RR would rather have the crawling be a job as far as VisTrails and tej are concerned
** The whole thing would be one pipeline: load examples, train classifier, start crawler [check for job, kill previous one, upload model, start processes], get snapshot, visualize
*** Need some support in tej and job submission system: long-running jobs, stop a job (wait for it to finish?), restart a job even though results are cached

=== January 21, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Unified wrapping method discussion [https://github.com/VisTrails/VisTrails/issues/991 #991]
** TE to work on reusable method with intermediate representation, starting with VTK
* [RR] Examples for scikit-learn: JF has an old example using Weka with parameter exploration (not currently in source tree)
** AM's examples are enough
* [AM] scikit-learn package is done, merge it in? [https://github.com/VisTrails/VisTrails/pull/955#issuecomment-70286788 #955]
** RR will merge
* [RR] What should copyright headers say? [https://github.com/VisTrails/VisTrails/pull/994#issuecomment-70173935 #994]
** Let's keep everything in there: Utah/Poly/NYU

=== January 14, 2015 ===
'''Updates'''
* [TE] Working on classifier
* [RR] Scripting integration, work in progress

'''Items to Discuss'''
* [RR] Unified wrapping method discussion ([https://github.com/VisTrails/VisTrails/issues/991 #991])
** Let's talk next week, [AM] and [DK] are not here

=== January 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* make sure that we address critical issues, questions, and pending review branches in a timely manner
* scripting support
** [RR] no issues if we want to just keep annotations in the generated code to allow the link back to a workflow
** [RR] can translate from workflow to script, working on script to workflow
** will work for parameter value changes, structural changes require changes to the annotations
** need to publish best practices here
** would be cool to do looping in scripts (easier interface than with workflows)
* notebook support (convert form notebook to workflow)
** RR will sync with FC on this
* Issue with console in built-from-scratch
** [TC] iPython rearranged some of the completion stuff in 2.2 and 2.3
** binary has old version of iPython -> 1.0.0, should we update?
* [TC] automated wrapping of numpy and scipy
** discovered a bunch of malformed documentation in numpy and scipy
** has github repo for vistrails tools
** example modules wrap a bunch of R stuff (not baked in, just how things are)
** will be pushing wrapping logic up
** port names forbidden (window and domain)
** have an import hook to get from yaml directly to VisTrails Modules
** should work for any python modules with well-formed numpy docstrings.
* [Action] should make it clear in documentation that Constant now means serializable not that the value doesn't change (e.g. List)
* [TC] might be interesting to try to build components of matplotlib and accumulate in figure (long-term project, but thinking about how this might work)
* [TE] build and build scripts
** completely automatic, buildbot
** need to set the build machines for the environment we want for the binary
** would virtualenv work here?
** [TC] anaconda can pin versions, potential path to test different configurations
** Q: upload nightly binary builds? A: makes sense, make sure they are well-labeled
* sourceforge stats: e.g. http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07
* package issues (see Remi's message)
* [TE] Scope of tej
** Support single ssh commands?
** Queue can be used as a remote machine (crawler is using queue.call*)
* SourceForge stats: http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07

== Older meetings ==
* [[Development/2014]]
* [[Development/2013]]
* [[Development/2012]]
* [[Development/2011]]
* [[Development/2010]]

Development

2016-04-20T22:26:42Z

Tommy: /* April 20, 2016 */

<div class="nonumtoc toclimit-1">
__TOC__
</div>

See also the [https://github.com/VisTrails/VisTrails/wiki/Development Github wiki]

== 2016 ==

=== April 20, 2016 ===
'''Updates'''
* Merged upgrade fixes
** Now has infinite loop test
** loop test now correctly loops 5 times
*** remap_module used wrong (current) package version when creating ModuleDescriptor
* Fixed multi-step group upgrades (PR: [https://github.com/VisTrails/VisTrails/issues/1168 #1168])

'''Items to Discuss'''
* New bugfix release
** Merge usagestats
** Need to finalize survey

=== April 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Chaining upgrades done ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Replace "Upgrade" description annotation with "upgraded_from" annotation to identify which tags to hide?

* [TE] Iterating handle_invalid_pipeline ([https://github.com/VisTrails/VisTrails/pull/1165 #1165])
** Not based on [https://github.com/VisTrails/VisTrails/tree/chain-upgrades-loop chain-upgrades-loop]
** Cherry-pick test to preserve source?
** Need maxPipelineFixAttempts option?
*** The code is now smarter about recursion, so max attempts will "probably" never be reached.
** Need [https://github.com/VisTrails/VisTrails/commit/0ef0667426937eddb1d1c1e397f0657ffec039a9 debug messages]?
*** Would need to be moved into handle_invalid_pipeline

=== April 6, 2016 ===
'''Updates'''
* [TE] Query View improvements
** Done except for displaying "Version Info" and #1164
* [RR] Working on finishing new interpreter (finally!)

'''Items to Discuss'''
* [TE] Chaining upgrades ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Try latest upgrade first, then previous.
** If all fail, select latest upgrade?

=== March 30, 2016 ===
'''Updates'''

'''Items to Discuss'''

* [TE] Query View improvements
** Unified do_version_switch and get_upgrades as validate_version()
** Problems with query view using its own controller
*** Fixed module info not being displayed for query results
*** Still no version info for query results
*** Still an issue with version query view not being updated

=== March 23, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Usage reporting almost ready to go
** Need to record whether specific features are used: paramexpore, mashup, query
*** [DK] Record if LaTeX extension is used? But hard to distinguish from direct batch invocation
** How to record size of vistrail?
*** [DK] IdScope already walks over vistrail, use that
*** but total number of modules and versions doesn't give an idea of average size of individual pipelines

=== March 16, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Upgrades in Query Mode
** Now using code similar to do_version_switch
*** Uses handle_invalid_pipeline
*** Differences: Not using current_pipeline, flushes changes
*** New controller method get_pipeline optimized using cached pipelines (but not current_pipeline)
*** Integrate to avoid repeated code?
*** Use this for query mode?
* [TE] VisTrails 2.2.4 ready for release?
** tej package updated. Others?
* [JF] upgrades and the version tree
* [JF] provenance in Jupyter
* [DK] bundles: [https://github.com/VisTrails/VisTrails/pull/1092 #1092]

=== March 9, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixing search mode
** String query now matches all by default
*** This caused pipeline queries to never match
** String query can search: User/Notes/Tagname/Time/Module name
*** Should we search module names by default? (Disabled by default because it is expensive)
*** Fixed notes search
** '>' parameter queries in documentation but has been removed
** Fixed module matches for upgraded pipelines (By not upgrading pipeline)
*** Upgrades still a problem
*** Add "Upgrade all menu option?" (Or upgrade all on open when `hideUpgrades`)
*** [JF] Allow search on past tags

* [TE] Create new bugfix release
** Finish querying
** Path issue on windows

* [DK] Look into sqlalchemy and new bundle branches

=== March 2, 2016 ===
'''Updates'''
* [TE] Fixed cache bug with port specs
* [TE] VisTrails Next
** Most packages now work
** No qgis for Python 3

'''Items to Discuss'''
** Always dereference symlinks? [https://github.com/VisTrails/VisTrails/issues/1146 #1146]

=== February 23, 2016 ===
'''Updates'''
* [TE] Fixed PythonSource 100% CPU bug
* [TE] VisTrails Next
** Updated [http://opendap.co-ops.nos.noaa.gov/axis/webservices/wind/ NOAA Web Service] examples
*** Now uses REST service, tabledata, and Google Maps
*** Web Service replaced with DownloadFile

'''Items to Discuss'''
* [RR] Couple of fixes are in for API, and tej&reprounzip on the Mac binary. Also new release of tej, and working on anonymous usage reports.
** New 2.2 release soon?
* [RR] Anonymous usage reports
** Sends out info like number of modules & versions, packages used, Python & libs versions, execution time, specific features [https://github.com/VisTrails/VisTrails/pull/1154 #1154]
* [JF] Bring in noWorkflow to track variable dependencies, for the considered Jupyter integration?
* noWorkflow - provenance for python scripts
** Recent work on tracking dependencies
* Also integrates ReproZip with Jupyter
** [http://mybinder.org mybinder]
*** Use with ReproZip to automatically build Jupyter notebook interfaces
* Daves comments on Jupyter integration
** It is possible to identify cell order on the server side
** Not trivial to track order of cells on client side
* How does Galaxy workflows relate to VisTrails?
** Packaging in Galaxy is hard
** Galaxy for biomedical workflows, difficulty making it general
* Action items
** How difficult to track cell dependencies in Jupyter notebooks?
** Use noWorkflow to track cell dependencies?
** How difficult to modify mybinder to use ReproZip packages?

=== February 17, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixed Group memory usage
** Modules in groups are supposed to be freed when done executing
*** Prevented by logger that stored references to the modules (fixed, now using id(module))
*** Prevented by list iterator bug that stored list of modules on the 'self' port bug (fixed)
* [TE] VisTrails Next
** Removed deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** PythonSources will be upgraded
*** Fixes for Python < 3
*** fixes for VTK < 6
** TODOs
*** Remove RemoteQ
**** Port Hadoop to tej (Already have pbs)
*** Merge package wrapper
*** Finish SQLAlchemy branch
*** Finish new bundle branch
** [JF] Will contact Jeff and Matthias about moving to Python 3
* [JF] Query by Example is broken
* [JF] VisTrails Data Cleaning Project
** Use VisTrails to process and explore task-specific data while keeping provenance.
** Remi's Idea
*** Use VisTrails as the backend in a Jupyter notebook
*** Overcome problems with executing cells in random order
**** Interesting research topic, but little interest has yet been noted
*** Interesting to study how such a notebook would be used (Is there notebook usage data available?)
*** Impose restrictions to notebook cell boundaries
*** It will only work for functional operations
*** Can we fix, or detect, non-functional (mutating) operations?
*** Analyse code and data flow and see if it mutates data in unexpected ways?
*** Mutable operations can be created in many ways in Python
* Next meeting Tuesday 11:30

=== February 10, 2016 ===
'''Updates'''

'''Items to Discuss'''
* VisTrails Next
** Test suite passes
*** Python 3 less deterministic, module upgrade order random.
** [RR] updating packages: Reprounzip (pushed), tej, persistent_archive, ...
** All of our packages should run fine :)
** VTK thumbnail comparison works
*** Rendering bug on some systems
**** QVTKCell now inherits QGLWidget
*** Old thumbnails had wrong height due to spreadsheetwindow being too small
**** Fixed by regenerating thumbnails
*** Silenced deprecation messages when generating modules
*** Many new classes in VTK 7
** Remove deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** Will break existing PythonSources
**** Try to upgrade?
*** Old-style packages
**** Or only allow a new style, like __init__.py renamed to info.py? (merge with identifiers.py?)
***** Read info.py without importing package?
*** Fixes for Python < 3
*** Fixes for Qt < 5
*** fixes for VTK < 7
*** Remove self port?

=== February 3, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] [http://lists.vistrails.org/pipermail/vistrails-users/2016-January/000402.html Rendering a .pvd (ParaView) file?]

* VisTrails Next
** All tests but thumbnail comparison passes
** Still issues with gui and more packages needs to be tested
** PythonSource and MplSource upgraded with lib2to3
** Keep contrib packages? Update?
** [https://blog.kitware.com/vtk-7-0-0/ VTK 7 is released]
*** Supports Python 3
*** Will hopefully get into conda and others soon
*** Deprecates a bunch of modules

* [https://travis-ci.org/VisTrails/VisTrails/builds/106743348 Travis builder] for VisTrails Next
** Runs!
** Uses conda
*** Many levels of requirements
**** apt packages
**** conda packages
**** python packages in requirements.txt
**** python packages in setup.py
*** Can probably drop conda. Default builder does not have Qt5, but beta builder do!
*** But useful if we want to use conda in our own build process.
** Lots of errors I do not get locally?

* [http://goo.gl/forms/Z4HBrwaBWL User Survey]
** Have you used any alternatives to vistrails?
*** Relevant? More options?
** How often do you use any of these particular features in VisTrails?
*** Add/Remove alternatives?
** How important would you rank the following potential improvements to VisTrails?
*** Add alternatives?

=== January 27, 2016 ===
'''Updates'''
* New interpreter
** Working prototype soon
** Looping not completely done (and port combination mode: pairwise/cartesian...)
** Need to integrate with VisTrails
*** Compatibility with existing modules
*** Use log controller
*** Want to cache at multiple levels (whole stream/single element of stream)
*** Non-runtime attributes of modules (cache check, automatic conversion check, constant from/to string)

'''Items to Discuss'''
* User Survey

* ZMQ failing on windows (vistrails-users)

* [TE] [https://github.com/VisTrails/VisTrails/pull/1143 Python 3 branch]
** Testsuite almost passes
*** Failing are unicode filenames, some users guide examples, and thumbnail comparisons.
** Fixed issues
*** Signatures are now bytes (convert to string to show in widget)
*** Cannot compare different types, e.g., (None < 1)
**** PortSpec.depth and min/maxConn could be None. (Backport!)
**** cell.row could be None
*** Lots of unicode/bytes fixes to serializations
**** We have encryption implementations in the code! (keychain)
*** Lots of small fixes to package method differences
** Current issues
*** logging widget empty?
*** version tree signals messed up
*** provenance view legend icons black
*** Text do not fit in some widgets
*** VTK thumbnail comparison fails
**** VTK Cells have some faces in wrong direction?
**** Because running in VM?
** Installing on Ubuntu LTS/Latest Mint
*** Install latest matplotlib from pip
*** Install VTK 7.0.0rc2 from source
*** No QtWebEngine binary (controversial) (Must install sip/PyQt5/Qt5 from source)

=== January 20, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Backporting features from Python 3 + PyQt5 + Qt5
** Merged unicode with master ([https://github.com/VisTrails/VisTrails/tree/unicode unicode])
*** One unicode test failing
*** Problem saving to xml
** Used [http://python-future.org/ python-future] to run futurize stage 1 to update legacy (pre 2.6) code ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized unicode-futurized])
*** Updates print to functions 'from __future__ import print_function'
*** Updates exception calls to use 'as'
*** removes most usages of 'long' (mostly used unnecessarily)
**** Only needed for 32-bit support
*** Fixes relative imports (from __future__ import absolute_import)
** Fixing code that is deprecated in Qt 4.8 and removed in Qt 5 ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized-qt5 unicode-futurized-qt5])
*** Updated all signals to new-style
* If we go 2 to 3, this could break packages
** means we should schedule any package format changes for the same time
** e.g., imports should be unrelated to code path (function to load module from package identifier?) (take them out of vistrails.* [https://github.com/VisTrails/VisTrails/pull/1002 #1002])
** any structural changes (e.g. the __init__ versus init thing) (RR thinks it makes sense, though having both named "init" is unfortunate)
** putting package identifier as xml?
*** Python not so bad, plus some stuff in there is Python code (checking dependencies)
** version the APIs?
*** RR planning on versioning vistrails_module.Module, no point versioning the whole package?
* file formats on 2 to 3:
** no real translation/upgrade, but non-ascii values that work on 3 won't load in 2

=== January 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://gist.github.com/rexissimus/dfd27e466427529c385c Porting to Python 3 / PyQt5]
** Basic GUI and execution works
** Minimal work to support 2to3
** Hard to support both PyQt4 and PyQt5

=== January 6, 2016 ===
'''Updates'''
'''Items to Discuss'''
* Updating VisTrails dependencies
** Successfully built [https://gist.github.com/rexissimus/f1a1aada7de1c00a57c7 Win7-64/Python3/PyQt5/Qt5/WebEngine/VTK7]
*** VTK 7 is the first supporting Python 3 but is only in release candidate phase.
**** Next version of VTK 6 is rumored to support Python 3
**** There is a development branch of VTK 6 supporting Python 3
*** Can travis build this?
**** We can skip tests for WebEngine and VTK if needed
** Python 3 [https://python3wos.appspot.com/ showstoppers]
*** No MySQL-python (sqlalchemy supports mysql through other drivers)
*** No suds (there are active forks but we could also drop support?)
* Options for python2/3 support:
** Interpreter could be python2/python3 based on packages
** six layer works but not the easiest to maintain (e.g. in reprozip)
* Drop support for win-64
* Update copyright headers to 2016

== 2015 ==

=== December 30, 2015 ===
'''Updates'''
* Bokeh package finished
** Can output to Browser/IPython/Spreadsheet (Limited functionality in spreadsheet)
'''Items to Discuss'''
* Updating VisTrails dependencies
** Bokeh needs QWebEngine (Chromium) in Qt5 which requires PyQt5
*** Many plotting libraries only work in browsers
*** But Chromium may be a big and controversial dependency
*** Or create a browser version of the spreadsheet?
** Some users have requested Python 3
** Not backwards compatible?
** Target for VisTrails 3.0 with new interpreter?

=== December 16, 2015 ===
'''Updates'''
'''Items to Discuss'''
* Users list question
* [TE] Wrapping Bokeh
** Added bokeh property parser
*** complements numpydoc parser
*** Not all attributes are available, partially because I am using a pre-release version.
** Wrapped modules
*** bokeh.plotting finished (Backwards like matplotlib: Create plot then draw on it)
*** bokeh.charts mostly done (Missing arguments)
** QWebView mostly works (but no zooming or buttons)
*** It would be better to use external browser or QWebEngineView
** Added improvements to wrapper
*** Generalized port translations (Color/Path to native types)
*** Can use multiple docstring/property parsers simultaneously

=== December 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Looking into wrapper
** Will port TensorFlow
** Doing a pass on the wrapper code & doc
*** UX improvements
** Factorize high-level docstring parsers into core.wrapper? (sphinx, numpy, google)
** Problem with name vs module_name (fails sklearn tests because class_by_name() is broken)
** Looking into compressing specs, lazy registration of modules

=== December 2, 2015 ===
'''Updates'''
* [TE] Package wrapping
** Wrapped most of numpy/scipy using __all__
** Added class attribute and method access for classes (Can add to class or to separate inspector module)
** TODO: Document wrapping procedure

'''Items to Discuss'''

=== November 25, 2015 ===
'''Updates'''
* [RR] New interpreter is coming along
** Everything is a stream
** Task system, eventually work-stealing parallelism
** Streams no longer advance in lock-step
*** Allows for constructions like filter, join, sorted-merge
** depth>1 still to be tested, no current plan to allow this through the module interface
*** Through looping though, can do streams of streams

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapped most numpy functions (no polynomials)
** and half of scipy classes and functions
** Added functions manually from documentation (no parseable lists?)
** Focusing on data flow constructs (no property/method access for classes)
*** Using spec diff (empty for now) and dynamic parser (stores spec in .vistrails/)
** Python class/function wrapper now stable
** Add google doc parser?
*** Is there a parser available?

=== November 18, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Numpy class wrapping works
*** Basic type is List, since most types are array_likes.
*** TODO: More classes and functions
*** Some operations are in-place and some aren't, and docstring not super clear
*** [RR] It seems only methods mutate, and most have a numpy.xx function equivalent; just manually go through the methods and remove the mutating ones?
** Class wrapper is modular
*** Docstring parser and type string parser can be customized
*** Classes can have optional attribute/method ports
**** Inspectors and attribute/method modules can be created separately
** Use PythonCalc as an example
*** Can be re-implemented as a function with a parseable docstring
*** [RR] PythonCalc is just an example, and it might actually make sense to get rid of it, or do a proper math package with scalar operations (as separate modules, no combobox)
** [RR] TensorFlow to use wrapping as well
*** Very simple (only types 'tensor' & 'variable')

=== November 11, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapping numpy's classes using numpydoc (ndarray)
*** Wrapping constructor arguments, attribute getters/setters as module ports
**** Then how to access attributes afterwards?
***** Use input value port to class modules?
*** Wrap methods as modules? E.g., `ndarray.shape`.
*** Function wrapping is almost a subset of class wrapping
**** May be able to use the same parsing/execution methods
** VTK's non-getter/setter methods could be wrapped as modules
*** We could then remove extra logic in interpreter for keeping function order
** Bokeh uses autogenerated docstrings
*** We may be able to read the specification directly

* [RR] [https://github.com/VisTrails/VisTrails/pull/1138 TensorFlow package]
** Basic setup working, can execute the Mandelbrot example
** Will autogenerate the operations

=== November 4, 2015 ===
'''Updates'''
* [RR] Interpreter work requires a fix for [https://github.com/VisTrails/VisTrails/issues/1137 DB issue #1137]
* [DK] Kitware's Resonant [http://www.kitware.com/source/home/post/173]
** [https://github.com/girder/girder Girder]: data management system
** [https://github.com/Kitware/romanesco Romanesco]: execution engine, uses [http://www.celeryproject.org/ Celery] for task management
** Resonant Flow: web app for editing and executing workflows

'''Items to Discuss'''
* [TE] Added OSX Lion (10.7) VM on build machine using vagrant (seems ok with license?)
** New builds works on Lion
** Change the minimum requirement to 10.7?
* [TE] Package wrapping
* Added upgrade suggestions using 2 spec versions ([http://pastebin.com/30XUU8Gp example])
** using name edit distance to find matches
** Could use something better like port similarity for modules, and type similarity for ports
** Should write python upgrade code?
** Added spec to sklearn package
*** Can now diff spec versions and keep the spec static
*** There will be problems with downgrades and package versions

=== October 29, 2015 ===
'''Updates'''
* [TE] nightly-build-mac fixed (Needed to approve xcode license)

'''Items to Discuss'''
* [TE] matplotlib wrapper
** ported to general spec
** Diff can be used on general spec
*** Only needed minor changes
*** Fixed indexing bug that corrupted specs
*** Can now move diff tools to core/wrapper
** Add new plots?
*** New plots in mpl 1.3: eventplot
*** New plots in mpl 1.4: angle_spectrum, magnitude_spectrum, phase_spectrum', violinplot
*** No new plots in mpl 1.5 (from looking at boilerplate.py)

=== October 21, 2015 ===
'''Updates'''
* [RR] Alexis has arrived, will be working with [RR] on a more efficient interpreter

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package]
** Supporting multiple package versions
*** Check which version can be loaded [https://github.com/VisTrails/VisTrails/pull/1135 #1135]
*** We cannot show version requirements in the list of packages because old packages are loaded when importing the codepath
** Visual diff does not work well, but we can use the spec differ to see differences.
** Unifying vtk and matplotlib wrapping specs (WIP)
*** And porting matplotlibs spec differ to work on the general spec
*** Spec differ can then be used on vtk and other packages in the future
*** Will enable automatic upgrade generation
* [RR] Rework interpreter
** restore abstraction between interpreter/module code
** build looping, streaming, caching into the interpreter
** rework cache
** look into parallelism once basic functionality is there

=== October 14, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package] (adding numpydoc parser)

=== October 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/tree/fix-matplotlib-parser New matplotlib parser] (adding numpydoc parser)
** Added numpydoc attribute parser for plots.
*** TODO: Need better port spec reconciliation with call signature parser.
*** We can create a general numpydoc parser, but attribute types are unique to matplotlib.
** Needs package versioning
*** New spec will not support matplotlib < v1.4 due to changed path to axes classes.
*** Load spec version corresponding to installed matplotlib version?
*** Need version downgrades?

=== September 30, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Updating Matplotlib parser
** Matplotlib docstring parser fails on numpy docstrings
** I have [https://github.com/VisTrails/VisTrails/commit/eae8b0c16260810587e47c41cab53552cbb3cf0a added basic numpydoc parsing]
*** Only used by a few docstrings so far
*** Parsing uses many sources (class tables, signatures, ACCEPTS, method docstrings, definition parsing).
** Caswell said they were thinking about moving to traitlets, but this is not ready yet

=== September 23, 2015 ===
'''Updates'''
* [TE] VisTrails 2.2.3 released
** Also have pushed to PyPI, binstar, etc.
** Sourceforge vs. GitHub
*** should be able to host releases on GitHub
*** nightly binaries pushed to sf each night
*** old binaries?
* [TE] Re-wrapping MatPlotlib
** Keep static generation - Docstrings are brittle beween matplotlib versions
** Keep generating the executable classes - but create functions, not vistrails Modules
*** Why is there so much patching?
** Re-implemented Alternate PortSpec for InputPortSpec
*** It will now inherit specs from parent (No need to reimplement)
** Module upgrades?

'''Items to Discuss'''

=== September 16, 2015 ===
'''Updates'''
* [TE] Job Monitor tests and documentation done
** OK to leave document package in packages directory?

'''Items to Discuss'''
* [TE] Library wrapping: How to do code patching? [https://docs.google.com/drawings/d/1Sh3eOXot6v2y880jHKQrqXqAwr-0aoqYligg3z8G8MY/edit?usp=sharing Wrapping diagram]
** Insert code into module template (Old VTK code)
** Patch the library that is called (New VTK code)
** Somehow store code in spec and apply when executed?
*** Executed code needs at a minimum access to inputs, outputs, current class
*** Use standard input/output dict and obj reference that the code operates on?
*** Can this be done while keeping the execution abstract?

* Do new release now?

=== September 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* New release?
** [RR] wants reprounzip
** tej changes & doc
** job monitor & jobmixin fixes
** mongodb
** reprounzip
** warning: MplFigure type is int
** tabledata: add Reshape, DictoToTable & ListToTable, fix ListToTable with numpy arrays
** PythonSource can have same name for an input & output
** don't show spreadsheet at exit

=== September 2, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Limit autosaves? [https://github.com/VisTrails/VisTrails/pull/1126 #1126]

=== August 26, 2015 ===
'''Updates'''
* [TE] Added Job support to Parameter Explorations (Requested by Colin), and Mashups
** specify job ids, need to specify different ids for parameter explorations since they have the same version id
** how to deal with parameters passed in on command line
* [General] provenance: should be creating a new version when we execute workflow with changed parameters?
** currently, custom_params annotation stores this in provenance currently
** [RR] API doesn't record provenance if passing in parameters: http://git.io/vsAA5
'''Items to Discuss'''

=== August 19, 2015 ===
'''Updates'''
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [TE] Working on Job Monitor documentation

'''Items to Discuss'''
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [TE] Stop testing VisTrails 2.0?

=== August 12, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Build broken on Travis; because of IPython 4 released today? ([https://travis-ci.org/VisTrails/VisTrails/builds/75279795 build 992]; [https://github.com/VisTrails/VisTrails/issues/1123 #1123])

=== August 5, 2015 ===
'''Updates'''
* [TE] Fixes to Jobs
** Could not delete jobs
** Could not run job in group
** Job not reset when calling ModuleSuspended
** Added deleting job from context menu
* [RR] Writing documentation for everything [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

'''Items to Discuss'''

=== July 29, 2015 ===
'''Updates'''
* RR still looking into new interpreter thing
** Goal is to take out scheduling logic from Module so it can be split in multiple processes, and so that smarter strategies can be added in time
** This means some work on packages
** Spreadsheet can live in kernel process? Still some UI stuff that will take work (changing configuration, persistent archive's viewer, ...)
* [TE] Problems running examples [https://github.com/VisTrails/VisTrails/pull/1111 #1111]
** Testing of more examples requires additional packages on the test machines.
** Fixed faulty line-ending in PythonSource:s failing on Python 2.6.
** Test suite now testing SUDSWebServices (If web service is down, test suite will fail)
** preferences.py test failed reloading 'dialogs' package, switched to using 'URL'.

'''Items to Discuss'''

=== July 22, 2015 ===
'''Updates'''
* [TE] mailing lists back online
* [TE] Working on [https://github.com/VisTrails/VisTrails/issues/1107 #1107]
* [RR] Working on ReproZip package

'''Items to Discuss'''
* [RR] MongoDB package [https://github.com/VisTrails/VisTrails/pull/1106 #1106]
* [RR] Example for tej docs? [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

=== July 15, 2015 ===
'''Updates'''
* 2.2.2 released

'''Items to Discuss'''
* RR is considering executing everything in an IPython kernel (i.e. separate Python interpreter, like the one spawned for a notebook)
** It's a separate process that we can restart without restarting the app/gui
** We can isolate the execution environment (e.g. for the server)
** We can run the whole thing remotely (if your data is elsewhere, just run VisTrails locally and the pipeline elsewhere)
** Pipeline execution no longer makes the interface hang, it just makes the kernel hang (but that's fine)
** We can use notebooks as modules (probably way nicer than the PythonSource module)
** We can run multiple kernels so long as the ports carry things that are serializable
*** meaning we can put the multithreaded-interpreter without all the hacky parts it has now
*** we can run IPython kernels in all the languages IPython supports, [https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages currently 46]

=== July 8, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Buildbot github hook not working after IP address change
* [TE] No reference to VistrailsApplication ([https://github.com/VisTrails/VisTrails/issues/1103 #1103])
** [RR] Added PR [https://github.com/VisTrails/VisTrails/pull/1104 #1104]
* [TE] Reopening VT file after saving with bundled subworkflow won't offer subworkflow upgrade ([https://github.com/VisTrails/VisTrails/issues/1102 #1102])
** allow manual delete to fix right now
** fix this on top of the use-uuid branch
* [TE] Release VisTrails 2.2.1? ([https://github.com/VisTrails/VisTrails/blob/v2.2/CHANGELOG CHANGELOG])
** [https://github.com/VisTrails/VisTrails/pull/1093 output-modules-use-global-dir]
** [https://github.com/VisTrails/VisTrails/milestones/version%202.2 Current issues for 2.2]

=== July 1, 2015 ===
'''Updates'''
* [TE] PROV fixed
* [TE] Working on subworkflow issues
* [RR] Considering reworking the controller (log vs exception problem, retained upgrades causing interferences) and also the interpreter (IPython?)

'''Items to Discuss'''

=== June 24, 2015 ===
'''Updates'''

'''Items to Discuss'''
* UV-CDAT
* [TE] Can a cyclic workflow be valid? ([https://github.com/VisTrails/VisTrails/issues/1097 #1097])
** focus on disabling the ability to create cyclic pipelines because more things break than just this with a cyclic pipeline
* [RR] Relative paths ([https://github.com/VisTrails/VisTrails/pull/1057 #1057])
** This interacts with the new bundle; how do handle packing files inside the VT bundle?

=== June 17, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] current_version and reusing existing upgrades are broken ([https://github.com/VisTrails/VisTrails/issues/1095 ticket #1095])
** Could be that export to PROV is using an unflushed upgrade pipeline?
** current_version would then be correct.
** It may work to flush the actions before exporting?

=== June 10, 2015 ===
'''Updates'''
* DAT: fixed VTK issue on Linux and Mac
* Still crashes on Windows. Need help! Reminder: this works in the VisTrails spreadsheet (QCellPresenter), although no widget get changed there during a drag
** Is it a VTK bug?
** Is it simply impossible to change widgets during the drag, should we do it a different way?
** Did I miss something that is done in VisTrails but somehow not in DAT?
** Low prio, UV-CDAT doesn't run on Windows anyway

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 Updated pull request])
* Single instance code and batch mode

=== June 3, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 pr])
** Requires fixes to command line parameters, Output modules, and batch mode
** How to test this
** Updated missing/outdated flags
** Fixed view issues when generating graphs
* [TE] batch mode
** SpreadsheetOutput not enabled in batch mode. Should we check is_running_gui instead?
** Other instance setting flags from caller
** Is graphsAsPdf replacing spreadsheetDumpPdf?
** graphsAsPdf true by Default?
** Batch mode executing by default (Not needed when generating graphs)
** Re-added workflowInfo as withWorkflowInfo for writing graph and xml workflow
** [DK] batch mode should be outputting to files or stdout, shouldn't always trigger SpreadsheetMode
** execute flag, maybe make execution the default and allow a "--no-execute" if you only want to capture graphs, for example

=== May 27, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] API question
** http://lists.vistrails.org/pipermail/vistrails-users/2015-May/000357.html
* Status of DAT
** Can add VCS plot to DAT but need to work on configuration windows
** Documentation for graphics templates for UV-CDAT/vcs?
* Qt support?

=== May 20, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Reviving the DAT, integrating scripting & porting UV-CDAT!
** On [https://github.com/VisTrails/DAT GitHub] ([https://github.com/VisTrails/DAT/issues issues])
** Merging 2 years of development taking longer than expected, but getting there. The plan is to get the patches in VisTrails and never fork again, we never want to get in UV-CDAT's situation (and don't need to).
** VTK cell works fine on Linux but there was flickering on Mac & Windows before; still issues on Mac (Windows status unknown)
** Can get a VCS plot soon (but will need VTK cell fix)
** Integrate in UV-CDAT's build system (so we have cdms, VCS, ...) -> RR can do this, low priority
** How do we integrate scripting?
*** We want to be able to seamlessly make changes to a plot by changing Python code
*** Define new plots by entering Python code without writing modules/packages?
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 13, 2015 ===
'''Updates'''
* [RR] Test skipping whitelist ([https://github.com/VisTrails/VisTrails/pull/1069 #1069]) -- low priority
* [RR] Custom matplotlib modules can't be compatible with both 2.1 and 2.2 ([https://github.com/VisTrails/VisTrails/issues/1067 #1067]); should be fixed for ALPS ([https://github.com/VisTrails/VisTrails/issues/1070 #1070])

'''Items to Discuss'''
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 7, 2015 ===
'''Updates'''
* [RR] Export/import workflow to Python working!

'''Items to Discuss'''
* [Claudio] UV-CDAT
** The UV-CDAT project is the biggest user base of VisTrails
** VisTrails package management provides a lot of friction towards people plugging in their code
** Need to make it easy to integrate your random Python scripts in the system without having to deal with all the boilerplate, at least in the first step
** [RR] argues that modules are still good; UV-CDAT shouldn't move towards a purely script-based backend
** [RR] export/import with Python could reduce a lot of that friction by allowing 1) to edit workflow as Python 2) to open up boxes automatically if needed code doesn't match actual modules
** ...

=== April 29, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] <strike>Abstractions</strike> subworkflows status ([https://github.com/VisTrails/VisTrails/labels/subworkflows tickets])
* [RR] matplotlib compatibility (2.1 & 2.2), [https://github.com/VisTrails/VisTrails/issues/1067 #1067]
** RR to try and fix ALPS matplotlib modules

=== April 22, 2015 ===
'''Updates'''
* 2.2.0 has been released!
* Windows issue (via email from Ryan)
** issue with manifest file (may be a new file in VTK6?)
** Tommy has regenerated new Windows builds
* Binaries, pypi, and conda released
* [RR] Export as script
* Python sources using VTK need to switch to SetInputData (users should be aware of this)

=== April 15, 2015 ===
'''Updates'''
* Ready for 2.2.0 (apart from binary/deps issues)
** Missing some libs (scikit-learn, tej, tdparser, SQLAlchemy+connectors
** Windows: runvistrails.py is no longer used, so the PATH is wrong
** Windows: pip is broken, but it probably wouldn't work anyway because of permission issues (disable this?)
* Queries, upgrades and getPipeline() usage ([https://github.com/VisTrails/VisTrails/issues/1054 #1054])
** Getting a pipeline with getPipeline() is not safe: it might return an invalid pipeline
** This is used in many places throughout the code, like queries
** Upgrading would require going through the controller, but that creates new actions
* [TC] Avoid copying a module's output if it's used as input by exactly one downstream module ([https://github.com/VisTrails/VisTrails/issues/1060 #1060]) (useful for big numpy arrays you can update in-place)

=== April 8, 2015 ===
'''Updates'''
* [DK] Merged RR's changes for output modules (1012 and 1013)
** RR will merge remaining changes, then create v2.2 branch!

'''Items to Discuss'''
* BNL need numpy array to VTK image
** Looks like VTK has some helpers for this
** We will help if issues arise
** Will contribute back to VisTrails package
* Upgrade issue: [https://github.com/VisTrails/VisTrails/issues/1017 #1017]
** Automatic upgrades should happen between versions of provided upgrades
** Our existing upgrades work around this so it doesn't need to be 2.2.0
* Corner-case VTK modules
** No longer need VTKCell input port, so don't interfere with registry and API anymore
** Still work weirdly, people probably shouldn't use them
** But we have lots of clunky modules since we wrap the whole of VTK; some people might rely on this and know how to use them, let's keep them anyway
** Ready for 2.2.0

=== April 1, 2015 ===
'''Updates'''
* [RR] UV-CDAT: bugfixing for 2.2, long-term plans: implement scripting import/export in VisTrails, port to UV-CDAT
* Possibly, try to move to regular VisTrails to use new features

'''Items to Discuss'''
* 2.2 release: nothing much is pending anymore, release next week?
** [TE] vtkExporter classes [https://github.com/VisTrails/VisTrails/issues/1032 #1032]
** [RR] Hiding upgrades in version tree might make it (or might be 2.2.1 so we can test it out) [https://github.com/VisTrails/VisTrails/issues/949 #949]
** Output modules changes to go in
* add note to documentation about order of parameters in VTK
* add issue about exporter upgrades if not already there

=== March 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* 2.2 release
** Checklist on Github: https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist
** Review output modules
** RR has a couple more issues to fix
** Ready to go -- sign app package for OSX? [https://github.com/VisTrails/VisTrails/issues/984 #984] We need access to the Apple Membership team

=== March 18, 2015 ===
'''Updates'''
* [TE] VTK6 works

'''Items to Discuss'''
* [RR] Release v2.1.5 with backported tabledata?
** MTA example needs updated tabledata (for JoinTables)
** Google Maps package still not available
* [RR] Work torward v2.2.0?
** changes:
*** new persistence
*** API changes
*** output module changes (upgrades?), maintain cells but try to upgrade
*** not wrapping stuff
*** VTK6? yes
*** JobSubmission stuff?
*** relabeling for upgrades [https://github.com/VisTrails/VisTrails/issues/949 #949]
** makes sense, needs the tree view code to be updated, check selection
** See [https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist 2.2 checklist]
* Discussion of [https://github.com/VisTrails/VisTrails/issues/1016 #1016]
** plumbing between outputs and output modes, how to define a mode that works for many outputs without writing for each output?

=== March 11, 2015 ===
'''Updates'''
* [RR] persistent_archive done; merge? ([https://github.com/VisTrails/VisTrails/pull/755 #755])
** note about the focus events for widgets
** TE be aware of file_archive for future binaries that include persistent_archive
* [TE] [https://github.com/VisTrails/VisTrails/pull/998 New VTK package] finished

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails? (see last week; decision needed)
** RR email to JF about this
** yes; email sent to Github
* [RR] Switching order of output ports ([https://github.com/VisTrails/VisTrails/pull/1006 #1006])
** added port specs are sorted at a separate spot (Module.*_port_specs properties) than those in the registry (which are sorted in the registry), but those two lists are just combined without respect to sort keys
** need to determine whether the two lists should be merged or remain distinct
** should make sure that order of input ports and output ports makes parallel connections for things with same order
** DK suggests breaking backward compatibility here: workflows still run, can fix easily if a problem in an existing package.
* [RR] Question about output modes ([https://github.com/VisTrails/VisTrails/pull/1007 #1007]), how to integrate in API ([https://github.com/VisTrails/VisTrails/pull/24 #24])
** Should ImageFileMode be removed? ("image" is not a mode, "file" is)
** ImageOutput missing?
** Feel free to change how formats works
* [TE] Test suite segfaults on Fedora 17 virtualbox. Install newer version? (Support ended in 2013)

=== March 4, 2015 ===
'''Updates'''
* [TE] VTK wrapper
** Works on VTK 5.10
** Still need to test VTK 6
** New general wrappers for python functions and classes

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails?
** When [http://i.imgur.com/UTY2qfg.png filing a pull request] from UV-CDAT/VisTrails, VisTrails/VisTrails is selected by default
** People keep forgetting to change the default ([https://github.com/VisTrails/VisTrails/pull/956 #956] [https://github.com/VisTrails/VisTrails/pull/968 #968] [https://github.com/VisTrails/VisTrails/pull/999 #999] [https://github.com/VisTrails/VisTrails/pull/1000 #1000] [https://github.com/VisTrails/VisTrails/pull/1003 #1003] [https://github.com/VisTrails/VisTrails/pull/1004 #1004] [https://github.com/VisTrails/VisTrails/pull/1005 #1005])
** Only way to change that is to not have it marked as a fork of VisTrails/VisTrails
** Github staff [https://gist.github.com/remram44/b364c24ef1e462ce6e2f can make that change for us]; should we do it?
** Juliana: comments on this? visibility vs. convenience/annoyance for developers
* [RR] What about [https://github.com/VisTrails/VisTrails/issues/991 #991]?

=== February 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] vtkviewcell for infovis support, can we unify with VTKCell?
** need to test this
* [TE] vtk wrapping
** Mostly finished
** VTK 5.10 produce incorrect results with old wrapping
*** Old wrapper is based mostly on VTK 4
*** Most vtk_examples affected
*** [http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Replacement_of_SetInput]
*** should be able to upgrade from SetInput to SetInputData (need to drop GetOutput and replace with self ports)
*** can we change vtkInstance to just return self and not wrap things
** terminator example not working under 5.8?
* How does VTK wrapping fit into general wrapping framework?
* [RR] new persistence package

=== February 18, 2015 ===
'''Updates'''
* [RR] New VisTrails API and IPython integration ([https://github.com/VisTrails/VisTrails/pull/24 #24])

'''Items to Discuss'''
* [TE] VTK wrapping
** [https://gist.github.com/rexissimus/16b74693545b5e7c1035 Benchmarking vtk package]
*** Old: 24.7 seconds
*** New: 10.5 seconds (Except first time that adds 8 sec)
**** The parsing that calls is_abstract (that tries to instanciate all vtk classes) is now only run the first time.
**** get_items_from_sigstring takes 2 seconds, maybe we can use a lookup dict for already computed sigstrings?
** Now using a general python function wrapper
*** VTK classes are wrapped into python function that does not depend on vistrails
*** VTK functions can be executed without vistrails
*** The spec maps functions into vistrails modules, but can also describe wrapping
*** A general python function wrapper that supports
**** kwarg inputs
**** single, list, dict outputs
**** callback for progress reporting
**** temporary file generator for using FilePool
**** optional output generation
*** Creating specs:
***** Create spec by hand
***** Auto-create spec outline (TODO) and manually finish it
***** Dynamically create spec (VTK)
***** Implement documentation wrappers (Can use scikitlearn wrapper to wrap numpydoc) (TODO)
***** Classes as bad functions needs to be wrapped in new functions before they are wrapped. This is different for each package.
****** Classes is hard: Like VTK, and matplotlib. Scikit-learn does still not wrap classes
***** Spec diffing and patching could be done using code from matplotlib.
** Still needs upgrades from old VTK package
*** Is it possible to dynamically wrap functions, e.g, you see a SetFunc and just remove the 'Set' prefix. Or do you need to create a complete mapping?

=== February 11, 2015 ===
'''Updates'''
* Update from Friday's meeting
** discussed VisTrails internals
** discussed wrapping
*** xml discussion, hard to modify because tied to db code
*** TE has made it possible to add the schema-defined attributes to the intermediate representation
*** higher-level operations on the port specs
** make sure the simple case works
*** [JF] take a simple package with documentation and figure out what the base case for wrapping is

'''Items to Discuss'''
* [TE] VTK wrapping
** Dynamic loading works
** Reading XML is fast enough, but [https://gist.github.com/rexissimus/8272d3c776ccfa115d82 unserializing data is slow]
** Working on patterns for patching
** Matplotlib has many advanced patterns like argument ordering, nested arguments, alternateSpecs, output types.
*** Having all this in a general wrapper might confuse users?
** [RR] Delay module (except for identifiers) until you need it---e.g. don't deal with port specs, etc. until necessary
* Scripting Support [https://github.com/VisTrails/VisTrails/pull/950 #950]
** [RR] Issue with getting code from modules
** Design a simple solution
** [JF] Couldn't you use modules as black boxes without conversion, just to call into modules/subworkflows easily from e.g. IPython?
*** [RR] This is a job for the API, and a very separate use case. See [https://github.com/VisTrails/VisTrails/pull/24 #24]

=== February 4, 2015 ===
'''Updates'''

'''Items to Discuss'''
* Wrapping
** Format to use? Currently XML (like current matplotlib)
*** JSON and YAML have simple "to python dictionary" methods
*** But don't stream
*** YAML a lot easier for humans
** [DK] vtk-new-package also changes parameter names, creates enumerations
*** intermediate schema needs to be extensible
*** packages will want to store there specific infos for compute() method generation
*** also might have specs-altering info, like matplotlib's alternateSpec
** representation to code , registry already has schema for some aspects
** [RR] We might want to see if Module subclasses can be created lazily
*** no need to create all the classes just to register them in the registry and never actually use most of them
*** future effort
* [RR] Where should VisTrails packages live?
** tej installs as 'vistrailspkg.tej', TE installed it as 'userpackages.tej'
** Currently, standard packages are 'vistrails.packages.', user packages are 'userpackages.' and packages loaded through pkg_resources might be anything
** [RR] Use 'vistrailspkg.' everywhere?
** Long-term effort to simplify package distribution/installation (and have VisTrails get them automatically?)

=== January 28, 2015 ===
'''Updates'''
* T. Caswell to come visit on Fri 6 to discuss wrapping work

'''Items to Discuss'''
* [TE] New VTK wrapping
** Current code by DK seems a good deal faster
** Generates XML that can be patched/tweaked, generates Python code from it, VisTrails only loads generated Python code
** RR would rather have VisTrails load intermediate representation (= XML) directly, wants to make sure this is not slower
** The goal is to turn the intermediate step into something generic that would be used for every wrapped package (vtk, numpy, matplotlib, sklearn, java) instead of each having its own
** TC has its own code at [https://github.com/Nikea/VTTools/blob/master/vttools/wrap_lib.py github:VTTools] which parses numpy docstrings and generates modules, doesn't yet handle classes or persist anything
* Web crawler
** Right now, TE starts jobs for "start crawler", "stop crawler", "install classifier"
** RR would rather have the crawling be a job as far as VisTrails and tej are concerned
** The whole thing would be one pipeline: load examples, train classifier, start crawler [check for job, kill previous one, upload model, start processes], get snapshot, visualize
*** Need some support in tej and job submission system: long-running jobs, stop a job (wait for it to finish?), restart a job even though results are cached

=== January 21, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Unified wrapping method discussion [https://github.com/VisTrails/VisTrails/issues/991 #991]
** TE to work on reusable method with intermediate representation, starting with VTK
* [RR] Examples for scikit-learn: JF has an old example using Weka with parameter exploration (not currently in source tree)
** AM's examples are enough
* [AM] scikit-learn package is done, merge it in? [https://github.com/VisTrails/VisTrails/pull/955#issuecomment-70286788 #955]
** RR will merge
* [RR] What should copyright headers say? [https://github.com/VisTrails/VisTrails/pull/994#issuecomment-70173935 #994]
** Let's keep everything in there: Utah/Poly/NYU

=== January 14, 2015 ===
'''Updates'''
* [TE] Working on classifier
* [RR] Scripting integration, work in progress

'''Items to Discuss'''
* [RR] Unified wrapping method discussion ([https://github.com/VisTrails/VisTrails/issues/991 #991])
** Let's talk next week, [AM] and [DK] are not here

=== January 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* make sure that we address critical issues, questions, and pending review branches in a timely manner
* scripting support
** [RR] no issues if we want to just keep annotations in the generated code to allow the link back to a workflow
** [RR] can translate from workflow to script, working on script to workflow
** will work for parameter value changes, structural changes require changes to the annotations
** need to publish best practices here
** would be cool to do looping in scripts (easier interface than with workflows)
* notebook support (convert form notebook to workflow)
** RR will sync with FC on this
* Issue with console in built-from-scratch
** [TC] iPython rearranged some of the completion stuff in 2.2 and 2.3
** binary has old version of iPython -> 1.0.0, should we update?
* [TC] automated wrapping of numpy and scipy
** discovered a bunch of malformed documentation in numpy and scipy
** has github repo for vistrails tools
** example modules wrap a bunch of R stuff (not baked in, just how things are)
** will be pushing wrapping logic up
** port names forbidden (window and domain)
** have an import hook to get from yaml directly to VisTrails Modules
** should work for any python modules with well-formed numpy docstrings.
* [Action] should make it clear in documentation that Constant now means serializable not that the value doesn't change (e.g. List)
* [TC] might be interesting to try to build components of matplotlib and accumulate in figure (long-term project, but thinking about how this might work)
* [TE] build and build scripts
** completely automatic, buildbot
** need to set the build machines for the environment we want for the binary
** would virtualenv work here?
** [TC] anaconda can pin versions, potential path to test different configurations
** Q: upload nightly binary builds? A: makes sense, make sure they are well-labeled
* sourceforge stats: e.g. http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07
* package issues (see Remi's message)
* [TE] Scope of tej
** Support single ssh commands?
** Queue can be used as a remote machine (crawler is using queue.call*)
* SourceForge stats: http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07

== Older meetings ==
* [[Development/2014]]
* [[Development/2013]]
* [[Development/2012]]
* [[Development/2011]]
* [[Development/2010]]

Development

2016-04-20T14:52:17Z

Tommy: /* April 13, 2016 */

<div class="nonumtoc toclimit-1">
__TOC__
</div>

See also the [https://github.com/VisTrails/VisTrails/wiki/Development Github wiki]

== 2016 ==

=== April 20, 2016 ===
'''Updates'''
* Merged upgrade fixes
** Now has infinite loop test
** loop test now correctly loops 5 times
*** remap_module used wrong (current) package version when creating ModuleDescriptor
* Fixed multi-step group upgrades (PR: [https://github.com/VisTrails/VisTrails/issues/1168 #1168])

'''Items to Discuss'''
* New bugfix release
** Merge usagestats
** Needs to finalize survey

=== April 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Chaining upgrades done ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Replace "Upgrade" description annotation with "upgraded_from" annotation to identify which tags to hide?

* [TE] Iterating handle_invalid_pipeline ([https://github.com/VisTrails/VisTrails/pull/1165 #1165])
** Not based on [https://github.com/VisTrails/VisTrails/tree/chain-upgrades-loop chain-upgrades-loop]
** Cherry-pick test to preserve source?
** Need maxPipelineFixAttempts option?
*** The code is now smarter about recursion, so max attempts will "probably" never be reached.
** Need [https://github.com/VisTrails/VisTrails/commit/0ef0667426937eddb1d1c1e397f0657ffec039a9 debug messages]?
*** Would need to be moved into handle_invalid_pipeline

=== April 6, 2016 ===
'''Updates'''
* [TE] Query View improvements
** Done except for displaying "Version Info" and #1164
* [RR] Working on finishing new interpreter (finally!)

'''Items to Discuss'''
* [TE] Chaining upgrades ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Try latest upgrade first, then previous.
** If all fail, select latest upgrade?

=== March 30, 2016 ===
'''Updates'''

'''Items to Discuss'''

* [TE] Query View improvements
** Unified do_version_switch and get_upgrades as validate_version()
** Problems with query view using its own controller
*** Fixed module info not being displayed for query results
*** Still no version info for query results
*** Still an issue with version query view not being updated

=== March 23, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Usage reporting almost ready to go
** Need to record whether specific features are used: paramexpore, mashup, query
*** [DK] Record if LaTeX extension is used? But hard to distinguish from direct batch invocation
** How to record size of vistrail?
*** [DK] IdScope already walks over vistrail, use that
*** but total number of modules and versions doesn't give an idea of average size of individual pipelines

=== March 16, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Upgrades in Query Mode
** Now using code similar to do_version_switch
*** Uses handle_invalid_pipeline
*** Differences: Not using current_pipeline, flushes changes
*** New controller method get_pipeline optimized using cached pipelines (but not current_pipeline)
*** Integrate to avoid repeated code?
*** Use this for query mode?
* [TE] VisTrails 2.2.4 ready for release?
** tej package updated. Others?
* [JF] upgrades and the version tree
* [JF] provenance in Jupyter
* [DK] bundles: [https://github.com/VisTrails/VisTrails/pull/1092 #1092]

=== March 9, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixing search mode
** String query now matches all by default
*** This caused pipeline queries to never match
** String query can search: User/Notes/Tagname/Time/Module name
*** Should we search module names by default? (Disabled by default because it is expensive)
*** Fixed notes search
** '>' parameter queries in documentation but has been removed
** Fixed module matches for upgraded pipelines (By not upgrading pipeline)
*** Upgrades still a problem
*** Add "Upgrade all menu option?" (Or upgrade all on open when `hideUpgrades`)
*** [JF] Allow search on past tags

* [TE] Create new bugfix release
** Finish querying
** Path issue on windows

* [DK] Look into sqlalchemy and new bundle branches

=== March 2, 2016 ===
'''Updates'''
* [TE] Fixed cache bug with port specs
* [TE] VisTrails Next
** Most packages now work
** No qgis for Python 3

'''Items to Discuss'''
** Always dereference symlinks? [https://github.com/VisTrails/VisTrails/issues/1146 #1146]

=== February 23, 2016 ===
'''Updates'''
* [TE] Fixed PythonSource 100% CPU bug
* [TE] VisTrails Next
** Updated [http://opendap.co-ops.nos.noaa.gov/axis/webservices/wind/ NOAA Web Service] examples
*** Now uses REST service, tabledata, and Google Maps
*** Web Service replaced with DownloadFile

'''Items to Discuss'''
* [RR] Couple of fixes are in for API, and tej&reprounzip on the Mac binary. Also new release of tej, and working on anonymous usage reports.
** New 2.2 release soon?
* [RR] Anonymous usage reports
** Sends out info like number of modules & versions, packages used, Python & libs versions, execution time, specific features [https://github.com/VisTrails/VisTrails/pull/1154 #1154]
* [JF] Bring in noWorkflow to track variable dependencies, for the considered Jupyter integration?
* noWorkflow - provenance for python scripts
** Recent work on tracking dependencies
* Also integrates ReproZip with Jupyter
** [http://mybinder.org mybinder]
*** Use with ReproZip to automatically build Jupyter notebook interfaces
* Daves comments on Jupyter integration
** It is possible to identify cell order on the server side
** Not trivial to track order of cells on client side
* How does Galaxy workflows relate to VisTrails?
** Packaging in Galaxy is hard
** Galaxy for biomedical workflows, difficulty making it general
* Action items
** How difficult to track cell dependencies in Jupyter notebooks?
** Use noWorkflow to track cell dependencies?
** How difficult to modify mybinder to use ReproZip packages?

=== February 17, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixed Group memory usage
** Modules in groups are supposed to be freed when done executing
*** Prevented by logger that stored references to the modules (fixed, now using id(module))
*** Prevented by list iterator bug that stored list of modules on the 'self' port bug (fixed)
* [TE] VisTrails Next
** Removed deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** PythonSources will be upgraded
*** Fixes for Python < 3
*** fixes for VTK < 6
** TODOs
*** Remove RemoteQ
**** Port Hadoop to tej (Already have pbs)
*** Merge package wrapper
*** Finish SQLAlchemy branch
*** Finish new bundle branch
** [JF] Will contact Jeff and Matthias about moving to Python 3
* [JF] Query by Example is broken
* [JF] VisTrails Data Cleaning Project
** Use VisTrails to process and explore task-specific data while keeping provenance.
** Remi's Idea
*** Use VisTrails as the backend in a Jupyter notebook
*** Overcome problems with executing cells in random order
**** Interesting research topic, but little interest has yet been noted
*** Interesting to study how such a notebook would be used (Is there notebook usage data available?)
*** Impose restrictions to notebook cell boundaries
*** It will only work for functional operations
*** Can we fix, or detect, non-functional (mutating) operations?
*** Analyse code and data flow and see if it mutates data in unexpected ways?
*** Mutable operations can be created in many ways in Python
* Next meeting Tuesday 11:30

=== February 10, 2016 ===
'''Updates'''

'''Items to Discuss'''
* VisTrails Next
** Test suite passes
*** Python 3 less deterministic, module upgrade order random.
** [RR] updating packages: Reprounzip (pushed), tej, persistent_archive, ...
** All of our packages should run fine :)
** VTK thumbnail comparison works
*** Rendering bug on some systems
**** QVTKCell now inherits QGLWidget
*** Old thumbnails had wrong height due to spreadsheetwindow being too small
**** Fixed by regenerating thumbnails
*** Silenced deprecation messages when generating modules
*** Many new classes in VTK 7
** Remove deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** Will break existing PythonSources
**** Try to upgrade?
*** Old-style packages
**** Or only allow a new style, like __init__.py renamed to info.py? (merge with identifiers.py?)
***** Read info.py without importing package?
*** Fixes for Python < 3
*** Fixes for Qt < 5
*** fixes for VTK < 7
*** Remove self port?

=== February 3, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] [http://lists.vistrails.org/pipermail/vistrails-users/2016-January/000402.html Rendering a .pvd (ParaView) file?]

* VisTrails Next
** All tests but thumbnail comparison passes
** Still issues with gui and more packages needs to be tested
** PythonSource and MplSource upgraded with lib2to3
** Keep contrib packages? Update?
** [https://blog.kitware.com/vtk-7-0-0/ VTK 7 is released]
*** Supports Python 3
*** Will hopefully get into conda and others soon
*** Deprecates a bunch of modules

* [https://travis-ci.org/VisTrails/VisTrails/builds/106743348 Travis builder] for VisTrails Next
** Runs!
** Uses conda
*** Many levels of requirements
**** apt packages
**** conda packages
**** python packages in requirements.txt
**** python packages in setup.py
*** Can probably drop conda. Default builder does not have Qt5, but beta builder do!
*** But useful if we want to use conda in our own build process.
** Lots of errors I do not get locally?

* [http://goo.gl/forms/Z4HBrwaBWL User Survey]
** Have you used any alternatives to vistrails?
*** Relevant? More options?
** How often do you use any of these particular features in VisTrails?
*** Add/Remove alternatives?
** How important would you rank the following potential improvements to VisTrails?
*** Add alternatives?

=== January 27, 2016 ===
'''Updates'''
* New interpreter
** Working prototype soon
** Looping not completely done (and port combination mode: pairwise/cartesian...)
** Need to integrate with VisTrails
*** Compatibility with existing modules
*** Use log controller
*** Want to cache at multiple levels (whole stream/single element of stream)
*** Non-runtime attributes of modules (cache check, automatic conversion check, constant from/to string)

'''Items to Discuss'''
* User Survey

* ZMQ failing on windows (vistrails-users)

* [TE] [https://github.com/VisTrails/VisTrails/pull/1143 Python 3 branch]
** Testsuite almost passes
*** Failing are unicode filenames, some users guide examples, and thumbnail comparisons.
** Fixed issues
*** Signatures are now bytes (convert to string to show in widget)
*** Cannot compare different types, e.g., (None < 1)
**** PortSpec.depth and min/maxConn could be None. (Backport!)
**** cell.row could be None
*** Lots of unicode/bytes fixes to serializations
**** We have encryption implementations in the code! (keychain)
*** Lots of small fixes to package method differences
** Current issues
*** logging widget empty?
*** version tree signals messed up
*** provenance view legend icons black
*** Text do not fit in some widgets
*** VTK thumbnail comparison fails
**** VTK Cells have some faces in wrong direction?
**** Because running in VM?
** Installing on Ubuntu LTS/Latest Mint
*** Install latest matplotlib from pip
*** Install VTK 7.0.0rc2 from source
*** No QtWebEngine binary (controversial) (Must install sip/PyQt5/Qt5 from source)

=== January 20, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Backporting features from Python 3 + PyQt5 + Qt5
** Merged unicode with master ([https://github.com/VisTrails/VisTrails/tree/unicode unicode])
*** One unicode test failing
*** Problem saving to xml
** Used [http://python-future.org/ python-future] to run futurize stage 1 to update legacy (pre 2.6) code ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized unicode-futurized])
*** Updates print to functions 'from __future__ import print_function'
*** Updates exception calls to use 'as'
*** removes most usages of 'long' (mostly used unnecessarily)
**** Only needed for 32-bit support
*** Fixes relative imports (from __future__ import absolute_import)
** Fixing code that is deprecated in Qt 4.8 and removed in Qt 5 ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized-qt5 unicode-futurized-qt5])
*** Updated all signals to new-style
* If we go 2 to 3, this could break packages
** means we should schedule any package format changes for the same time
** e.g., imports should be unrelated to code path (function to load module from package identifier?) (take them out of vistrails.* [https://github.com/VisTrails/VisTrails/pull/1002 #1002])
** any structural changes (e.g. the __init__ versus init thing) (RR thinks it makes sense, though having both named "init" is unfortunate)
** putting package identifier as xml?
*** Python not so bad, plus some stuff in there is Python code (checking dependencies)
** version the APIs?
*** RR planning on versioning vistrails_module.Module, no point versioning the whole package?
* file formats on 2 to 3:
** no real translation/upgrade, but non-ascii values that work on 3 won't load in 2

=== January 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://gist.github.com/rexissimus/dfd27e466427529c385c Porting to Python 3 / PyQt5]
** Basic GUI and execution works
** Minimal work to support 2to3
** Hard to support both PyQt4 and PyQt5

=== January 6, 2016 ===
'''Updates'''
'''Items to Discuss'''
* Updating VisTrails dependencies
** Successfully built [https://gist.github.com/rexissimus/f1a1aada7de1c00a57c7 Win7-64/Python3/PyQt5/Qt5/WebEngine/VTK7]
*** VTK 7 is the first supporting Python 3 but is only in release candidate phase.
**** Next version of VTK 6 is rumored to support Python 3
**** There is a development branch of VTK 6 supporting Python 3
*** Can travis build this?
**** We can skip tests for WebEngine and VTK if needed
** Python 3 [https://python3wos.appspot.com/ showstoppers]
*** No MySQL-python (sqlalchemy supports mysql through other drivers)
*** No suds (there are active forks but we could also drop support?)
* Options for python2/3 support:
** Interpreter could be python2/python3 based on packages
** six layer works but not the easiest to maintain (e.g. in reprozip)
* Drop support for win-64
* Update copyright headers to 2016

== 2015 ==

=== December 30, 2015 ===
'''Updates'''
* Bokeh package finished
** Can output to Browser/IPython/Spreadsheet (Limited functionality in spreadsheet)
'''Items to Discuss'''
* Updating VisTrails dependencies
** Bokeh needs QWebEngine (Chromium) in Qt5 which requires PyQt5
*** Many plotting libraries only work in browsers
*** But Chromium may be a big and controversial dependency
*** Or create a browser version of the spreadsheet?
** Some users have requested Python 3
** Not backwards compatible?
** Target for VisTrails 3.0 with new interpreter?

=== December 16, 2015 ===
'''Updates'''
'''Items to Discuss'''
* Users list question
* [TE] Wrapping Bokeh
** Added bokeh property parser
*** complements numpydoc parser
*** Not all attributes are available, partially because I am using a pre-release version.
** Wrapped modules
*** bokeh.plotting finished (Backwards like matplotlib: Create plot then draw on it)
*** bokeh.charts mostly done (Missing arguments)
** QWebView mostly works (but no zooming or buttons)
*** It would be better to use external browser or QWebEngineView
** Added improvements to wrapper
*** Generalized port translations (Color/Path to native types)
*** Can use multiple docstring/property parsers simultaneously

=== December 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Looking into wrapper
** Will port TensorFlow
** Doing a pass on the wrapper code & doc
*** UX improvements
** Factorize high-level docstring parsers into core.wrapper? (sphinx, numpy, google)
** Problem with name vs module_name (fails sklearn tests because class_by_name() is broken)
** Looking into compressing specs, lazy registration of modules

=== December 2, 2015 ===
'''Updates'''
* [TE] Package wrapping
** Wrapped most of numpy/scipy using __all__
** Added class attribute and method access for classes (Can add to class or to separate inspector module)
** TODO: Document wrapping procedure

'''Items to Discuss'''

=== November 25, 2015 ===
'''Updates'''
* [RR] New interpreter is coming along
** Everything is a stream
** Task system, eventually work-stealing parallelism
** Streams no longer advance in lock-step
*** Allows for constructions like filter, join, sorted-merge
** depth>1 still to be tested, no current plan to allow this through the module interface
*** Through looping though, can do streams of streams

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapped most numpy functions (no polynomials)
** and half of scipy classes and functions
** Added functions manually from documentation (no parseable lists?)
** Focusing on data flow constructs (no property/method access for classes)
*** Using spec diff (empty for now) and dynamic parser (stores spec in .vistrails/)
** Python class/function wrapper now stable
** Add google doc parser?
*** Is there a parser available?

=== November 18, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Numpy class wrapping works
*** Basic type is List, since most types are array_likes.
*** TODO: More classes and functions
*** Some operations are in-place and some aren't, and docstring not super clear
*** [RR] It seems only methods mutate, and most have a numpy.xx function equivalent; just manually go through the methods and remove the mutating ones?
** Class wrapper is modular
*** Docstring parser and type string parser can be customized
*** Classes can have optional attribute/method ports
**** Inspectors and attribute/method modules can be created separately
** Use PythonCalc as an example
*** Can be re-implemented as a function with a parseable docstring
*** [RR] PythonCalc is just an example, and it might actually make sense to get rid of it, or do a proper math package with scalar operations (as separate modules, no combobox)
** [RR] TensorFlow to use wrapping as well
*** Very simple (only types 'tensor' & 'variable')

=== November 11, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapping numpy's classes using numpydoc (ndarray)
*** Wrapping constructor arguments, attribute getters/setters as module ports
**** Then how to access attributes afterwards?
***** Use input value port to class modules?
*** Wrap methods as modules? E.g., `ndarray.shape`.
*** Function wrapping is almost a subset of class wrapping
**** May be able to use the same parsing/execution methods
** VTK's non-getter/setter methods could be wrapped as modules
*** We could then remove extra logic in interpreter for keeping function order
** Bokeh uses autogenerated docstrings
*** We may be able to read the specification directly

* [RR] [https://github.com/VisTrails/VisTrails/pull/1138 TensorFlow package]
** Basic setup working, can execute the Mandelbrot example
** Will autogenerate the operations

=== November 4, 2015 ===
'''Updates'''
* [RR] Interpreter work requires a fix for [https://github.com/VisTrails/VisTrails/issues/1137 DB issue #1137]
* [DK] Kitware's Resonant [http://www.kitware.com/source/home/post/173]
** [https://github.com/girder/girder Girder]: data management system
** [https://github.com/Kitware/romanesco Romanesco]: execution engine, uses [http://www.celeryproject.org/ Celery] for task management
** Resonant Flow: web app for editing and executing workflows

'''Items to Discuss'''
* [TE] Added OSX Lion (10.7) VM on build machine using vagrant (seems ok with license?)
** New builds works on Lion
** Change the minimum requirement to 10.7?
* [TE] Package wrapping
* Added upgrade suggestions using 2 spec versions ([http://pastebin.com/30XUU8Gp example])
** using name edit distance to find matches
** Could use something better like port similarity for modules, and type similarity for ports
** Should write python upgrade code?
** Added spec to sklearn package
*** Can now diff spec versions and keep the spec static
*** There will be problems with downgrades and package versions

=== October 29, 2015 ===
'''Updates'''
* [TE] nightly-build-mac fixed (Needed to approve xcode license)

'''Items to Discuss'''
* [TE] matplotlib wrapper
** ported to general spec
** Diff can be used on general spec
*** Only needed minor changes
*** Fixed indexing bug that corrupted specs
*** Can now move diff tools to core/wrapper
** Add new plots?
*** New plots in mpl 1.3: eventplot
*** New plots in mpl 1.4: angle_spectrum, magnitude_spectrum, phase_spectrum', violinplot
*** No new plots in mpl 1.5 (from looking at boilerplate.py)

=== October 21, 2015 ===
'''Updates'''
* [RR] Alexis has arrived, will be working with [RR] on a more efficient interpreter

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package]
** Supporting multiple package versions
*** Check which version can be loaded [https://github.com/VisTrails/VisTrails/pull/1135 #1135]
*** We cannot show version requirements in the list of packages because old packages are loaded when importing the codepath
** Visual diff does not work well, but we can use the spec differ to see differences.
** Unifying vtk and matplotlib wrapping specs (WIP)
*** And porting matplotlibs spec differ to work on the general spec
*** Spec differ can then be used on vtk and other packages in the future
*** Will enable automatic upgrade generation
* [RR] Rework interpreter
** restore abstraction between interpreter/module code
** build looping, streaming, caching into the interpreter
** rework cache
** look into parallelism once basic functionality is there

=== October 14, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package] (adding numpydoc parser)

=== October 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/tree/fix-matplotlib-parser New matplotlib parser] (adding numpydoc parser)
** Added numpydoc attribute parser for plots.
*** TODO: Need better port spec reconciliation with call signature parser.
*** We can create a general numpydoc parser, but attribute types are unique to matplotlib.
** Needs package versioning
*** New spec will not support matplotlib < v1.4 due to changed path to axes classes.
*** Load spec version corresponding to installed matplotlib version?
*** Need version downgrades?

=== September 30, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Updating Matplotlib parser
** Matplotlib docstring parser fails on numpy docstrings
** I have [https://github.com/VisTrails/VisTrails/commit/eae8b0c16260810587e47c41cab53552cbb3cf0a added basic numpydoc parsing]
*** Only used by a few docstrings so far
*** Parsing uses many sources (class tables, signatures, ACCEPTS, method docstrings, definition parsing).
** Caswell said they were thinking about moving to traitlets, but this is not ready yet

=== September 23, 2015 ===
'''Updates'''
* [TE] VisTrails 2.2.3 released
** Also have pushed to PyPI, binstar, etc.
** Sourceforge vs. GitHub
*** should be able to host releases on GitHub
*** nightly binaries pushed to sf each night
*** old binaries?
* [TE] Re-wrapping MatPlotlib
** Keep static generation - Docstrings are brittle beween matplotlib versions
** Keep generating the executable classes - but create functions, not vistrails Modules
*** Why is there so much patching?
** Re-implemented Alternate PortSpec for InputPortSpec
*** It will now inherit specs from parent (No need to reimplement)
** Module upgrades?

'''Items to Discuss'''

=== September 16, 2015 ===
'''Updates'''
* [TE] Job Monitor tests and documentation done
** OK to leave document package in packages directory?

'''Items to Discuss'''
* [TE] Library wrapping: How to do code patching? [https://docs.google.com/drawings/d/1Sh3eOXot6v2y880jHKQrqXqAwr-0aoqYligg3z8G8MY/edit?usp=sharing Wrapping diagram]
** Insert code into module template (Old VTK code)
** Patch the library that is called (New VTK code)
** Somehow store code in spec and apply when executed?
*** Executed code needs at a minimum access to inputs, outputs, current class
*** Use standard input/output dict and obj reference that the code operates on?
*** Can this be done while keeping the execution abstract?

* Do new release now?

=== September 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* New release?
** [RR] wants reprounzip
** tej changes & doc
** job monitor & jobmixin fixes
** mongodb
** reprounzip
** warning: MplFigure type is int
** tabledata: add Reshape, DictoToTable & ListToTable, fix ListToTable with numpy arrays
** PythonSource can have same name for an input & output
** don't show spreadsheet at exit

=== September 2, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Limit autosaves? [https://github.com/VisTrails/VisTrails/pull/1126 #1126]

=== August 26, 2015 ===
'''Updates'''
* [TE] Added Job support to Parameter Explorations (Requested by Colin), and Mashups
** specify job ids, need to specify different ids for parameter explorations since they have the same version id
** how to deal with parameters passed in on command line
* [General] provenance: should be creating a new version when we execute workflow with changed parameters?
** currently, custom_params annotation stores this in provenance currently
** [RR] API doesn't record provenance if passing in parameters: http://git.io/vsAA5
'''Items to Discuss'''

=== August 19, 2015 ===
'''Updates'''
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [TE] Working on Job Monitor documentation

'''Items to Discuss'''
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [TE] Stop testing VisTrails 2.0?

=== August 12, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Build broken on Travis; because of IPython 4 released today? ([https://travis-ci.org/VisTrails/VisTrails/builds/75279795 build 992]; [https://github.com/VisTrails/VisTrails/issues/1123 #1123])

=== August 5, 2015 ===
'''Updates'''
* [TE] Fixes to Jobs
** Could not delete jobs
** Could not run job in group
** Job not reset when calling ModuleSuspended
** Added deleting job from context menu
* [RR] Writing documentation for everything [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

'''Items to Discuss'''

=== July 29, 2015 ===
'''Updates'''
* RR still looking into new interpreter thing
** Goal is to take out scheduling logic from Module so it can be split in multiple processes, and so that smarter strategies can be added in time
** This means some work on packages
** Spreadsheet can live in kernel process? Still some UI stuff that will take work (changing configuration, persistent archive's viewer, ...)
* [TE] Problems running examples [https://github.com/VisTrails/VisTrails/pull/1111 #1111]
** Testing of more examples requires additional packages on the test machines.
** Fixed faulty line-ending in PythonSource:s failing on Python 2.6.
** Test suite now testing SUDSWebServices (If web service is down, test suite will fail)
** preferences.py test failed reloading 'dialogs' package, switched to using 'URL'.

'''Items to Discuss'''

=== July 22, 2015 ===
'''Updates'''
* [TE] mailing lists back online
* [TE] Working on [https://github.com/VisTrails/VisTrails/issues/1107 #1107]
* [RR] Working on ReproZip package

'''Items to Discuss'''
* [RR] MongoDB package [https://github.com/VisTrails/VisTrails/pull/1106 #1106]
* [RR] Example for tej docs? [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

=== July 15, 2015 ===
'''Updates'''
* 2.2.2 released

'''Items to Discuss'''
* RR is considering executing everything in an IPython kernel (i.e. separate Python interpreter, like the one spawned for a notebook)
** It's a separate process that we can restart without restarting the app/gui
** We can isolate the execution environment (e.g. for the server)
** We can run the whole thing remotely (if your data is elsewhere, just run VisTrails locally and the pipeline elsewhere)
** Pipeline execution no longer makes the interface hang, it just makes the kernel hang (but that's fine)
** We can use notebooks as modules (probably way nicer than the PythonSource module)
** We can run multiple kernels so long as the ports carry things that are serializable
*** meaning we can put the multithreaded-interpreter without all the hacky parts it has now
*** we can run IPython kernels in all the languages IPython supports, [https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages currently 46]

=== July 8, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Buildbot github hook not working after IP address change
* [TE] No reference to VistrailsApplication ([https://github.com/VisTrails/VisTrails/issues/1103 #1103])
** [RR] Added PR [https://github.com/VisTrails/VisTrails/pull/1104 #1104]
* [TE] Reopening VT file after saving with bundled subworkflow won't offer subworkflow upgrade ([https://github.com/VisTrails/VisTrails/issues/1102 #1102])
** allow manual delete to fix right now
** fix this on top of the use-uuid branch
* [TE] Release VisTrails 2.2.1? ([https://github.com/VisTrails/VisTrails/blob/v2.2/CHANGELOG CHANGELOG])
** [https://github.com/VisTrails/VisTrails/pull/1093 output-modules-use-global-dir]
** [https://github.com/VisTrails/VisTrails/milestones/version%202.2 Current issues for 2.2]

=== July 1, 2015 ===
'''Updates'''
* [TE] PROV fixed
* [TE] Working on subworkflow issues
* [RR] Considering reworking the controller (log vs exception problem, retained upgrades causing interferences) and also the interpreter (IPython?)

'''Items to Discuss'''

=== June 24, 2015 ===
'''Updates'''

'''Items to Discuss'''
* UV-CDAT
* [TE] Can a cyclic workflow be valid? ([https://github.com/VisTrails/VisTrails/issues/1097 #1097])
** focus on disabling the ability to create cyclic pipelines because more things break than just this with a cyclic pipeline
* [RR] Relative paths ([https://github.com/VisTrails/VisTrails/pull/1057 #1057])
** This interacts with the new bundle; how do handle packing files inside the VT bundle?

=== June 17, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] current_version and reusing existing upgrades are broken ([https://github.com/VisTrails/VisTrails/issues/1095 ticket #1095])
** Could be that export to PROV is using an unflushed upgrade pipeline?
** current_version would then be correct.
** It may work to flush the actions before exporting?

=== June 10, 2015 ===
'''Updates'''
* DAT: fixed VTK issue on Linux and Mac
* Still crashes on Windows. Need help! Reminder: this works in the VisTrails spreadsheet (QCellPresenter), although no widget get changed there during a drag
** Is it a VTK bug?
** Is it simply impossible to change widgets during the drag, should we do it a different way?
** Did I miss something that is done in VisTrails but somehow not in DAT?
** Low prio, UV-CDAT doesn't run on Windows anyway

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 Updated pull request])
* Single instance code and batch mode

=== June 3, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 pr])
** Requires fixes to command line parameters, Output modules, and batch mode
** How to test this
** Updated missing/outdated flags
** Fixed view issues when generating graphs
* [TE] batch mode
** SpreadsheetOutput not enabled in batch mode. Should we check is_running_gui instead?
** Other instance setting flags from caller
** Is graphsAsPdf replacing spreadsheetDumpPdf?
** graphsAsPdf true by Default?
** Batch mode executing by default (Not needed when generating graphs)
** Re-added workflowInfo as withWorkflowInfo for writing graph and xml workflow
** [DK] batch mode should be outputting to files or stdout, shouldn't always trigger SpreadsheetMode
** execute flag, maybe make execution the default and allow a "--no-execute" if you only want to capture graphs, for example

=== May 27, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] API question
** http://lists.vistrails.org/pipermail/vistrails-users/2015-May/000357.html
* Status of DAT
** Can add VCS plot to DAT but need to work on configuration windows
** Documentation for graphics templates for UV-CDAT/vcs?
* Qt support?

=== May 20, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Reviving the DAT, integrating scripting & porting UV-CDAT!
** On [https://github.com/VisTrails/DAT GitHub] ([https://github.com/VisTrails/DAT/issues issues])
** Merging 2 years of development taking longer than expected, but getting there. The plan is to get the patches in VisTrails and never fork again, we never want to get in UV-CDAT's situation (and don't need to).
** VTK cell works fine on Linux but there was flickering on Mac & Windows before; still issues on Mac (Windows status unknown)
** Can get a VCS plot soon (but will need VTK cell fix)
** Integrate in UV-CDAT's build system (so we have cdms, VCS, ...) -> RR can do this, low priority
** How do we integrate scripting?
*** We want to be able to seamlessly make changes to a plot by changing Python code
*** Define new plots by entering Python code without writing modules/packages?
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 13, 2015 ===
'''Updates'''
* [RR] Test skipping whitelist ([https://github.com/VisTrails/VisTrails/pull/1069 #1069]) -- low priority
* [RR] Custom matplotlib modules can't be compatible with both 2.1 and 2.2 ([https://github.com/VisTrails/VisTrails/issues/1067 #1067]); should be fixed for ALPS ([https://github.com/VisTrails/VisTrails/issues/1070 #1070])

'''Items to Discuss'''
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 7, 2015 ===
'''Updates'''
* [RR] Export/import workflow to Python working!

'''Items to Discuss'''
* [Claudio] UV-CDAT
** The UV-CDAT project is the biggest user base of VisTrails
** VisTrails package management provides a lot of friction towards people plugging in their code
** Need to make it easy to integrate your random Python scripts in the system without having to deal with all the boilerplate, at least in the first step
** [RR] argues that modules are still good; UV-CDAT shouldn't move towards a purely script-based backend
** [RR] export/import with Python could reduce a lot of that friction by allowing 1) to edit workflow as Python 2) to open up boxes automatically if needed code doesn't match actual modules
** ...

=== April 29, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] <strike>Abstractions</strike> subworkflows status ([https://github.com/VisTrails/VisTrails/labels/subworkflows tickets])
* [RR] matplotlib compatibility (2.1 & 2.2), [https://github.com/VisTrails/VisTrails/issues/1067 #1067]
** RR to try and fix ALPS matplotlib modules

=== April 22, 2015 ===
'''Updates'''
* 2.2.0 has been released!
* Windows issue (via email from Ryan)
** issue with manifest file (may be a new file in VTK6?)
** Tommy has regenerated new Windows builds
* Binaries, pypi, and conda released
* [RR] Export as script
* Python sources using VTK need to switch to SetInputData (users should be aware of this)

=== April 15, 2015 ===
'''Updates'''
* Ready for 2.2.0 (apart from binary/deps issues)
** Missing some libs (scikit-learn, tej, tdparser, SQLAlchemy+connectors
** Windows: runvistrails.py is no longer used, so the PATH is wrong
** Windows: pip is broken, but it probably wouldn't work anyway because of permission issues (disable this?)
* Queries, upgrades and getPipeline() usage ([https://github.com/VisTrails/VisTrails/issues/1054 #1054])
** Getting a pipeline with getPipeline() is not safe: it might return an invalid pipeline
** This is used in many places throughout the code, like queries
** Upgrading would require going through the controller, but that creates new actions
* [TC] Avoid copying a module's output if it's used as input by exactly one downstream module ([https://github.com/VisTrails/VisTrails/issues/1060 #1060]) (useful for big numpy arrays you can update in-place)

=== April 8, 2015 ===
'''Updates'''
* [DK] Merged RR's changes for output modules (1012 and 1013)
** RR will merge remaining changes, then create v2.2 branch!

'''Items to Discuss'''
* BNL need numpy array to VTK image
** Looks like VTK has some helpers for this
** We will help if issues arise
** Will contribute back to VisTrails package
* Upgrade issue: [https://github.com/VisTrails/VisTrails/issues/1017 #1017]
** Automatic upgrades should happen between versions of provided upgrades
** Our existing upgrades work around this so it doesn't need to be 2.2.0
* Corner-case VTK modules
** No longer need VTKCell input port, so don't interfere with registry and API anymore
** Still work weirdly, people probably shouldn't use them
** But we have lots of clunky modules since we wrap the whole of VTK; some people might rely on this and know how to use them, let's keep them anyway
** Ready for 2.2.0

=== April 1, 2015 ===
'''Updates'''
* [RR] UV-CDAT: bugfixing for 2.2, long-term plans: implement scripting import/export in VisTrails, port to UV-CDAT
* Possibly, try to move to regular VisTrails to use new features

'''Items to Discuss'''
* 2.2 release: nothing much is pending anymore, release next week?
** [TE] vtkExporter classes [https://github.com/VisTrails/VisTrails/issues/1032 #1032]
** [RR] Hiding upgrades in version tree might make it (or might be 2.2.1 so we can test it out) [https://github.com/VisTrails/VisTrails/issues/949 #949]
** Output modules changes to go in
* add note to documentation about order of parameters in VTK
* add issue about exporter upgrades if not already there

=== March 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* 2.2 release
** Checklist on Github: https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist
** Review output modules
** RR has a couple more issues to fix
** Ready to go -- sign app package for OSX? [https://github.com/VisTrails/VisTrails/issues/984 #984] We need access to the Apple Membership team

=== March 18, 2015 ===
'''Updates'''
* [TE] VTK6 works

'''Items to Discuss'''
* [RR] Release v2.1.5 with backported tabledata?
** MTA example needs updated tabledata (for JoinTables)
** Google Maps package still not available
* [RR] Work torward v2.2.0?
** changes:
*** new persistence
*** API changes
*** output module changes (upgrades?), maintain cells but try to upgrade
*** not wrapping stuff
*** VTK6? yes
*** JobSubmission stuff?
*** relabeling for upgrades [https://github.com/VisTrails/VisTrails/issues/949 #949]
** makes sense, needs the tree view code to be updated, check selection
** See [https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist 2.2 checklist]
* Discussion of [https://github.com/VisTrails/VisTrails/issues/1016 #1016]
** plumbing between outputs and output modes, how to define a mode that works for many outputs without writing for each output?

=== March 11, 2015 ===
'''Updates'''
* [RR] persistent_archive done; merge? ([https://github.com/VisTrails/VisTrails/pull/755 #755])
** note about the focus events for widgets
** TE be aware of file_archive for future binaries that include persistent_archive
* [TE] [https://github.com/VisTrails/VisTrails/pull/998 New VTK package] finished

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails? (see last week; decision needed)
** RR email to JF about this
** yes; email sent to Github
* [RR] Switching order of output ports ([https://github.com/VisTrails/VisTrails/pull/1006 #1006])
** added port specs are sorted at a separate spot (Module.*_port_specs properties) than those in the registry (which are sorted in the registry), but those two lists are just combined without respect to sort keys
** need to determine whether the two lists should be merged or remain distinct
** should make sure that order of input ports and output ports makes parallel connections for things with same order
** DK suggests breaking backward compatibility here: workflows still run, can fix easily if a problem in an existing package.
* [RR] Question about output modes ([https://github.com/VisTrails/VisTrails/pull/1007 #1007]), how to integrate in API ([https://github.com/VisTrails/VisTrails/pull/24 #24])
** Should ImageFileMode be removed? ("image" is not a mode, "file" is)
** ImageOutput missing?
** Feel free to change how formats works
* [TE] Test suite segfaults on Fedora 17 virtualbox. Install newer version? (Support ended in 2013)

=== March 4, 2015 ===
'''Updates'''
* [TE] VTK wrapper
** Works on VTK 5.10
** Still need to test VTK 6
** New general wrappers for python functions and classes

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails?
** When [http://i.imgur.com/UTY2qfg.png filing a pull request] from UV-CDAT/VisTrails, VisTrails/VisTrails is selected by default
** People keep forgetting to change the default ([https://github.com/VisTrails/VisTrails/pull/956 #956] [https://github.com/VisTrails/VisTrails/pull/968 #968] [https://github.com/VisTrails/VisTrails/pull/999 #999] [https://github.com/VisTrails/VisTrails/pull/1000 #1000] [https://github.com/VisTrails/VisTrails/pull/1003 #1003] [https://github.com/VisTrails/VisTrails/pull/1004 #1004] [https://github.com/VisTrails/VisTrails/pull/1005 #1005])
** Only way to change that is to not have it marked as a fork of VisTrails/VisTrails
** Github staff [https://gist.github.com/remram44/b364c24ef1e462ce6e2f can make that change for us]; should we do it?
** Juliana: comments on this? visibility vs. convenience/annoyance for developers
* [RR] What about [https://github.com/VisTrails/VisTrails/issues/991 #991]?

=== February 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] vtkviewcell for infovis support, can we unify with VTKCell?
** need to test this
* [TE] vtk wrapping
** Mostly finished
** VTK 5.10 produce incorrect results with old wrapping
*** Old wrapper is based mostly on VTK 4
*** Most vtk_examples affected
*** [http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Replacement_of_SetInput]
*** should be able to upgrade from SetInput to SetInputData (need to drop GetOutput and replace with self ports)
*** can we change vtkInstance to just return self and not wrap things
** terminator example not working under 5.8?
* How does VTK wrapping fit into general wrapping framework?
* [RR] new persistence package

=== February 18, 2015 ===
'''Updates'''
* [RR] New VisTrails API and IPython integration ([https://github.com/VisTrails/VisTrails/pull/24 #24])

'''Items to Discuss'''
* [TE] VTK wrapping
** [https://gist.github.com/rexissimus/16b74693545b5e7c1035 Benchmarking vtk package]
*** Old: 24.7 seconds
*** New: 10.5 seconds (Except first time that adds 8 sec)
**** The parsing that calls is_abstract (that tries to instanciate all vtk classes) is now only run the first time.
**** get_items_from_sigstring takes 2 seconds, maybe we can use a lookup dict for already computed sigstrings?
** Now using a general python function wrapper
*** VTK classes are wrapped into python function that does not depend on vistrails
*** VTK functions can be executed without vistrails
*** The spec maps functions into vistrails modules, but can also describe wrapping
*** A general python function wrapper that supports
**** kwarg inputs
**** single, list, dict outputs
**** callback for progress reporting
**** temporary file generator for using FilePool
**** optional output generation
*** Creating specs:
***** Create spec by hand
***** Auto-create spec outline (TODO) and manually finish it
***** Dynamically create spec (VTK)
***** Implement documentation wrappers (Can use scikitlearn wrapper to wrap numpydoc) (TODO)
***** Classes as bad functions needs to be wrapped in new functions before they are wrapped. This is different for each package.
****** Classes is hard: Like VTK, and matplotlib. Scikit-learn does still not wrap classes
***** Spec diffing and patching could be done using code from matplotlib.
** Still needs upgrades from old VTK package
*** Is it possible to dynamically wrap functions, e.g, you see a SetFunc and just remove the 'Set' prefix. Or do you need to create a complete mapping?

=== February 11, 2015 ===
'''Updates'''
* Update from Friday's meeting
** discussed VisTrails internals
** discussed wrapping
*** xml discussion, hard to modify because tied to db code
*** TE has made it possible to add the schema-defined attributes to the intermediate representation
*** higher-level operations on the port specs
** make sure the simple case works
*** [JF] take a simple package with documentation and figure out what the base case for wrapping is

'''Items to Discuss'''
* [TE] VTK wrapping
** Dynamic loading works
** Reading XML is fast enough, but [https://gist.github.com/rexissimus/8272d3c776ccfa115d82 unserializing data is slow]
** Working on patterns for patching
** Matplotlib has many advanced patterns like argument ordering, nested arguments, alternateSpecs, output types.
*** Having all this in a general wrapper might confuse users?
** [RR] Delay module (except for identifiers) until you need it---e.g. don't deal with port specs, etc. until necessary
* Scripting Support [https://github.com/VisTrails/VisTrails/pull/950 #950]
** [RR] Issue with getting code from modules
** Design a simple solution
** [JF] Couldn't you use modules as black boxes without conversion, just to call into modules/subworkflows easily from e.g. IPython?
*** [RR] This is a job for the API, and a very separate use case. See [https://github.com/VisTrails/VisTrails/pull/24 #24]

=== February 4, 2015 ===
'''Updates'''

'''Items to Discuss'''
* Wrapping
** Format to use? Currently XML (like current matplotlib)
*** JSON and YAML have simple "to python dictionary" methods
*** But don't stream
*** YAML a lot easier for humans
** [DK] vtk-new-package also changes parameter names, creates enumerations
*** intermediate schema needs to be extensible
*** packages will want to store there specific infos for compute() method generation
*** also might have specs-altering info, like matplotlib's alternateSpec
** representation to code , registry already has schema for some aspects
** [RR] We might want to see if Module subclasses can be created lazily
*** no need to create all the classes just to register them in the registry and never actually use most of them
*** future effort
* [RR] Where should VisTrails packages live?
** tej installs as 'vistrailspkg.tej', TE installed it as 'userpackages.tej'
** Currently, standard packages are 'vistrails.packages.', user packages are 'userpackages.' and packages loaded through pkg_resources might be anything
** [RR] Use 'vistrailspkg.' everywhere?
** Long-term effort to simplify package distribution/installation (and have VisTrails get them automatically?)

=== January 28, 2015 ===
'''Updates'''
* T. Caswell to come visit on Fri 6 to discuss wrapping work

'''Items to Discuss'''
* [TE] New VTK wrapping
** Current code by DK seems a good deal faster
** Generates XML that can be patched/tweaked, generates Python code from it, VisTrails only loads generated Python code
** RR would rather have VisTrails load intermediate representation (= XML) directly, wants to make sure this is not slower
** The goal is to turn the intermediate step into something generic that would be used for every wrapped package (vtk, numpy, matplotlib, sklearn, java) instead of each having its own
** TC has its own code at [https://github.com/Nikea/VTTools/blob/master/vttools/wrap_lib.py github:VTTools] which parses numpy docstrings and generates modules, doesn't yet handle classes or persist anything
* Web crawler
** Right now, TE starts jobs for "start crawler", "stop crawler", "install classifier"
** RR would rather have the crawling be a job as far as VisTrails and tej are concerned
** The whole thing would be one pipeline: load examples, train classifier, start crawler [check for job, kill previous one, upload model, start processes], get snapshot, visualize
*** Need some support in tej and job submission system: long-running jobs, stop a job (wait for it to finish?), restart a job even though results are cached

=== January 21, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Unified wrapping method discussion [https://github.com/VisTrails/VisTrails/issues/991 #991]
** TE to work on reusable method with intermediate representation, starting with VTK
* [RR] Examples for scikit-learn: JF has an old example using Weka with parameter exploration (not currently in source tree)
** AM's examples are enough
* [AM] scikit-learn package is done, merge it in? [https://github.com/VisTrails/VisTrails/pull/955#issuecomment-70286788 #955]
** RR will merge
* [RR] What should copyright headers say? [https://github.com/VisTrails/VisTrails/pull/994#issuecomment-70173935 #994]
** Let's keep everything in there: Utah/Poly/NYU

=== January 14, 2015 ===
'''Updates'''
* [TE] Working on classifier
* [RR] Scripting integration, work in progress

'''Items to Discuss'''
* [RR] Unified wrapping method discussion ([https://github.com/VisTrails/VisTrails/issues/991 #991])
** Let's talk next week, [AM] and [DK] are not here

=== January 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* make sure that we address critical issues, questions, and pending review branches in a timely manner
* scripting support
** [RR] no issues if we want to just keep annotations in the generated code to allow the link back to a workflow
** [RR] can translate from workflow to script, working on script to workflow
** will work for parameter value changes, structural changes require changes to the annotations
** need to publish best practices here
** would be cool to do looping in scripts (easier interface than with workflows)
* notebook support (convert form notebook to workflow)
** RR will sync with FC on this
* Issue with console in built-from-scratch
** [TC] iPython rearranged some of the completion stuff in 2.2 and 2.3
** binary has old version of iPython -> 1.0.0, should we update?
* [TC] automated wrapping of numpy and scipy
** discovered a bunch of malformed documentation in numpy and scipy
** has github repo for vistrails tools
** example modules wrap a bunch of R stuff (not baked in, just how things are)
** will be pushing wrapping logic up
** port names forbidden (window and domain)
** have an import hook to get from yaml directly to VisTrails Modules
** should work for any python modules with well-formed numpy docstrings.
* [Action] should make it clear in documentation that Constant now means serializable not that the value doesn't change (e.g. List)
* [TC] might be interesting to try to build components of matplotlib and accumulate in figure (long-term project, but thinking about how this might work)
* [TE] build and build scripts
** completely automatic, buildbot
** need to set the build machines for the environment we want for the binary
** would virtualenv work here?
** [TC] anaconda can pin versions, potential path to test different configurations
** Q: upload nightly binary builds? A: makes sense, make sure they are well-labeled
* sourceforge stats: e.g. http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07
* package issues (see Remi's message)
* [TE] Scope of tej
** Support single ssh commands?
** Queue can be used as a remote machine (crawler is using queue.call*)
* SourceForge stats: http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07

== Older meetings ==
* [[Development/2014]]
* [[Development/2013]]
* [[Development/2012]]
* [[Development/2011]]
* [[Development/2010]]

Development

2016-04-13T14:54:25Z

Tommy: /* April 13, 2016 */

<div class="nonumtoc toclimit-1">
__TOC__
</div>

See also the [https://github.com/VisTrails/VisTrails/wiki/Development Github wiki]

== 2016 ==

=== April 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Chaining upgrades done ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Replace "Upgrade" description annotation with "upgraded_from" annotation to identify which tags to hide?

* [TE] Iterating handle_invalid_pipeline ([https://github.com/VisTrails/VisTrails/pull/1165 #1165])
** Not based on [https://github.com/VisTrails/VisTrails/tree/chain-upgrades-loop chain-upgrades-loop]
** Cherry-pick test to preserve source?
** Need maxPipelineFixAttempts option?
*** The code is now smarter about recursion, so max attempts will "probably" never be reached.
** Need [https://github.com/VisTrails/VisTrails/commit/0ef0667426937eddb1d1c1e397f0657ffec039a9 debug messages]?
*** Would need to be moved into handle_invalid_pipeline

=== April 6, 2016 ===
'''Updates'''
* [TE] Query View improvements
** Done except for displaying "Version Info" and #1164
* [RR] Working on finishing new interpreter (finally!)

'''Items to Discuss'''
* [TE] Chaining upgrades ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Try latest upgrade first, then previous.
** If all fail, select latest upgrade?

=== March 30, 2016 ===
'''Updates'''

'''Items to Discuss'''

* [TE] Query View improvements
** Unified do_version_switch and get_upgrades as validate_version()
** Problems with query view using its own controller
*** Fixed module info not being displayed for query results
*** Still no version info for query results
*** Still an issue with version query view not being updated

=== March 23, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Usage reporting almost ready to go
** Need to record whether specific features are used: paramexpore, mashup, query
*** [DK] Record if LaTeX extension is used? But hard to distinguish from direct batch invocation
** How to record size of vistrail?
*** [DK] IdScope already walks over vistrail, use that
*** but total number of modules and versions doesn't give an idea of average size of individual pipelines

=== March 16, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Upgrades in Query Mode
** Now using code similar to do_version_switch
*** Uses handle_invalid_pipeline
*** Differences: Not using current_pipeline, flushes changes
*** New controller method get_pipeline optimized using cached pipelines (but not current_pipeline)
*** Integrate to avoid repeated code?
*** Use this for query mode?
* [TE] VisTrails 2.2.4 ready for release?
** tej package updated. Others?
* [JF] upgrades and the version tree
* [JF] provenance in Jupyter
* [DK] bundles: [https://github.com/VisTrails/VisTrails/pull/1092 #1092]

=== March 9, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixing search mode
** String query now matches all by default
*** This caused pipeline queries to never match
** String query can search: User/Notes/Tagname/Time/Module name
*** Should we search module names by default? (Disabled by default because it is expensive)
*** Fixed notes search
** '>' parameter queries in documentation but has been removed
** Fixed module matches for upgraded pipelines (By not upgrading pipeline)
*** Upgrades still a problem
*** Add "Upgrade all menu option?" (Or upgrade all on open when `hideUpgrades`)
*** [JF] Allow search on past tags

* [TE] Create new bugfix release
** Finish querying
** Path issue on windows

* [DK] Look into sqlalchemy and new bundle branches

=== March 2, 2016 ===
'''Updates'''
* [TE] Fixed cache bug with port specs
* [TE] VisTrails Next
** Most packages now work
** No qgis for Python 3

'''Items to Discuss'''
** Always dereference symlinks? [https://github.com/VisTrails/VisTrails/issues/1146 #1146]

=== February 23, 2016 ===
'''Updates'''
* [TE] Fixed PythonSource 100% CPU bug
* [TE] VisTrails Next
** Updated [http://opendap.co-ops.nos.noaa.gov/axis/webservices/wind/ NOAA Web Service] examples
*** Now uses REST service, tabledata, and Google Maps
*** Web Service replaced with DownloadFile

'''Items to Discuss'''
* [RR] Couple of fixes are in for API, and tej&reprounzip on the Mac binary. Also new release of tej, and working on anonymous usage reports.
** New 2.2 release soon?
* [RR] Anonymous usage reports
** Sends out info like number of modules & versions, packages used, Python & libs versions, execution time, specific features [https://github.com/VisTrails/VisTrails/pull/1154 #1154]
* [JF] Bring in noWorkflow to track variable dependencies, for the considered Jupyter integration?
* noWorkflow - provenance for python scripts
** Recent work on tracking dependencies
* Also integrates ReproZip with Jupyter
** [http://mybinder.org mybinder]
*** Use with ReproZip to automatically build Jupyter notebook interfaces
* Daves comments on Jupyter integration
** It is possible to identify cell order on the server side
** Not trivial to track order of cells on client side
* How does Galaxy workflows relate to VisTrails?
** Packaging in Galaxy is hard
** Galaxy for biomedical workflows, difficulty making it general
* Action items
** How difficult to track cell dependencies in Jupyter notebooks?
** Use noWorkflow to track cell dependencies?
** How difficult to modify mybinder to use ReproZip packages?

=== February 17, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixed Group memory usage
** Modules in groups are supposed to be freed when done executing
*** Prevented by logger that stored references to the modules (fixed, now using id(module))
*** Prevented by list iterator bug that stored list of modules on the 'self' port bug (fixed)
* [TE] VisTrails Next
** Removed deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** PythonSources will be upgraded
*** Fixes for Python < 3
*** fixes for VTK < 6
** TODOs
*** Remove RemoteQ
**** Port Hadoop to tej (Already have pbs)
*** Merge package wrapper
*** Finish SQLAlchemy branch
*** Finish new bundle branch
** [JF] Will contact Jeff and Matthias about moving to Python 3
* [JF] Query by Example is broken
* [JF] VisTrails Data Cleaning Project
** Use VisTrails to process and explore task-specific data while keeping provenance.
** Remi's Idea
*** Use VisTrails as the backend in a Jupyter notebook
*** Overcome problems with executing cells in random order
**** Interesting research topic, but little interest has yet been noted
*** Interesting to study how such a notebook would be used (Is there notebook usage data available?)
*** Impose restrictions to notebook cell boundaries
*** It will only work for functional operations
*** Can we fix, or detect, non-functional (mutating) operations?
*** Analyse code and data flow and see if it mutates data in unexpected ways?
*** Mutable operations can be created in many ways in Python
* Next meeting Tuesday 11:30

=== February 10, 2016 ===
'''Updates'''

'''Items to Discuss'''
* VisTrails Next
** Test suite passes
*** Python 3 less deterministic, module upgrade order random.
** [RR] updating packages: Reprounzip (pushed), tej, persistent_archive, ...
** All of our packages should run fine :)
** VTK thumbnail comparison works
*** Rendering bug on some systems
**** QVTKCell now inherits QGLWidget
*** Old thumbnails had wrong height due to spreadsheetwindow being too small
**** Fixed by regenerating thumbnails
*** Silenced deprecation messages when generating modules
*** Many new classes in VTK 7
** Remove deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** Will break existing PythonSources
**** Try to upgrade?
*** Old-style packages
**** Or only allow a new style, like __init__.py renamed to info.py? (merge with identifiers.py?)
***** Read info.py without importing package?
*** Fixes for Python < 3
*** Fixes for Qt < 5
*** fixes for VTK < 7
*** Remove self port?

=== February 3, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] [http://lists.vistrails.org/pipermail/vistrails-users/2016-January/000402.html Rendering a .pvd (ParaView) file?]

* VisTrails Next
** All tests but thumbnail comparison passes
** Still issues with gui and more packages needs to be tested
** PythonSource and MplSource upgraded with lib2to3
** Keep contrib packages? Update?
** [https://blog.kitware.com/vtk-7-0-0/ VTK 7 is released]
*** Supports Python 3
*** Will hopefully get into conda and others soon
*** Deprecates a bunch of modules

* [https://travis-ci.org/VisTrails/VisTrails/builds/106743348 Travis builder] for VisTrails Next
** Runs!
** Uses conda
*** Many levels of requirements
**** apt packages
**** conda packages
**** python packages in requirements.txt
**** python packages in setup.py
*** Can probably drop conda. Default builder does not have Qt5, but beta builder do!
*** But useful if we want to use conda in our own build process.
** Lots of errors I do not get locally?

* [http://goo.gl/forms/Z4HBrwaBWL User Survey]
** Have you used any alternatives to vistrails?
*** Relevant? More options?
** How often do you use any of these particular features in VisTrails?
*** Add/Remove alternatives?
** How important would you rank the following potential improvements to VisTrails?
*** Add alternatives?

=== January 27, 2016 ===
'''Updates'''
* New interpreter
** Working prototype soon
** Looping not completely done (and port combination mode: pairwise/cartesian...)
** Need to integrate with VisTrails
*** Compatibility with existing modules
*** Use log controller
*** Want to cache at multiple levels (whole stream/single element of stream)
*** Non-runtime attributes of modules (cache check, automatic conversion check, constant from/to string)

'''Items to Discuss'''
* User Survey

* ZMQ failing on windows (vistrails-users)

* [TE] [https://github.com/VisTrails/VisTrails/pull/1143 Python 3 branch]
** Testsuite almost passes
*** Failing are unicode filenames, some users guide examples, and thumbnail comparisons.
** Fixed issues
*** Signatures are now bytes (convert to string to show in widget)
*** Cannot compare different types, e.g., (None < 1)
**** PortSpec.depth and min/maxConn could be None. (Backport!)
**** cell.row could be None
*** Lots of unicode/bytes fixes to serializations
**** We have encryption implementations in the code! (keychain)
*** Lots of small fixes to package method differences
** Current issues
*** logging widget empty?
*** version tree signals messed up
*** provenance view legend icons black
*** Text do not fit in some widgets
*** VTK thumbnail comparison fails
**** VTK Cells have some faces in wrong direction?
**** Because running in VM?
** Installing on Ubuntu LTS/Latest Mint
*** Install latest matplotlib from pip
*** Install VTK 7.0.0rc2 from source
*** No QtWebEngine binary (controversial) (Must install sip/PyQt5/Qt5 from source)

=== January 20, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Backporting features from Python 3 + PyQt5 + Qt5
** Merged unicode with master ([https://github.com/VisTrails/VisTrails/tree/unicode unicode])
*** One unicode test failing
*** Problem saving to xml
** Used [http://python-future.org/ python-future] to run futurize stage 1 to update legacy (pre 2.6) code ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized unicode-futurized])
*** Updates print to functions 'from __future__ import print_function'
*** Updates exception calls to use 'as'
*** removes most usages of 'long' (mostly used unnecessarily)
**** Only needed for 32-bit support
*** Fixes relative imports (from __future__ import absolute_import)
** Fixing code that is deprecated in Qt 4.8 and removed in Qt 5 ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized-qt5 unicode-futurized-qt5])
*** Updated all signals to new-style
* If we go 2 to 3, this could break packages
** means we should schedule any package format changes for the same time
** e.g., imports should be unrelated to code path (function to load module from package identifier?) (take them out of vistrails.* [https://github.com/VisTrails/VisTrails/pull/1002 #1002])
** any structural changes (e.g. the __init__ versus init thing) (RR thinks it makes sense, though having both named "init" is unfortunate)
** putting package identifier as xml?
*** Python not so bad, plus some stuff in there is Python code (checking dependencies)
** version the APIs?
*** RR planning on versioning vistrails_module.Module, no point versioning the whole package?
* file formats on 2 to 3:
** no real translation/upgrade, but non-ascii values that work on 3 won't load in 2

=== January 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://gist.github.com/rexissimus/dfd27e466427529c385c Porting to Python 3 / PyQt5]
** Basic GUI and execution works
** Minimal work to support 2to3
** Hard to support both PyQt4 and PyQt5

=== January 6, 2016 ===
'''Updates'''
'''Items to Discuss'''
* Updating VisTrails dependencies
** Successfully built [https://gist.github.com/rexissimus/f1a1aada7de1c00a57c7 Win7-64/Python3/PyQt5/Qt5/WebEngine/VTK7]
*** VTK 7 is the first supporting Python 3 but is only in release candidate phase.
**** Next version of VTK 6 is rumored to support Python 3
**** There is a development branch of VTK 6 supporting Python 3
*** Can travis build this?
**** We can skip tests for WebEngine and VTK if needed
** Python 3 [https://python3wos.appspot.com/ showstoppers]
*** No MySQL-python (sqlalchemy supports mysql through other drivers)
*** No suds (there are active forks but we could also drop support?)
* Options for python2/3 support:
** Interpreter could be python2/python3 based on packages
** six layer works but not the easiest to maintain (e.g. in reprozip)
* Drop support for win-64
* Update copyright headers to 2016

== 2015 ==

=== December 30, 2015 ===
'''Updates'''
* Bokeh package finished
** Can output to Browser/IPython/Spreadsheet (Limited functionality in spreadsheet)
'''Items to Discuss'''
* Updating VisTrails dependencies
** Bokeh needs QWebEngine (Chromium) in Qt5 which requires PyQt5
*** Many plotting libraries only work in browsers
*** But Chromium may be a big and controversial dependency
*** Or create a browser version of the spreadsheet?
** Some users have requested Python 3
** Not backwards compatible?
** Target for VisTrails 3.0 with new interpreter?

=== December 16, 2015 ===
'''Updates'''
'''Items to Discuss'''
* Users list question
* [TE] Wrapping Bokeh
** Added bokeh property parser
*** complements numpydoc parser
*** Not all attributes are available, partially because I am using a pre-release version.
** Wrapped modules
*** bokeh.plotting finished (Backwards like matplotlib: Create plot then draw on it)
*** bokeh.charts mostly done (Missing arguments)
** QWebView mostly works (but no zooming or buttons)
*** It would be better to use external browser or QWebEngineView
** Added improvements to wrapper
*** Generalized port translations (Color/Path to native types)
*** Can use multiple docstring/property parsers simultaneously

=== December 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Looking into wrapper
** Will port TensorFlow
** Doing a pass on the wrapper code & doc
*** UX improvements
** Factorize high-level docstring parsers into core.wrapper? (sphinx, numpy, google)
** Problem with name vs module_name (fails sklearn tests because class_by_name() is broken)
** Looking into compressing specs, lazy registration of modules

=== December 2, 2015 ===
'''Updates'''
* [TE] Package wrapping
** Wrapped most of numpy/scipy using __all__
** Added class attribute and method access for classes (Can add to class or to separate inspector module)
** TODO: Document wrapping procedure

'''Items to Discuss'''

=== November 25, 2015 ===
'''Updates'''
* [RR] New interpreter is coming along
** Everything is a stream
** Task system, eventually work-stealing parallelism
** Streams no longer advance in lock-step
*** Allows for constructions like filter, join, sorted-merge
** depth>1 still to be tested, no current plan to allow this through the module interface
*** Through looping though, can do streams of streams

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapped most numpy functions (no polynomials)
** and half of scipy classes and functions
** Added functions manually from documentation (no parseable lists?)
** Focusing on data flow constructs (no property/method access for classes)
*** Using spec diff (empty for now) and dynamic parser (stores spec in .vistrails/)
** Python class/function wrapper now stable
** Add google doc parser?
*** Is there a parser available?

=== November 18, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Numpy class wrapping works
*** Basic type is List, since most types are array_likes.
*** TODO: More classes and functions
*** Some operations are in-place and some aren't, and docstring not super clear
*** [RR] It seems only methods mutate, and most have a numpy.xx function equivalent; just manually go through the methods and remove the mutating ones?
** Class wrapper is modular
*** Docstring parser and type string parser can be customized
*** Classes can have optional attribute/method ports
**** Inspectors and attribute/method modules can be created separately
** Use PythonCalc as an example
*** Can be re-implemented as a function with a parseable docstring
*** [RR] PythonCalc is just an example, and it might actually make sense to get rid of it, or do a proper math package with scalar operations (as separate modules, no combobox)
** [RR] TensorFlow to use wrapping as well
*** Very simple (only types 'tensor' & 'variable')

=== November 11, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapping numpy's classes using numpydoc (ndarray)
*** Wrapping constructor arguments, attribute getters/setters as module ports
**** Then how to access attributes afterwards?
***** Use input value port to class modules?
*** Wrap methods as modules? E.g., `ndarray.shape`.
*** Function wrapping is almost a subset of class wrapping
**** May be able to use the same parsing/execution methods
** VTK's non-getter/setter methods could be wrapped as modules
*** We could then remove extra logic in interpreter for keeping function order
** Bokeh uses autogenerated docstrings
*** We may be able to read the specification directly

* [RR] [https://github.com/VisTrails/VisTrails/pull/1138 TensorFlow package]
** Basic setup working, can execute the Mandelbrot example
** Will autogenerate the operations

=== November 4, 2015 ===
'''Updates'''
* [RR] Interpreter work requires a fix for [https://github.com/VisTrails/VisTrails/issues/1137 DB issue #1137]
* [DK] Kitware's Resonant [http://www.kitware.com/source/home/post/173]
** [https://github.com/girder/girder Girder]: data management system
** [https://github.com/Kitware/romanesco Romanesco]: execution engine, uses [http://www.celeryproject.org/ Celery] for task management
** Resonant Flow: web app for editing and executing workflows

'''Items to Discuss'''
* [TE] Added OSX Lion (10.7) VM on build machine using vagrant (seems ok with license?)
** New builds works on Lion
** Change the minimum requirement to 10.7?
* [TE] Package wrapping
* Added upgrade suggestions using 2 spec versions ([http://pastebin.com/30XUU8Gp example])
** using name edit distance to find matches
** Could use something better like port similarity for modules, and type similarity for ports
** Should write python upgrade code?
** Added spec to sklearn package
*** Can now diff spec versions and keep the spec static
*** There will be problems with downgrades and package versions

=== October 29, 2015 ===
'''Updates'''
* [TE] nightly-build-mac fixed (Needed to approve xcode license)

'''Items to Discuss'''
* [TE] matplotlib wrapper
** ported to general spec
** Diff can be used on general spec
*** Only needed minor changes
*** Fixed indexing bug that corrupted specs
*** Can now move diff tools to core/wrapper
** Add new plots?
*** New plots in mpl 1.3: eventplot
*** New plots in mpl 1.4: angle_spectrum, magnitude_spectrum, phase_spectrum', violinplot
*** No new plots in mpl 1.5 (from looking at boilerplate.py)

=== October 21, 2015 ===
'''Updates'''
* [RR] Alexis has arrived, will be working with [RR] on a more efficient interpreter

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package]
** Supporting multiple package versions
*** Check which version can be loaded [https://github.com/VisTrails/VisTrails/pull/1135 #1135]
*** We cannot show version requirements in the list of packages because old packages are loaded when importing the codepath
** Visual diff does not work well, but we can use the spec differ to see differences.
** Unifying vtk and matplotlib wrapping specs (WIP)
*** And porting matplotlibs spec differ to work on the general spec
*** Spec differ can then be used on vtk and other packages in the future
*** Will enable automatic upgrade generation
* [RR] Rework interpreter
** restore abstraction between interpreter/module code
** build looping, streaming, caching into the interpreter
** rework cache
** look into parallelism once basic functionality is there

=== October 14, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package] (adding numpydoc parser)

=== October 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/tree/fix-matplotlib-parser New matplotlib parser] (adding numpydoc parser)
** Added numpydoc attribute parser for plots.
*** TODO: Need better port spec reconciliation with call signature parser.
*** We can create a general numpydoc parser, but attribute types are unique to matplotlib.
** Needs package versioning
*** New spec will not support matplotlib < v1.4 due to changed path to axes classes.
*** Load spec version corresponding to installed matplotlib version?
*** Need version downgrades?

=== September 30, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Updating Matplotlib parser
** Matplotlib docstring parser fails on numpy docstrings
** I have [https://github.com/VisTrails/VisTrails/commit/eae8b0c16260810587e47c41cab53552cbb3cf0a added basic numpydoc parsing]
*** Only used by a few docstrings so far
*** Parsing uses many sources (class tables, signatures, ACCEPTS, method docstrings, definition parsing).
** Caswell said they were thinking about moving to traitlets, but this is not ready yet

=== September 23, 2015 ===
'''Updates'''
* [TE] VisTrails 2.2.3 released
** Also have pushed to PyPI, binstar, etc.
** Sourceforge vs. GitHub
*** should be able to host releases on GitHub
*** nightly binaries pushed to sf each night
*** old binaries?
* [TE] Re-wrapping MatPlotlib
** Keep static generation - Docstrings are brittle beween matplotlib versions
** Keep generating the executable classes - but create functions, not vistrails Modules
*** Why is there so much patching?
** Re-implemented Alternate PortSpec for InputPortSpec
*** It will now inherit specs from parent (No need to reimplement)
** Module upgrades?

'''Items to Discuss'''

=== September 16, 2015 ===
'''Updates'''
* [TE] Job Monitor tests and documentation done
** OK to leave document package in packages directory?

'''Items to Discuss'''
* [TE] Library wrapping: How to do code patching? [https://docs.google.com/drawings/d/1Sh3eOXot6v2y880jHKQrqXqAwr-0aoqYligg3z8G8MY/edit?usp=sharing Wrapping diagram]
** Insert code into module template (Old VTK code)
** Patch the library that is called (New VTK code)
** Somehow store code in spec and apply when executed?
*** Executed code needs at a minimum access to inputs, outputs, current class
*** Use standard input/output dict and obj reference that the code operates on?
*** Can this be done while keeping the execution abstract?

* Do new release now?

=== September 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* New release?
** [RR] wants reprounzip
** tej changes & doc
** job monitor & jobmixin fixes
** mongodb
** reprounzip
** warning: MplFigure type is int
** tabledata: add Reshape, DictoToTable & ListToTable, fix ListToTable with numpy arrays
** PythonSource can have same name for an input & output
** don't show spreadsheet at exit

=== September 2, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Limit autosaves? [https://github.com/VisTrails/VisTrails/pull/1126 #1126]

=== August 26, 2015 ===
'''Updates'''
* [TE] Added Job support to Parameter Explorations (Requested by Colin), and Mashups
** specify job ids, need to specify different ids for parameter explorations since they have the same version id
** how to deal with parameters passed in on command line
* [General] provenance: should be creating a new version when we execute workflow with changed parameters?
** currently, custom_params annotation stores this in provenance currently
** [RR] API doesn't record provenance if passing in parameters: http://git.io/vsAA5
'''Items to Discuss'''

=== August 19, 2015 ===
'''Updates'''
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [TE] Working on Job Monitor documentation

'''Items to Discuss'''
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [TE] Stop testing VisTrails 2.0?

=== August 12, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Build broken on Travis; because of IPython 4 released today? ([https://travis-ci.org/VisTrails/VisTrails/builds/75279795 build 992]; [https://github.com/VisTrails/VisTrails/issues/1123 #1123])

=== August 5, 2015 ===
'''Updates'''
* [TE] Fixes to Jobs
** Could not delete jobs
** Could not run job in group
** Job not reset when calling ModuleSuspended
** Added deleting job from context menu
* [RR] Writing documentation for everything [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

'''Items to Discuss'''

=== July 29, 2015 ===
'''Updates'''
* RR still looking into new interpreter thing
** Goal is to take out scheduling logic from Module so it can be split in multiple processes, and so that smarter strategies can be added in time
** This means some work on packages
** Spreadsheet can live in kernel process? Still some UI stuff that will take work (changing configuration, persistent archive's viewer, ...)
* [TE] Problems running examples [https://github.com/VisTrails/VisTrails/pull/1111 #1111]
** Testing of more examples requires additional packages on the test machines.
** Fixed faulty line-ending in PythonSource:s failing on Python 2.6.
** Test suite now testing SUDSWebServices (If web service is down, test suite will fail)
** preferences.py test failed reloading 'dialogs' package, switched to using 'URL'.

'''Items to Discuss'''

=== July 22, 2015 ===
'''Updates'''
* [TE] mailing lists back online
* [TE] Working on [https://github.com/VisTrails/VisTrails/issues/1107 #1107]
* [RR] Working on ReproZip package

'''Items to Discuss'''
* [RR] MongoDB package [https://github.com/VisTrails/VisTrails/pull/1106 #1106]
* [RR] Example for tej docs? [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

=== July 15, 2015 ===
'''Updates'''
* 2.2.2 released

'''Items to Discuss'''
* RR is considering executing everything in an IPython kernel (i.e. separate Python interpreter, like the one spawned for a notebook)
** It's a separate process that we can restart without restarting the app/gui
** We can isolate the execution environment (e.g. for the server)
** We can run the whole thing remotely (if your data is elsewhere, just run VisTrails locally and the pipeline elsewhere)
** Pipeline execution no longer makes the interface hang, it just makes the kernel hang (but that's fine)
** We can use notebooks as modules (probably way nicer than the PythonSource module)
** We can run multiple kernels so long as the ports carry things that are serializable
*** meaning we can put the multithreaded-interpreter without all the hacky parts it has now
*** we can run IPython kernels in all the languages IPython supports, [https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages currently 46]

=== July 8, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Buildbot github hook not working after IP address change
* [TE] No reference to VistrailsApplication ([https://github.com/VisTrails/VisTrails/issues/1103 #1103])
** [RR] Added PR [https://github.com/VisTrails/VisTrails/pull/1104 #1104]
* [TE] Reopening VT file after saving with bundled subworkflow won't offer subworkflow upgrade ([https://github.com/VisTrails/VisTrails/issues/1102 #1102])
** allow manual delete to fix right now
** fix this on top of the use-uuid branch
* [TE] Release VisTrails 2.2.1? ([https://github.com/VisTrails/VisTrails/blob/v2.2/CHANGELOG CHANGELOG])
** [https://github.com/VisTrails/VisTrails/pull/1093 output-modules-use-global-dir]
** [https://github.com/VisTrails/VisTrails/milestones/version%202.2 Current issues for 2.2]

=== July 1, 2015 ===
'''Updates'''
* [TE] PROV fixed
* [TE] Working on subworkflow issues
* [RR] Considering reworking the controller (log vs exception problem, retained upgrades causing interferences) and also the interpreter (IPython?)

'''Items to Discuss'''

=== June 24, 2015 ===
'''Updates'''

'''Items to Discuss'''
* UV-CDAT
* [TE] Can a cyclic workflow be valid? ([https://github.com/VisTrails/VisTrails/issues/1097 #1097])
** focus on disabling the ability to create cyclic pipelines because more things break than just this with a cyclic pipeline
* [RR] Relative paths ([https://github.com/VisTrails/VisTrails/pull/1057 #1057])
** This interacts with the new bundle; how do handle packing files inside the VT bundle?

=== June 17, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] current_version and reusing existing upgrades are broken ([https://github.com/VisTrails/VisTrails/issues/1095 ticket #1095])
** Could be that export to PROV is using an unflushed upgrade pipeline?
** current_version would then be correct.
** It may work to flush the actions before exporting?

=== June 10, 2015 ===
'''Updates'''
* DAT: fixed VTK issue on Linux and Mac
* Still crashes on Windows. Need help! Reminder: this works in the VisTrails spreadsheet (QCellPresenter), although no widget get changed there during a drag
** Is it a VTK bug?
** Is it simply impossible to change widgets during the drag, should we do it a different way?
** Did I miss something that is done in VisTrails but somehow not in DAT?
** Low prio, UV-CDAT doesn't run on Windows anyway

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 Updated pull request])
* Single instance code and batch mode

=== June 3, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 pr])
** Requires fixes to command line parameters, Output modules, and batch mode
** How to test this
** Updated missing/outdated flags
** Fixed view issues when generating graphs
* [TE] batch mode
** SpreadsheetOutput not enabled in batch mode. Should we check is_running_gui instead?
** Other instance setting flags from caller
** Is graphsAsPdf replacing spreadsheetDumpPdf?
** graphsAsPdf true by Default?
** Batch mode executing by default (Not needed when generating graphs)
** Re-added workflowInfo as withWorkflowInfo for writing graph and xml workflow
** [DK] batch mode should be outputting to files or stdout, shouldn't always trigger SpreadsheetMode
** execute flag, maybe make execution the default and allow a "--no-execute" if you only want to capture graphs, for example

=== May 27, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] API question
** http://lists.vistrails.org/pipermail/vistrails-users/2015-May/000357.html
* Status of DAT
** Can add VCS plot to DAT but need to work on configuration windows
** Documentation for graphics templates for UV-CDAT/vcs?
* Qt support?

=== May 20, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Reviving the DAT, integrating scripting & porting UV-CDAT!
** On [https://github.com/VisTrails/DAT GitHub] ([https://github.com/VisTrails/DAT/issues issues])
** Merging 2 years of development taking longer than expected, but getting there. The plan is to get the patches in VisTrails and never fork again, we never want to get in UV-CDAT's situation (and don't need to).
** VTK cell works fine on Linux but there was flickering on Mac & Windows before; still issues on Mac (Windows status unknown)
** Can get a VCS plot soon (but will need VTK cell fix)
** Integrate in UV-CDAT's build system (so we have cdms, VCS, ...) -> RR can do this, low priority
** How do we integrate scripting?
*** We want to be able to seamlessly make changes to a plot by changing Python code
*** Define new plots by entering Python code without writing modules/packages?
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 13, 2015 ===
'''Updates'''
* [RR] Test skipping whitelist ([https://github.com/VisTrails/VisTrails/pull/1069 #1069]) -- low priority
* [RR] Custom matplotlib modules can't be compatible with both 2.1 and 2.2 ([https://github.com/VisTrails/VisTrails/issues/1067 #1067]); should be fixed for ALPS ([https://github.com/VisTrails/VisTrails/issues/1070 #1070])

'''Items to Discuss'''
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 7, 2015 ===
'''Updates'''
* [RR] Export/import workflow to Python working!

'''Items to Discuss'''
* [Claudio] UV-CDAT
** The UV-CDAT project is the biggest user base of VisTrails
** VisTrails package management provides a lot of friction towards people plugging in their code
** Need to make it easy to integrate your random Python scripts in the system without having to deal with all the boilerplate, at least in the first step
** [RR] argues that modules are still good; UV-CDAT shouldn't move towards a purely script-based backend
** [RR] export/import with Python could reduce a lot of that friction by allowing 1) to edit workflow as Python 2) to open up boxes automatically if needed code doesn't match actual modules
** ...

=== April 29, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] <strike>Abstractions</strike> subworkflows status ([https://github.com/VisTrails/VisTrails/labels/subworkflows tickets])
* [RR] matplotlib compatibility (2.1 & 2.2), [https://github.com/VisTrails/VisTrails/issues/1067 #1067]
** RR to try and fix ALPS matplotlib modules

=== April 22, 2015 ===
'''Updates'''
* 2.2.0 has been released!
* Windows issue (via email from Ryan)
** issue with manifest file (may be a new file in VTK6?)
** Tommy has regenerated new Windows builds
* Binaries, pypi, and conda released
* [RR] Export as script
* Python sources using VTK need to switch to SetInputData (users should be aware of this)

=== April 15, 2015 ===
'''Updates'''
* Ready for 2.2.0 (apart from binary/deps issues)
** Missing some libs (scikit-learn, tej, tdparser, SQLAlchemy+connectors
** Windows: runvistrails.py is no longer used, so the PATH is wrong
** Windows: pip is broken, but it probably wouldn't work anyway because of permission issues (disable this?)
* Queries, upgrades and getPipeline() usage ([https://github.com/VisTrails/VisTrails/issues/1054 #1054])
** Getting a pipeline with getPipeline() is not safe: it might return an invalid pipeline
** This is used in many places throughout the code, like queries
** Upgrading would require going through the controller, but that creates new actions
* [TC] Avoid copying a module's output if it's used as input by exactly one downstream module ([https://github.com/VisTrails/VisTrails/issues/1060 #1060]) (useful for big numpy arrays you can update in-place)

=== April 8, 2015 ===
'''Updates'''
* [DK] Merged RR's changes for output modules (1012 and 1013)
** RR will merge remaining changes, then create v2.2 branch!

'''Items to Discuss'''
* BNL need numpy array to VTK image
** Looks like VTK has some helpers for this
** We will help if issues arise
** Will contribute back to VisTrails package
* Upgrade issue: [https://github.com/VisTrails/VisTrails/issues/1017 #1017]
** Automatic upgrades should happen between versions of provided upgrades
** Our existing upgrades work around this so it doesn't need to be 2.2.0
* Corner-case VTK modules
** No longer need VTKCell input port, so don't interfere with registry and API anymore
** Still work weirdly, people probably shouldn't use them
** But we have lots of clunky modules since we wrap the whole of VTK; some people might rely on this and know how to use them, let's keep them anyway
** Ready for 2.2.0

=== April 1, 2015 ===
'''Updates'''
* [RR] UV-CDAT: bugfixing for 2.2, long-term plans: implement scripting import/export in VisTrails, port to UV-CDAT
* Possibly, try to move to regular VisTrails to use new features

'''Items to Discuss'''
* 2.2 release: nothing much is pending anymore, release next week?
** [TE] vtkExporter classes [https://github.com/VisTrails/VisTrails/issues/1032 #1032]
** [RR] Hiding upgrades in version tree might make it (or might be 2.2.1 so we can test it out) [https://github.com/VisTrails/VisTrails/issues/949 #949]
** Output modules changes to go in
* add note to documentation about order of parameters in VTK
* add issue about exporter upgrades if not already there

=== March 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* 2.2 release
** Checklist on Github: https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist
** Review output modules
** RR has a couple more issues to fix
** Ready to go -- sign app package for OSX? [https://github.com/VisTrails/VisTrails/issues/984 #984] We need access to the Apple Membership team

=== March 18, 2015 ===
'''Updates'''
* [TE] VTK6 works

'''Items to Discuss'''
* [RR] Release v2.1.5 with backported tabledata?
** MTA example needs updated tabledata (for JoinTables)
** Google Maps package still not available
* [RR] Work torward v2.2.0?
** changes:
*** new persistence
*** API changes
*** output module changes (upgrades?), maintain cells but try to upgrade
*** not wrapping stuff
*** VTK6? yes
*** JobSubmission stuff?
*** relabeling for upgrades [https://github.com/VisTrails/VisTrails/issues/949 #949]
** makes sense, needs the tree view code to be updated, check selection
** See [https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist 2.2 checklist]
* Discussion of [https://github.com/VisTrails/VisTrails/issues/1016 #1016]
** plumbing between outputs and output modes, how to define a mode that works for many outputs without writing for each output?

=== March 11, 2015 ===
'''Updates'''
* [RR] persistent_archive done; merge? ([https://github.com/VisTrails/VisTrails/pull/755 #755])
** note about the focus events for widgets
** TE be aware of file_archive for future binaries that include persistent_archive
* [TE] [https://github.com/VisTrails/VisTrails/pull/998 New VTK package] finished

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails? (see last week; decision needed)
** RR email to JF about this
** yes; email sent to Github
* [RR] Switching order of output ports ([https://github.com/VisTrails/VisTrails/pull/1006 #1006])
** added port specs are sorted at a separate spot (Module.*_port_specs properties) than those in the registry (which are sorted in the registry), but those two lists are just combined without respect to sort keys
** need to determine whether the two lists should be merged or remain distinct
** should make sure that order of input ports and output ports makes parallel connections for things with same order
** DK suggests breaking backward compatibility here: workflows still run, can fix easily if a problem in an existing package.
* [RR] Question about output modes ([https://github.com/VisTrails/VisTrails/pull/1007 #1007]), how to integrate in API ([https://github.com/VisTrails/VisTrails/pull/24 #24])
** Should ImageFileMode be removed? ("image" is not a mode, "file" is)
** ImageOutput missing?
** Feel free to change how formats works
* [TE] Test suite segfaults on Fedora 17 virtualbox. Install newer version? (Support ended in 2013)

=== March 4, 2015 ===
'''Updates'''
* [TE] VTK wrapper
** Works on VTK 5.10
** Still need to test VTK 6
** New general wrappers for python functions and classes

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails?
** When [http://i.imgur.com/UTY2qfg.png filing a pull request] from UV-CDAT/VisTrails, VisTrails/VisTrails is selected by default
** People keep forgetting to change the default ([https://github.com/VisTrails/VisTrails/pull/956 #956] [https://github.com/VisTrails/VisTrails/pull/968 #968] [https://github.com/VisTrails/VisTrails/pull/999 #999] [https://github.com/VisTrails/VisTrails/pull/1000 #1000] [https://github.com/VisTrails/VisTrails/pull/1003 #1003] [https://github.com/VisTrails/VisTrails/pull/1004 #1004] [https://github.com/VisTrails/VisTrails/pull/1005 #1005])
** Only way to change that is to not have it marked as a fork of VisTrails/VisTrails
** Github staff [https://gist.github.com/remram44/b364c24ef1e462ce6e2f can make that change for us]; should we do it?
** Juliana: comments on this? visibility vs. convenience/annoyance for developers
* [RR] What about [https://github.com/VisTrails/VisTrails/issues/991 #991]?

=== February 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] vtkviewcell for infovis support, can we unify with VTKCell?
** need to test this
* [TE] vtk wrapping
** Mostly finished
** VTK 5.10 produce incorrect results with old wrapping
*** Old wrapper is based mostly on VTK 4
*** Most vtk_examples affected
*** [http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Replacement_of_SetInput]
*** should be able to upgrade from SetInput to SetInputData (need to drop GetOutput and replace with self ports)
*** can we change vtkInstance to just return self and not wrap things
** terminator example not working under 5.8?
* How does VTK wrapping fit into general wrapping framework?
* [RR] new persistence package

=== February 18, 2015 ===
'''Updates'''
* [RR] New VisTrails API and IPython integration ([https://github.com/VisTrails/VisTrails/pull/24 #24])

'''Items to Discuss'''
* [TE] VTK wrapping
** [https://gist.github.com/rexissimus/16b74693545b5e7c1035 Benchmarking vtk package]
*** Old: 24.7 seconds
*** New: 10.5 seconds (Except first time that adds 8 sec)
**** The parsing that calls is_abstract (that tries to instanciate all vtk classes) is now only run the first time.
**** get_items_from_sigstring takes 2 seconds, maybe we can use a lookup dict for already computed sigstrings?
** Now using a general python function wrapper
*** VTK classes are wrapped into python function that does not depend on vistrails
*** VTK functions can be executed without vistrails
*** The spec maps functions into vistrails modules, but can also describe wrapping
*** A general python function wrapper that supports
**** kwarg inputs
**** single, list, dict outputs
**** callback for progress reporting
**** temporary file generator for using FilePool
**** optional output generation
*** Creating specs:
***** Create spec by hand
***** Auto-create spec outline (TODO) and manually finish it
***** Dynamically create spec (VTK)
***** Implement documentation wrappers (Can use scikitlearn wrapper to wrap numpydoc) (TODO)
***** Classes as bad functions needs to be wrapped in new functions before they are wrapped. This is different for each package.
****** Classes is hard: Like VTK, and matplotlib. Scikit-learn does still not wrap classes
***** Spec diffing and patching could be done using code from matplotlib.
** Still needs upgrades from old VTK package
*** Is it possible to dynamically wrap functions, e.g, you see a SetFunc and just remove the 'Set' prefix. Or do you need to create a complete mapping?

=== February 11, 2015 ===
'''Updates'''
* Update from Friday's meeting
** discussed VisTrails internals
** discussed wrapping
*** xml discussion, hard to modify because tied to db code
*** TE has made it possible to add the schema-defined attributes to the intermediate representation
*** higher-level operations on the port specs
** make sure the simple case works
*** [JF] take a simple package with documentation and figure out what the base case for wrapping is

'''Items to Discuss'''
* [TE] VTK wrapping
** Dynamic loading works
** Reading XML is fast enough, but [https://gist.github.com/rexissimus/8272d3c776ccfa115d82 unserializing data is slow]
** Working on patterns for patching
** Matplotlib has many advanced patterns like argument ordering, nested arguments, alternateSpecs, output types.
*** Having all this in a general wrapper might confuse users?
** [RR] Delay module (except for identifiers) until you need it---e.g. don't deal with port specs, etc. until necessary
* Scripting Support [https://github.com/VisTrails/VisTrails/pull/950 #950]
** [RR] Issue with getting code from modules
** Design a simple solution
** [JF] Couldn't you use modules as black boxes without conversion, just to call into modules/subworkflows easily from e.g. IPython?
*** [RR] This is a job for the API, and a very separate use case. See [https://github.com/VisTrails/VisTrails/pull/24 #24]

=== February 4, 2015 ===
'''Updates'''

'''Items to Discuss'''
* Wrapping
** Format to use? Currently XML (like current matplotlib)
*** JSON and YAML have simple "to python dictionary" methods
*** But don't stream
*** YAML a lot easier for humans
** [DK] vtk-new-package also changes parameter names, creates enumerations
*** intermediate schema needs to be extensible
*** packages will want to store there specific infos for compute() method generation
*** also might have specs-altering info, like matplotlib's alternateSpec
** representation to code , registry already has schema for some aspects
** [RR] We might want to see if Module subclasses can be created lazily
*** no need to create all the classes just to register them in the registry and never actually use most of them
*** future effort
* [RR] Where should VisTrails packages live?
** tej installs as 'vistrailspkg.tej', TE installed it as 'userpackages.tej'
** Currently, standard packages are 'vistrails.packages.', user packages are 'userpackages.' and packages loaded through pkg_resources might be anything
** [RR] Use 'vistrailspkg.' everywhere?
** Long-term effort to simplify package distribution/installation (and have VisTrails get them automatically?)

=== January 28, 2015 ===
'''Updates'''
* T. Caswell to come visit on Fri 6 to discuss wrapping work

'''Items to Discuss'''
* [TE] New VTK wrapping
** Current code by DK seems a good deal faster
** Generates XML that can be patched/tweaked, generates Python code from it, VisTrails only loads generated Python code
** RR would rather have VisTrails load intermediate representation (= XML) directly, wants to make sure this is not slower
** The goal is to turn the intermediate step into something generic that would be used for every wrapped package (vtk, numpy, matplotlib, sklearn, java) instead of each having its own
** TC has its own code at [https://github.com/Nikea/VTTools/blob/master/vttools/wrap_lib.py github:VTTools] which parses numpy docstrings and generates modules, doesn't yet handle classes or persist anything
* Web crawler
** Right now, TE starts jobs for "start crawler", "stop crawler", "install classifier"
** RR would rather have the crawling be a job as far as VisTrails and tej are concerned
** The whole thing would be one pipeline: load examples, train classifier, start crawler [check for job, kill previous one, upload model, start processes], get snapshot, visualize
*** Need some support in tej and job submission system: long-running jobs, stop a job (wait for it to finish?), restart a job even though results are cached

=== January 21, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Unified wrapping method discussion [https://github.com/VisTrails/VisTrails/issues/991 #991]
** TE to work on reusable method with intermediate representation, starting with VTK
* [RR] Examples for scikit-learn: JF has an old example using Weka with parameter exploration (not currently in source tree)
** AM's examples are enough
* [AM] scikit-learn package is done, merge it in? [https://github.com/VisTrails/VisTrails/pull/955#issuecomment-70286788 #955]
** RR will merge
* [RR] What should copyright headers say? [https://github.com/VisTrails/VisTrails/pull/994#issuecomment-70173935 #994]
** Let's keep everything in there: Utah/Poly/NYU

=== January 14, 2015 ===
'''Updates'''
* [TE] Working on classifier
* [RR] Scripting integration, work in progress

'''Items to Discuss'''
* [RR] Unified wrapping method discussion ([https://github.com/VisTrails/VisTrails/issues/991 #991])
** Let's talk next week, [AM] and [DK] are not here

=== January 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* make sure that we address critical issues, questions, and pending review branches in a timely manner
* scripting support
** [RR] no issues if we want to just keep annotations in the generated code to allow the link back to a workflow
** [RR] can translate from workflow to script, working on script to workflow
** will work for parameter value changes, structural changes require changes to the annotations
** need to publish best practices here
** would be cool to do looping in scripts (easier interface than with workflows)
* notebook support (convert form notebook to workflow)
** RR will sync with FC on this
* Issue with console in built-from-scratch
** [TC] iPython rearranged some of the completion stuff in 2.2 and 2.3
** binary has old version of iPython -> 1.0.0, should we update?
* [TC] automated wrapping of numpy and scipy
** discovered a bunch of malformed documentation in numpy and scipy
** has github repo for vistrails tools
** example modules wrap a bunch of R stuff (not baked in, just how things are)
** will be pushing wrapping logic up
** port names forbidden (window and domain)
** have an import hook to get from yaml directly to VisTrails Modules
** should work for any python modules with well-formed numpy docstrings.
* [Action] should make it clear in documentation that Constant now means serializable not that the value doesn't change (e.g. List)
* [TC] might be interesting to try to build components of matplotlib and accumulate in figure (long-term project, but thinking about how this might work)
* [TE] build and build scripts
** completely automatic, buildbot
** need to set the build machines for the environment we want for the binary
** would virtualenv work here?
** [TC] anaconda can pin versions, potential path to test different configurations
** Q: upload nightly binary builds? A: makes sense, make sure they are well-labeled
* sourceforge stats: e.g. http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07
* package issues (see Remi's message)
* [TE] Scope of tej
** Support single ssh commands?
** Queue can be used as a remote machine (crawler is using queue.call*)
* SourceForge stats: http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07

== Older meetings ==
* [[Development/2014]]
* [[Development/2013]]
* [[Development/2012]]
* [[Development/2011]]
* [[Development/2010]]

Development

2016-04-13T14:49:31Z

Tommy: /* April 13, 2016 */

<div class="nonumtoc toclimit-1">
__TOC__
</div>

See also the [https://github.com/VisTrails/VisTrails/wiki/Development Github wiki]

== 2016 ==

=== April 13, 2016 ===
'''Updates'''
* [TE] Chaining upgrades done ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])

'''Items to Discuss'''
* [TE] Iterating handle_invalid_pipeline ([https://github.com/VisTrails/VisTrails/pull/1165 #1165])
** Not based on [https://github.com/VisTrails/VisTrails/tree/chain-upgrades-loop chain-upgrades-loop]
** Cherry-pick test to preserve source?
** Need maxPipelineFixAttempts option?
*** The code is now smarter about recursion, so max attempts will "probably" never be reached.
** Need [https://github.com/VisTrails/VisTrails/commit/0ef0667426937eddb1d1c1e397f0657ffec039a9 debug messages]?
*** Would need to be moved into handle_invalid_pipeline

=== April 6, 2016 ===
'''Updates'''
* [TE] Query View improvements
** Done except for displaying "Version Info" and #1164
* [RR] Working on finishing new interpreter (finally!)

'''Items to Discuss'''
* [TE] Chaining upgrades ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Try latest upgrade first, then previous.
** If all fail, select latest upgrade?

=== March 30, 2016 ===
'''Updates'''

'''Items to Discuss'''

* [TE] Query View improvements
** Unified do_version_switch and get_upgrades as validate_version()
** Problems with query view using its own controller
*** Fixed module info not being displayed for query results
*** Still no version info for query results
*** Still an issue with version query view not being updated

=== March 23, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Usage reporting almost ready to go
** Need to record whether specific features are used: paramexpore, mashup, query
*** [DK] Record if LaTeX extension is used? But hard to distinguish from direct batch invocation
** How to record size of vistrail?
*** [DK] IdScope already walks over vistrail, use that
*** but total number of modules and versions doesn't give an idea of average size of individual pipelines

=== March 16, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Upgrades in Query Mode
** Now using code similar to do_version_switch
*** Uses handle_invalid_pipeline
*** Differences: Not using current_pipeline, flushes changes
*** New controller method get_pipeline optimized using cached pipelines (but not current_pipeline)
*** Integrate to avoid repeated code?
*** Use this for query mode?
* [TE] VisTrails 2.2.4 ready for release?
** tej package updated. Others?
* [JF] upgrades and the version tree
* [JF] provenance in Jupyter
* [DK] bundles: [https://github.com/VisTrails/VisTrails/pull/1092 #1092]

=== March 9, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixing search mode
** String query now matches all by default
*** This caused pipeline queries to never match
** String query can search: User/Notes/Tagname/Time/Module name
*** Should we search module names by default? (Disabled by default because it is expensive)
*** Fixed notes search
** '>' parameter queries in documentation but has been removed
** Fixed module matches for upgraded pipelines (By not upgrading pipeline)
*** Upgrades still a problem
*** Add "Upgrade all menu option?" (Or upgrade all on open when `hideUpgrades`)
*** [JF] Allow search on past tags

* [TE] Create new bugfix release
** Finish querying
** Path issue on windows

* [DK] Look into sqlalchemy and new bundle branches

=== March 2, 2016 ===
'''Updates'''
* [TE] Fixed cache bug with port specs
* [TE] VisTrails Next
** Most packages now work
** No qgis for Python 3

'''Items to Discuss'''
** Always dereference symlinks? [https://github.com/VisTrails/VisTrails/issues/1146 #1146]

=== February 23, 2016 ===
'''Updates'''
* [TE] Fixed PythonSource 100% CPU bug
* [TE] VisTrails Next
** Updated [http://opendap.co-ops.nos.noaa.gov/axis/webservices/wind/ NOAA Web Service] examples
*** Now uses REST service, tabledata, and Google Maps
*** Web Service replaced with DownloadFile

'''Items to Discuss'''
* [RR] Couple of fixes are in for API, and tej&reprounzip on the Mac binary. Also new release of tej, and working on anonymous usage reports.
** New 2.2 release soon?
* [RR] Anonymous usage reports
** Sends out info like number of modules & versions, packages used, Python & libs versions, execution time, specific features [https://github.com/VisTrails/VisTrails/pull/1154 #1154]
* [JF] Bring in noWorkflow to track variable dependencies, for the considered Jupyter integration?
* noWorkflow - provenance for python scripts
** Recent work on tracking dependencies
* Also integrates ReproZip with Jupyter
** [http://mybinder.org mybinder]
*** Use with ReproZip to automatically build Jupyter notebook interfaces
* Daves comments on Jupyter integration
** It is possible to identify cell order on the server side
** Not trivial to track order of cells on client side
* How does Galaxy workflows relate to VisTrails?
** Packaging in Galaxy is hard
** Galaxy for biomedical workflows, difficulty making it general
* Action items
** How difficult to track cell dependencies in Jupyter notebooks?
** Use noWorkflow to track cell dependencies?
** How difficult to modify mybinder to use ReproZip packages?

=== February 17, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixed Group memory usage
** Modules in groups are supposed to be freed when done executing
*** Prevented by logger that stored references to the modules (fixed, now using id(module))
*** Prevented by list iterator bug that stored list of modules on the 'self' port bug (fixed)
* [TE] VisTrails Next
** Removed deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** PythonSources will be upgraded
*** Fixes for Python < 3
*** fixes for VTK < 6
** TODOs
*** Remove RemoteQ
**** Port Hadoop to tej (Already have pbs)
*** Merge package wrapper
*** Finish SQLAlchemy branch
*** Finish new bundle branch
** [JF] Will contact Jeff and Matthias about moving to Python 3
* [JF] Query by Example is broken
* [JF] VisTrails Data Cleaning Project
** Use VisTrails to process and explore task-specific data while keeping provenance.
** Remi's Idea
*** Use VisTrails as the backend in a Jupyter notebook
*** Overcome problems with executing cells in random order
**** Interesting research topic, but little interest has yet been noted
*** Interesting to study how such a notebook would be used (Is there notebook usage data available?)
*** Impose restrictions to notebook cell boundaries
*** It will only work for functional operations
*** Can we fix, or detect, non-functional (mutating) operations?
*** Analyse code and data flow and see if it mutates data in unexpected ways?
*** Mutable operations can be created in many ways in Python
* Next meeting Tuesday 11:30

=== February 10, 2016 ===
'''Updates'''

'''Items to Discuss'''
* VisTrails Next
** Test suite passes
*** Python 3 less deterministic, module upgrade order random.
** [RR] updating packages: Reprounzip (pushed), tej, persistent_archive, ...
** All of our packages should run fine :)
** VTK thumbnail comparison works
*** Rendering bug on some systems
**** QVTKCell now inherits QGLWidget
*** Old thumbnails had wrong height due to spreadsheetwindow being too small
**** Fixed by regenerating thumbnails
*** Silenced deprecation messages when generating modules
*** Many new classes in VTK 7
** Remove deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** Will break existing PythonSources
**** Try to upgrade?
*** Old-style packages
**** Or only allow a new style, like __init__.py renamed to info.py? (merge with identifiers.py?)
***** Read info.py without importing package?
*** Fixes for Python < 3
*** Fixes for Qt < 5
*** fixes for VTK < 7
*** Remove self port?

=== February 3, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] [http://lists.vistrails.org/pipermail/vistrails-users/2016-January/000402.html Rendering a .pvd (ParaView) file?]

* VisTrails Next
** All tests but thumbnail comparison passes
** Still issues with gui and more packages needs to be tested
** PythonSource and MplSource upgraded with lib2to3
** Keep contrib packages? Update?
** [https://blog.kitware.com/vtk-7-0-0/ VTK 7 is released]
*** Supports Python 3
*** Will hopefully get into conda and others soon
*** Deprecates a bunch of modules

* [https://travis-ci.org/VisTrails/VisTrails/builds/106743348 Travis builder] for VisTrails Next
** Runs!
** Uses conda
*** Many levels of requirements
**** apt packages
**** conda packages
**** python packages in requirements.txt
**** python packages in setup.py
*** Can probably drop conda. Default builder does not have Qt5, but beta builder do!
*** But useful if we want to use conda in our own build process.
** Lots of errors I do not get locally?

* [http://goo.gl/forms/Z4HBrwaBWL User Survey]
** Have you used any alternatives to vistrails?
*** Relevant? More options?
** How often do you use any of these particular features in VisTrails?
*** Add/Remove alternatives?
** How important would you rank the following potential improvements to VisTrails?
*** Add alternatives?

=== January 27, 2016 ===
'''Updates'''
* New interpreter
** Working prototype soon
** Looping not completely done (and port combination mode: pairwise/cartesian...)
** Need to integrate with VisTrails
*** Compatibility with existing modules
*** Use log controller
*** Want to cache at multiple levels (whole stream/single element of stream)
*** Non-runtime attributes of modules (cache check, automatic conversion check, constant from/to string)

'''Items to Discuss'''
* User Survey

* ZMQ failing on windows (vistrails-users)

* [TE] [https://github.com/VisTrails/VisTrails/pull/1143 Python 3 branch]
** Testsuite almost passes
*** Failing are unicode filenames, some users guide examples, and thumbnail comparisons.
** Fixed issues
*** Signatures are now bytes (convert to string to show in widget)
*** Cannot compare different types, e.g., (None < 1)
**** PortSpec.depth and min/maxConn could be None. (Backport!)
**** cell.row could be None
*** Lots of unicode/bytes fixes to serializations
**** We have encryption implementations in the code! (keychain)
*** Lots of small fixes to package method differences
** Current issues
*** logging widget empty?
*** version tree signals messed up
*** provenance view legend icons black
*** Text do not fit in some widgets
*** VTK thumbnail comparison fails
**** VTK Cells have some faces in wrong direction?
**** Because running in VM?
** Installing on Ubuntu LTS/Latest Mint
*** Install latest matplotlib from pip
*** Install VTK 7.0.0rc2 from source
*** No QtWebEngine binary (controversial) (Must install sip/PyQt5/Qt5 from source)

=== January 20, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Backporting features from Python 3 + PyQt5 + Qt5
** Merged unicode with master ([https://github.com/VisTrails/VisTrails/tree/unicode unicode])
*** One unicode test failing
*** Problem saving to xml
** Used [http://python-future.org/ python-future] to run futurize stage 1 to update legacy (pre 2.6) code ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized unicode-futurized])
*** Updates print to functions 'from __future__ import print_function'
*** Updates exception calls to use 'as'
*** removes most usages of 'long' (mostly used unnecessarily)
**** Only needed for 32-bit support
*** Fixes relative imports (from __future__ import absolute_import)
** Fixing code that is deprecated in Qt 4.8 and removed in Qt 5 ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized-qt5 unicode-futurized-qt5])
*** Updated all signals to new-style
* If we go 2 to 3, this could break packages
** means we should schedule any package format changes for the same time
** e.g., imports should be unrelated to code path (function to load module from package identifier?) (take them out of vistrails.* [https://github.com/VisTrails/VisTrails/pull/1002 #1002])
** any structural changes (e.g. the __init__ versus init thing) (RR thinks it makes sense, though having both named "init" is unfortunate)
** putting package identifier as xml?
*** Python not so bad, plus some stuff in there is Python code (checking dependencies)
** version the APIs?
*** RR planning on versioning vistrails_module.Module, no point versioning the whole package?
* file formats on 2 to 3:
** no real translation/upgrade, but non-ascii values that work on 3 won't load in 2

=== January 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://gist.github.com/rexissimus/dfd27e466427529c385c Porting to Python 3 / PyQt5]
** Basic GUI and execution works
** Minimal work to support 2to3
** Hard to support both PyQt4 and PyQt5

=== January 6, 2016 ===
'''Updates'''
'''Items to Discuss'''
* Updating VisTrails dependencies
** Successfully built [https://gist.github.com/rexissimus/f1a1aada7de1c00a57c7 Win7-64/Python3/PyQt5/Qt5/WebEngine/VTK7]
*** VTK 7 is the first supporting Python 3 but is only in release candidate phase.
**** Next version of VTK 6 is rumored to support Python 3
**** There is a development branch of VTK 6 supporting Python 3
*** Can travis build this?
**** We can skip tests for WebEngine and VTK if needed
** Python 3 [https://python3wos.appspot.com/ showstoppers]
*** No MySQL-python (sqlalchemy supports mysql through other drivers)
*** No suds (there are active forks but we could also drop support?)
* Options for python2/3 support:
** Interpreter could be python2/python3 based on packages
** six layer works but not the easiest to maintain (e.g. in reprozip)
* Drop support for win-64
* Update copyright headers to 2016

== 2015 ==

=== December 30, 2015 ===
'''Updates'''
* Bokeh package finished
** Can output to Browser/IPython/Spreadsheet (Limited functionality in spreadsheet)
'''Items to Discuss'''
* Updating VisTrails dependencies
** Bokeh needs QWebEngine (Chromium) in Qt5 which requires PyQt5
*** Many plotting libraries only work in browsers
*** But Chromium may be a big and controversial dependency
*** Or create a browser version of the spreadsheet?
** Some users have requested Python 3
** Not backwards compatible?
** Target for VisTrails 3.0 with new interpreter?

=== December 16, 2015 ===
'''Updates'''
'''Items to Discuss'''
* Users list question
* [TE] Wrapping Bokeh
** Added bokeh property parser
*** complements numpydoc parser
*** Not all attributes are available, partially because I am using a pre-release version.
** Wrapped modules
*** bokeh.plotting finished (Backwards like matplotlib: Create plot then draw on it)
*** bokeh.charts mostly done (Missing arguments)
** QWebView mostly works (but no zooming or buttons)
*** It would be better to use external browser or QWebEngineView
** Added improvements to wrapper
*** Generalized port translations (Color/Path to native types)
*** Can use multiple docstring/property parsers simultaneously

=== December 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Looking into wrapper
** Will port TensorFlow
** Doing a pass on the wrapper code & doc
*** UX improvements
** Factorize high-level docstring parsers into core.wrapper? (sphinx, numpy, google)
** Problem with name vs module_name (fails sklearn tests because class_by_name() is broken)
** Looking into compressing specs, lazy registration of modules

=== December 2, 2015 ===
'''Updates'''
* [TE] Package wrapping
** Wrapped most of numpy/scipy using __all__
** Added class attribute and method access for classes (Can add to class or to separate inspector module)
** TODO: Document wrapping procedure

'''Items to Discuss'''

=== November 25, 2015 ===
'''Updates'''
* [RR] New interpreter is coming along
** Everything is a stream
** Task system, eventually work-stealing parallelism
** Streams no longer advance in lock-step
*** Allows for constructions like filter, join, sorted-merge
** depth>1 still to be tested, no current plan to allow this through the module interface
*** Through looping though, can do streams of streams

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapped most numpy functions (no polynomials)
** and half of scipy classes and functions
** Added functions manually from documentation (no parseable lists?)
** Focusing on data flow constructs (no property/method access for classes)
*** Using spec diff (empty for now) and dynamic parser (stores spec in .vistrails/)
** Python class/function wrapper now stable
** Add google doc parser?
*** Is there a parser available?

=== November 18, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Numpy class wrapping works
*** Basic type is List, since most types are array_likes.
*** TODO: More classes and functions
*** Some operations are in-place and some aren't, and docstring not super clear
*** [RR] It seems only methods mutate, and most have a numpy.xx function equivalent; just manually go through the methods and remove the mutating ones?
** Class wrapper is modular
*** Docstring parser and type string parser can be customized
*** Classes can have optional attribute/method ports
**** Inspectors and attribute/method modules can be created separately
** Use PythonCalc as an example
*** Can be re-implemented as a function with a parseable docstring
*** [RR] PythonCalc is just an example, and it might actually make sense to get rid of it, or do a proper math package with scalar operations (as separate modules, no combobox)
** [RR] TensorFlow to use wrapping as well
*** Very simple (only types 'tensor' & 'variable')

=== November 11, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapping numpy's classes using numpydoc (ndarray)
*** Wrapping constructor arguments, attribute getters/setters as module ports
**** Then how to access attributes afterwards?
***** Use input value port to class modules?
*** Wrap methods as modules? E.g., `ndarray.shape`.
*** Function wrapping is almost a subset of class wrapping
**** May be able to use the same parsing/execution methods
** VTK's non-getter/setter methods could be wrapped as modules
*** We could then remove extra logic in interpreter for keeping function order
** Bokeh uses autogenerated docstrings
*** We may be able to read the specification directly

* [RR] [https://github.com/VisTrails/VisTrails/pull/1138 TensorFlow package]
** Basic setup working, can execute the Mandelbrot example
** Will autogenerate the operations

=== November 4, 2015 ===
'''Updates'''
* [RR] Interpreter work requires a fix for [https://github.com/VisTrails/VisTrails/issues/1137 DB issue #1137]
* [DK] Kitware's Resonant [http://www.kitware.com/source/home/post/173]
** [https://github.com/girder/girder Girder]: data management system
** [https://github.com/Kitware/romanesco Romanesco]: execution engine, uses [http://www.celeryproject.org/ Celery] for task management
** Resonant Flow: web app for editing and executing workflows

'''Items to Discuss'''
* [TE] Added OSX Lion (10.7) VM on build machine using vagrant (seems ok with license?)
** New builds works on Lion
** Change the minimum requirement to 10.7?
* [TE] Package wrapping
* Added upgrade suggestions using 2 spec versions ([http://pastebin.com/30XUU8Gp example])
** using name edit distance to find matches
** Could use something better like port similarity for modules, and type similarity for ports
** Should write python upgrade code?
** Added spec to sklearn package
*** Can now diff spec versions and keep the spec static
*** There will be problems with downgrades and package versions

=== October 29, 2015 ===
'''Updates'''
* [TE] nightly-build-mac fixed (Needed to approve xcode license)

'''Items to Discuss'''
* [TE] matplotlib wrapper
** ported to general spec
** Diff can be used on general spec
*** Only needed minor changes
*** Fixed indexing bug that corrupted specs
*** Can now move diff tools to core/wrapper
** Add new plots?
*** New plots in mpl 1.3: eventplot
*** New plots in mpl 1.4: angle_spectrum, magnitude_spectrum, phase_spectrum', violinplot
*** No new plots in mpl 1.5 (from looking at boilerplate.py)

=== October 21, 2015 ===
'''Updates'''
* [RR] Alexis has arrived, will be working with [RR] on a more efficient interpreter

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package]
** Supporting multiple package versions
*** Check which version can be loaded [https://github.com/VisTrails/VisTrails/pull/1135 #1135]
*** We cannot show version requirements in the list of packages because old packages are loaded when importing the codepath
** Visual diff does not work well, but we can use the spec differ to see differences.
** Unifying vtk and matplotlib wrapping specs (WIP)
*** And porting matplotlibs spec differ to work on the general spec
*** Spec differ can then be used on vtk and other packages in the future
*** Will enable automatic upgrade generation
* [RR] Rework interpreter
** restore abstraction between interpreter/module code
** build looping, streaming, caching into the interpreter
** rework cache
** look into parallelism once basic functionality is there

=== October 14, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package] (adding numpydoc parser)

=== October 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/tree/fix-matplotlib-parser New matplotlib parser] (adding numpydoc parser)
** Added numpydoc attribute parser for plots.
*** TODO: Need better port spec reconciliation with call signature parser.
*** We can create a general numpydoc parser, but attribute types are unique to matplotlib.
** Needs package versioning
*** New spec will not support matplotlib < v1.4 due to changed path to axes classes.
*** Load spec version corresponding to installed matplotlib version?
*** Need version downgrades?

=== September 30, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Updating Matplotlib parser
** Matplotlib docstring parser fails on numpy docstrings
** I have [https://github.com/VisTrails/VisTrails/commit/eae8b0c16260810587e47c41cab53552cbb3cf0a added basic numpydoc parsing]
*** Only used by a few docstrings so far
*** Parsing uses many sources (class tables, signatures, ACCEPTS, method docstrings, definition parsing).
** Caswell said they were thinking about moving to traitlets, but this is not ready yet

=== September 23, 2015 ===
'''Updates'''
* [TE] VisTrails 2.2.3 released
** Also have pushed to PyPI, binstar, etc.
** Sourceforge vs. GitHub
*** should be able to host releases on GitHub
*** nightly binaries pushed to sf each night
*** old binaries?
* [TE] Re-wrapping MatPlotlib
** Keep static generation - Docstrings are brittle beween matplotlib versions
** Keep generating the executable classes - but create functions, not vistrails Modules
*** Why is there so much patching?
** Re-implemented Alternate PortSpec for InputPortSpec
*** It will now inherit specs from parent (No need to reimplement)
** Module upgrades?

'''Items to Discuss'''

=== September 16, 2015 ===
'''Updates'''
* [TE] Job Monitor tests and documentation done
** OK to leave document package in packages directory?

'''Items to Discuss'''
* [TE] Library wrapping: How to do code patching? [https://docs.google.com/drawings/d/1Sh3eOXot6v2y880jHKQrqXqAwr-0aoqYligg3z8G8MY/edit?usp=sharing Wrapping diagram]
** Insert code into module template (Old VTK code)
** Patch the library that is called (New VTK code)
** Somehow store code in spec and apply when executed?
*** Executed code needs at a minimum access to inputs, outputs, current class
*** Use standard input/output dict and obj reference that the code operates on?
*** Can this be done while keeping the execution abstract?

* Do new release now?

=== September 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* New release?
** [RR] wants reprounzip
** tej changes & doc
** job monitor & jobmixin fixes
** mongodb
** reprounzip
** warning: MplFigure type is int
** tabledata: add Reshape, DictoToTable & ListToTable, fix ListToTable with numpy arrays
** PythonSource can have same name for an input & output
** don't show spreadsheet at exit

=== September 2, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Limit autosaves? [https://github.com/VisTrails/VisTrails/pull/1126 #1126]

=== August 26, 2015 ===
'''Updates'''
* [TE] Added Job support to Parameter Explorations (Requested by Colin), and Mashups
** specify job ids, need to specify different ids for parameter explorations since they have the same version id
** how to deal with parameters passed in on command line
* [General] provenance: should be creating a new version when we execute workflow with changed parameters?
** currently, custom_params annotation stores this in provenance currently
** [RR] API doesn't record provenance if passing in parameters: http://git.io/vsAA5
'''Items to Discuss'''

=== August 19, 2015 ===
'''Updates'''
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [TE] Working on Job Monitor documentation

'''Items to Discuss'''
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [TE] Stop testing VisTrails 2.0?

=== August 12, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Build broken on Travis; because of IPython 4 released today? ([https://travis-ci.org/VisTrails/VisTrails/builds/75279795 build 992]; [https://github.com/VisTrails/VisTrails/issues/1123 #1123])

=== August 5, 2015 ===
'''Updates'''
* [TE] Fixes to Jobs
** Could not delete jobs
** Could not run job in group
** Job not reset when calling ModuleSuspended
** Added deleting job from context menu
* [RR] Writing documentation for everything [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

'''Items to Discuss'''

=== July 29, 2015 ===
'''Updates'''
* RR still looking into new interpreter thing
** Goal is to take out scheduling logic from Module so it can be split in multiple processes, and so that smarter strategies can be added in time
** This means some work on packages
** Spreadsheet can live in kernel process? Still some UI stuff that will take work (changing configuration, persistent archive's viewer, ...)
* [TE] Problems running examples [https://github.com/VisTrails/VisTrails/pull/1111 #1111]
** Testing of more examples requires additional packages on the test machines.
** Fixed faulty line-ending in PythonSource:s failing on Python 2.6.
** Test suite now testing SUDSWebServices (If web service is down, test suite will fail)
** preferences.py test failed reloading 'dialogs' package, switched to using 'URL'.

'''Items to Discuss'''

=== July 22, 2015 ===
'''Updates'''
* [TE] mailing lists back online
* [TE] Working on [https://github.com/VisTrails/VisTrails/issues/1107 #1107]
* [RR] Working on ReproZip package

'''Items to Discuss'''
* [RR] MongoDB package [https://github.com/VisTrails/VisTrails/pull/1106 #1106]
* [RR] Example for tej docs? [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

=== July 15, 2015 ===
'''Updates'''
* 2.2.2 released

'''Items to Discuss'''
* RR is considering executing everything in an IPython kernel (i.e. separate Python interpreter, like the one spawned for a notebook)
** It's a separate process that we can restart without restarting the app/gui
** We can isolate the execution environment (e.g. for the server)
** We can run the whole thing remotely (if your data is elsewhere, just run VisTrails locally and the pipeline elsewhere)
** Pipeline execution no longer makes the interface hang, it just makes the kernel hang (but that's fine)
** We can use notebooks as modules (probably way nicer than the PythonSource module)
** We can run multiple kernels so long as the ports carry things that are serializable
*** meaning we can put the multithreaded-interpreter without all the hacky parts it has now
*** we can run IPython kernels in all the languages IPython supports, [https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages currently 46]

=== July 8, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Buildbot github hook not working after IP address change
* [TE] No reference to VistrailsApplication ([https://github.com/VisTrails/VisTrails/issues/1103 #1103])
** [RR] Added PR [https://github.com/VisTrails/VisTrails/pull/1104 #1104]
* [TE] Reopening VT file after saving with bundled subworkflow won't offer subworkflow upgrade ([https://github.com/VisTrails/VisTrails/issues/1102 #1102])
** allow manual delete to fix right now
** fix this on top of the use-uuid branch
* [TE] Release VisTrails 2.2.1? ([https://github.com/VisTrails/VisTrails/blob/v2.2/CHANGELOG CHANGELOG])
** [https://github.com/VisTrails/VisTrails/pull/1093 output-modules-use-global-dir]
** [https://github.com/VisTrails/VisTrails/milestones/version%202.2 Current issues for 2.2]

=== July 1, 2015 ===
'''Updates'''
* [TE] PROV fixed
* [TE] Working on subworkflow issues
* [RR] Considering reworking the controller (log vs exception problem, retained upgrades causing interferences) and also the interpreter (IPython?)

'''Items to Discuss'''

=== June 24, 2015 ===
'''Updates'''

'''Items to Discuss'''
* UV-CDAT
* [TE] Can a cyclic workflow be valid? ([https://github.com/VisTrails/VisTrails/issues/1097 #1097])
** focus on disabling the ability to create cyclic pipelines because more things break than just this with a cyclic pipeline
* [RR] Relative paths ([https://github.com/VisTrails/VisTrails/pull/1057 #1057])
** This interacts with the new bundle; how do handle packing files inside the VT bundle?

=== June 17, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] current_version and reusing existing upgrades are broken ([https://github.com/VisTrails/VisTrails/issues/1095 ticket #1095])
** Could be that export to PROV is using an unflushed upgrade pipeline?
** current_version would then be correct.
** It may work to flush the actions before exporting?

=== June 10, 2015 ===
'''Updates'''
* DAT: fixed VTK issue on Linux and Mac
* Still crashes on Windows. Need help! Reminder: this works in the VisTrails spreadsheet (QCellPresenter), although no widget get changed there during a drag
** Is it a VTK bug?
** Is it simply impossible to change widgets during the drag, should we do it a different way?
** Did I miss something that is done in VisTrails but somehow not in DAT?
** Low prio, UV-CDAT doesn't run on Windows anyway

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 Updated pull request])
* Single instance code and batch mode

=== June 3, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 pr])
** Requires fixes to command line parameters, Output modules, and batch mode
** How to test this
** Updated missing/outdated flags
** Fixed view issues when generating graphs
* [TE] batch mode
** SpreadsheetOutput not enabled in batch mode. Should we check is_running_gui instead?
** Other instance setting flags from caller
** Is graphsAsPdf replacing spreadsheetDumpPdf?
** graphsAsPdf true by Default?
** Batch mode executing by default (Not needed when generating graphs)
** Re-added workflowInfo as withWorkflowInfo for writing graph and xml workflow
** [DK] batch mode should be outputting to files or stdout, shouldn't always trigger SpreadsheetMode
** execute flag, maybe make execution the default and allow a "--no-execute" if you only want to capture graphs, for example

=== May 27, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] API question
** http://lists.vistrails.org/pipermail/vistrails-users/2015-May/000357.html
* Status of DAT
** Can add VCS plot to DAT but need to work on configuration windows
** Documentation for graphics templates for UV-CDAT/vcs?
* Qt support?

=== May 20, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Reviving the DAT, integrating scripting & porting UV-CDAT!
** On [https://github.com/VisTrails/DAT GitHub] ([https://github.com/VisTrails/DAT/issues issues])
** Merging 2 years of development taking longer than expected, but getting there. The plan is to get the patches in VisTrails and never fork again, we never want to get in UV-CDAT's situation (and don't need to).
** VTK cell works fine on Linux but there was flickering on Mac & Windows before; still issues on Mac (Windows status unknown)
** Can get a VCS plot soon (but will need VTK cell fix)
** Integrate in UV-CDAT's build system (so we have cdms, VCS, ...) -> RR can do this, low priority
** How do we integrate scripting?
*** We want to be able to seamlessly make changes to a plot by changing Python code
*** Define new plots by entering Python code without writing modules/packages?
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 13, 2015 ===
'''Updates'''
* [RR] Test skipping whitelist ([https://github.com/VisTrails/VisTrails/pull/1069 #1069]) -- low priority
* [RR] Custom matplotlib modules can't be compatible with both 2.1 and 2.2 ([https://github.com/VisTrails/VisTrails/issues/1067 #1067]); should be fixed for ALPS ([https://github.com/VisTrails/VisTrails/issues/1070 #1070])

'''Items to Discuss'''
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 7, 2015 ===
'''Updates'''
* [RR] Export/import workflow to Python working!

'''Items to Discuss'''
* [Claudio] UV-CDAT
** The UV-CDAT project is the biggest user base of VisTrails
** VisTrails package management provides a lot of friction towards people plugging in their code
** Need to make it easy to integrate your random Python scripts in the system without having to deal with all the boilerplate, at least in the first step
** [RR] argues that modules are still good; UV-CDAT shouldn't move towards a purely script-based backend
** [RR] export/import with Python could reduce a lot of that friction by allowing 1) to edit workflow as Python 2) to open up boxes automatically if needed code doesn't match actual modules
** ...

=== April 29, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] <strike>Abstractions</strike> subworkflows status ([https://github.com/VisTrails/VisTrails/labels/subworkflows tickets])
* [RR] matplotlib compatibility (2.1 & 2.2), [https://github.com/VisTrails/VisTrails/issues/1067 #1067]
** RR to try and fix ALPS matplotlib modules

=== April 22, 2015 ===
'''Updates'''
* 2.2.0 has been released!
* Windows issue (via email from Ryan)
** issue with manifest file (may be a new file in VTK6?)
** Tommy has regenerated new Windows builds
* Binaries, pypi, and conda released
* [RR] Export as script
* Python sources using VTK need to switch to SetInputData (users should be aware of this)

=== April 15, 2015 ===
'''Updates'''
* Ready for 2.2.0 (apart from binary/deps issues)
** Missing some libs (scikit-learn, tej, tdparser, SQLAlchemy+connectors
** Windows: runvistrails.py is no longer used, so the PATH is wrong
** Windows: pip is broken, but it probably wouldn't work anyway because of permission issues (disable this?)
* Queries, upgrades and getPipeline() usage ([https://github.com/VisTrails/VisTrails/issues/1054 #1054])
** Getting a pipeline with getPipeline() is not safe: it might return an invalid pipeline
** This is used in many places throughout the code, like queries
** Upgrading would require going through the controller, but that creates new actions
* [TC] Avoid copying a module's output if it's used as input by exactly one downstream module ([https://github.com/VisTrails/VisTrails/issues/1060 #1060]) (useful for big numpy arrays you can update in-place)

=== April 8, 2015 ===
'''Updates'''
* [DK] Merged RR's changes for output modules (1012 and 1013)
** RR will merge remaining changes, then create v2.2 branch!

'''Items to Discuss'''
* BNL need numpy array to VTK image
** Looks like VTK has some helpers for this
** We will help if issues arise
** Will contribute back to VisTrails package
* Upgrade issue: [https://github.com/VisTrails/VisTrails/issues/1017 #1017]
** Automatic upgrades should happen between versions of provided upgrades
** Our existing upgrades work around this so it doesn't need to be 2.2.0
* Corner-case VTK modules
** No longer need VTKCell input port, so don't interfere with registry and API anymore
** Still work weirdly, people probably shouldn't use them
** But we have lots of clunky modules since we wrap the whole of VTK; some people might rely on this and know how to use them, let's keep them anyway
** Ready for 2.2.0

=== April 1, 2015 ===
'''Updates'''
* [RR] UV-CDAT: bugfixing for 2.2, long-term plans: implement scripting import/export in VisTrails, port to UV-CDAT
* Possibly, try to move to regular VisTrails to use new features

'''Items to Discuss'''
* 2.2 release: nothing much is pending anymore, release next week?
** [TE] vtkExporter classes [https://github.com/VisTrails/VisTrails/issues/1032 #1032]
** [RR] Hiding upgrades in version tree might make it (or might be 2.2.1 so we can test it out) [https://github.com/VisTrails/VisTrails/issues/949 #949]
** Output modules changes to go in
* add note to documentation about order of parameters in VTK
* add issue about exporter upgrades if not already there

=== March 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* 2.2 release
** Checklist on Github: https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist
** Review output modules
** RR has a couple more issues to fix
** Ready to go -- sign app package for OSX? [https://github.com/VisTrails/VisTrails/issues/984 #984] We need access to the Apple Membership team

=== March 18, 2015 ===
'''Updates'''
* [TE] VTK6 works

'''Items to Discuss'''
* [RR] Release v2.1.5 with backported tabledata?
** MTA example needs updated tabledata (for JoinTables)
** Google Maps package still not available
* [RR] Work torward v2.2.0?
** changes:
*** new persistence
*** API changes
*** output module changes (upgrades?), maintain cells but try to upgrade
*** not wrapping stuff
*** VTK6? yes
*** JobSubmission stuff?
*** relabeling for upgrades [https://github.com/VisTrails/VisTrails/issues/949 #949]
** makes sense, needs the tree view code to be updated, check selection
** See [https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist 2.2 checklist]
* Discussion of [https://github.com/VisTrails/VisTrails/issues/1016 #1016]
** plumbing between outputs and output modes, how to define a mode that works for many outputs without writing for each output?

=== March 11, 2015 ===
'''Updates'''
* [RR] persistent_archive done; merge? ([https://github.com/VisTrails/VisTrails/pull/755 #755])
** note about the focus events for widgets
** TE be aware of file_archive for future binaries that include persistent_archive
* [TE] [https://github.com/VisTrails/VisTrails/pull/998 New VTK package] finished

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails? (see last week; decision needed)
** RR email to JF about this
** yes; email sent to Github
* [RR] Switching order of output ports ([https://github.com/VisTrails/VisTrails/pull/1006 #1006])
** added port specs are sorted at a separate spot (Module.*_port_specs properties) than those in the registry (which are sorted in the registry), but those two lists are just combined without respect to sort keys
** need to determine whether the two lists should be merged or remain distinct
** should make sure that order of input ports and output ports makes parallel connections for things with same order
** DK suggests breaking backward compatibility here: workflows still run, can fix easily if a problem in an existing package.
* [RR] Question about output modes ([https://github.com/VisTrails/VisTrails/pull/1007 #1007]), how to integrate in API ([https://github.com/VisTrails/VisTrails/pull/24 #24])
** Should ImageFileMode be removed? ("image" is not a mode, "file" is)
** ImageOutput missing?
** Feel free to change how formats works
* [TE] Test suite segfaults on Fedora 17 virtualbox. Install newer version? (Support ended in 2013)

=== March 4, 2015 ===
'''Updates'''
* [TE] VTK wrapper
** Works on VTK 5.10
** Still need to test VTK 6
** New general wrappers for python functions and classes

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails?
** When [http://i.imgur.com/UTY2qfg.png filing a pull request] from UV-CDAT/VisTrails, VisTrails/VisTrails is selected by default
** People keep forgetting to change the default ([https://github.com/VisTrails/VisTrails/pull/956 #956] [https://github.com/VisTrails/VisTrails/pull/968 #968] [https://github.com/VisTrails/VisTrails/pull/999 #999] [https://github.com/VisTrails/VisTrails/pull/1000 #1000] [https://github.com/VisTrails/VisTrails/pull/1003 #1003] [https://github.com/VisTrails/VisTrails/pull/1004 #1004] [https://github.com/VisTrails/VisTrails/pull/1005 #1005])
** Only way to change that is to not have it marked as a fork of VisTrails/VisTrails
** Github staff [https://gist.github.com/remram44/b364c24ef1e462ce6e2f can make that change for us]; should we do it?
** Juliana: comments on this? visibility vs. convenience/annoyance for developers
* [RR] What about [https://github.com/VisTrails/VisTrails/issues/991 #991]?

=== February 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] vtkviewcell for infovis support, can we unify with VTKCell?
** need to test this
* [TE] vtk wrapping
** Mostly finished
** VTK 5.10 produce incorrect results with old wrapping
*** Old wrapper is based mostly on VTK 4
*** Most vtk_examples affected
*** [http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Replacement_of_SetInput]
*** should be able to upgrade from SetInput to SetInputData (need to drop GetOutput and replace with self ports)
*** can we change vtkInstance to just return self and not wrap things
** terminator example not working under 5.8?
* How does VTK wrapping fit into general wrapping framework?
* [RR] new persistence package

=== February 18, 2015 ===
'''Updates'''
* [RR] New VisTrails API and IPython integration ([https://github.com/VisTrails/VisTrails/pull/24 #24])

'''Items to Discuss'''
* [TE] VTK wrapping
** [https://gist.github.com/rexissimus/16b74693545b5e7c1035 Benchmarking vtk package]
*** Old: 24.7 seconds
*** New: 10.5 seconds (Except first time that adds 8 sec)
**** The parsing that calls is_abstract (that tries to instanciate all vtk classes) is now only run the first time.
**** get_items_from_sigstring takes 2 seconds, maybe we can use a lookup dict for already computed sigstrings?
** Now using a general python function wrapper
*** VTK classes are wrapped into python function that does not depend on vistrails
*** VTK functions can be executed without vistrails
*** The spec maps functions into vistrails modules, but can also describe wrapping
*** A general python function wrapper that supports
**** kwarg inputs
**** single, list, dict outputs
**** callback for progress reporting
**** temporary file generator for using FilePool
**** optional output generation
*** Creating specs:
***** Create spec by hand
***** Auto-create spec outline (TODO) and manually finish it
***** Dynamically create spec (VTK)
***** Implement documentation wrappers (Can use scikitlearn wrapper to wrap numpydoc) (TODO)
***** Classes as bad functions needs to be wrapped in new functions before they are wrapped. This is different for each package.
****** Classes is hard: Like VTK, and matplotlib. Scikit-learn does still not wrap classes
***** Spec diffing and patching could be done using code from matplotlib.
** Still needs upgrades from old VTK package
*** Is it possible to dynamically wrap functions, e.g, you see a SetFunc and just remove the 'Set' prefix. Or do you need to create a complete mapping?

=== February 11, 2015 ===
'''Updates'''
* Update from Friday's meeting
** discussed VisTrails internals
** discussed wrapping
*** xml discussion, hard to modify because tied to db code
*** TE has made it possible to add the schema-defined attributes to the intermediate representation
*** higher-level operations on the port specs
** make sure the simple case works
*** [JF] take a simple package with documentation and figure out what the base case for wrapping is

'''Items to Discuss'''
* [TE] VTK wrapping
** Dynamic loading works
** Reading XML is fast enough, but [https://gist.github.com/rexissimus/8272d3c776ccfa115d82 unserializing data is slow]
** Working on patterns for patching
** Matplotlib has many advanced patterns like argument ordering, nested arguments, alternateSpecs, output types.
*** Having all this in a general wrapper might confuse users?
** [RR] Delay module (except for identifiers) until you need it---e.g. don't deal with port specs, etc. until necessary
* Scripting Support [https://github.com/VisTrails/VisTrails/pull/950 #950]
** [RR] Issue with getting code from modules
** Design a simple solution
** [JF] Couldn't you use modules as black boxes without conversion, just to call into modules/subworkflows easily from e.g. IPython?
*** [RR] This is a job for the API, and a very separate use case. See [https://github.com/VisTrails/VisTrails/pull/24 #24]

=== February 4, 2015 ===
'''Updates'''

'''Items to Discuss'''
* Wrapping
** Format to use? Currently XML (like current matplotlib)
*** JSON and YAML have simple "to python dictionary" methods
*** But don't stream
*** YAML a lot easier for humans
** [DK] vtk-new-package also changes parameter names, creates enumerations
*** intermediate schema needs to be extensible
*** packages will want to store there specific infos for compute() method generation
*** also might have specs-altering info, like matplotlib's alternateSpec
** representation to code , registry already has schema for some aspects
** [RR] We might want to see if Module subclasses can be created lazily
*** no need to create all the classes just to register them in the registry and never actually use most of them
*** future effort
* [RR] Where should VisTrails packages live?
** tej installs as 'vistrailspkg.tej', TE installed it as 'userpackages.tej'
** Currently, standard packages are 'vistrails.packages.', user packages are 'userpackages.' and packages loaded through pkg_resources might be anything
** [RR] Use 'vistrailspkg.' everywhere?
** Long-term effort to simplify package distribution/installation (and have VisTrails get them automatically?)

=== January 28, 2015 ===
'''Updates'''
* T. Caswell to come visit on Fri 6 to discuss wrapping work

'''Items to Discuss'''
* [TE] New VTK wrapping
** Current code by DK seems a good deal faster
** Generates XML that can be patched/tweaked, generates Python code from it, VisTrails only loads generated Python code
** RR would rather have VisTrails load intermediate representation (= XML) directly, wants to make sure this is not slower
** The goal is to turn the intermediate step into something generic that would be used for every wrapped package (vtk, numpy, matplotlib, sklearn, java) instead of each having its own
** TC has its own code at [https://github.com/Nikea/VTTools/blob/master/vttools/wrap_lib.py github:VTTools] which parses numpy docstrings and generates modules, doesn't yet handle classes or persist anything
* Web crawler
** Right now, TE starts jobs for "start crawler", "stop crawler", "install classifier"
** RR would rather have the crawling be a job as far as VisTrails and tej are concerned
** The whole thing would be one pipeline: load examples, train classifier, start crawler [check for job, kill previous one, upload model, start processes], get snapshot, visualize
*** Need some support in tej and job submission system: long-running jobs, stop a job (wait for it to finish?), restart a job even though results are cached

=== January 21, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Unified wrapping method discussion [https://github.com/VisTrails/VisTrails/issues/991 #991]
** TE to work on reusable method with intermediate representation, starting with VTK
* [RR] Examples for scikit-learn: JF has an old example using Weka with parameter exploration (not currently in source tree)
** AM's examples are enough
* [AM] scikit-learn package is done, merge it in? [https://github.com/VisTrails/VisTrails/pull/955#issuecomment-70286788 #955]
** RR will merge
* [RR] What should copyright headers say? [https://github.com/VisTrails/VisTrails/pull/994#issuecomment-70173935 #994]
** Let's keep everything in there: Utah/Poly/NYU

=== January 14, 2015 ===
'''Updates'''
* [TE] Working on classifier
* [RR] Scripting integration, work in progress

'''Items to Discuss'''
* [RR] Unified wrapping method discussion ([https://github.com/VisTrails/VisTrails/issues/991 #991])
** Let's talk next week, [AM] and [DK] are not here

=== January 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* make sure that we address critical issues, questions, and pending review branches in a timely manner
* scripting support
** [RR] no issues if we want to just keep annotations in the generated code to allow the link back to a workflow
** [RR] can translate from workflow to script, working on script to workflow
** will work for parameter value changes, structural changes require changes to the annotations
** need to publish best practices here
** would be cool to do looping in scripts (easier interface than with workflows)
* notebook support (convert form notebook to workflow)
** RR will sync with FC on this
* Issue with console in built-from-scratch
** [TC] iPython rearranged some of the completion stuff in 2.2 and 2.3
** binary has old version of iPython -> 1.0.0, should we update?
* [TC] automated wrapping of numpy and scipy
** discovered a bunch of malformed documentation in numpy and scipy
** has github repo for vistrails tools
** example modules wrap a bunch of R stuff (not baked in, just how things are)
** will be pushing wrapping logic up
** port names forbidden (window and domain)
** have an import hook to get from yaml directly to VisTrails Modules
** should work for any python modules with well-formed numpy docstrings.
* [Action] should make it clear in documentation that Constant now means serializable not that the value doesn't change (e.g. List)
* [TC] might be interesting to try to build components of matplotlib and accumulate in figure (long-term project, but thinking about how this might work)
* [TE] build and build scripts
** completely automatic, buildbot
** need to set the build machines for the environment we want for the binary
** would virtualenv work here?
** [TC] anaconda can pin versions, potential path to test different configurations
** Q: upload nightly binary builds? A: makes sense, make sure they are well-labeled
* sourceforge stats: e.g. http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07
* package issues (see Remi's message)
* [TE] Scope of tej
** Support single ssh commands?
** Queue can be used as a remote machine (crawler is using queue.call*)
* SourceForge stats: http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07

== Older meetings ==
* [[Development/2014]]
* [[Development/2013]]
* [[Development/2012]]
* [[Development/2011]]
* [[Development/2010]]

Development

2016-04-13T14:48:37Z

Tommy: /* April 13, 2016 */

<div class="nonumtoc toclimit-1">
__TOC__
</div>

See also the [https://github.com/VisTrails/VisTrails/wiki/Development Github wiki]

== 2016 ==

=== April 13, 2016 ===
'''Updates'''
* [TE] Chaining upgrades done ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])

'''Items to Discuss'''
* [TE] Iterating handle_invalid_pipeline ([https://github.com/VisTrails/VisTrails/pull/1165 #1165])
** Not based on [https://github.com/VisTrails/VisTrails/tree/chain-upgrades-loop chain-upgrades-loop]
** Cherry-pick test to preserve source?
** Need maxPipelineFixAttempts option?
*** The code is now smarter about recursion, so max attempts will "probably" never be reached.
** Need [https://github.com/VisTrails/VisTrails/commit/0ef0667426937eddb1d1c1e397f0657ffec039a9 debug messages]?

=== April 6, 2016 ===
'''Updates'''
* [TE] Query View improvements
** Done except for displaying "Version Info" and #1164
* [RR] Working on finishing new interpreter (finally!)

'''Items to Discuss'''
* [TE] Chaining upgrades ([https://github.com/VisTrails/VisTrails/pull/1164 #1164])
** Try latest upgrade first, then previous.
** If all fail, select latest upgrade?

=== March 30, 2016 ===
'''Updates'''

'''Items to Discuss'''

* [TE] Query View improvements
** Unified do_version_switch and get_upgrades as validate_version()
** Problems with query view using its own controller
*** Fixed module info not being displayed for query results
*** Still no version info for query results
*** Still an issue with version query view not being updated

=== March 23, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Usage reporting almost ready to go
** Need to record whether specific features are used: paramexpore, mashup, query
*** [DK] Record if LaTeX extension is used? But hard to distinguish from direct batch invocation
** How to record size of vistrail?
*** [DK] IdScope already walks over vistrail, use that
*** but total number of modules and versions doesn't give an idea of average size of individual pipelines

=== March 16, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Upgrades in Query Mode
** Now using code similar to do_version_switch
*** Uses handle_invalid_pipeline
*** Differences: Not using current_pipeline, flushes changes
*** New controller method get_pipeline optimized using cached pipelines (but not current_pipeline)
*** Integrate to avoid repeated code?
*** Use this for query mode?
* [TE] VisTrails 2.2.4 ready for release?
** tej package updated. Others?
* [JF] upgrades and the version tree
* [JF] provenance in Jupyter
* [DK] bundles: [https://github.com/VisTrails/VisTrails/pull/1092 #1092]

=== March 9, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixing search mode
** String query now matches all by default
*** This caused pipeline queries to never match
** String query can search: User/Notes/Tagname/Time/Module name
*** Should we search module names by default? (Disabled by default because it is expensive)
*** Fixed notes search
** '>' parameter queries in documentation but has been removed
** Fixed module matches for upgraded pipelines (By not upgrading pipeline)
*** Upgrades still a problem
*** Add "Upgrade all menu option?" (Or upgrade all on open when `hideUpgrades`)
*** [JF] Allow search on past tags

* [TE] Create new bugfix release
** Finish querying
** Path issue on windows

* [DK] Look into sqlalchemy and new bundle branches

=== March 2, 2016 ===
'''Updates'''
* [TE] Fixed cache bug with port specs
* [TE] VisTrails Next
** Most packages now work
** No qgis for Python 3

'''Items to Discuss'''
** Always dereference symlinks? [https://github.com/VisTrails/VisTrails/issues/1146 #1146]

=== February 23, 2016 ===
'''Updates'''
* [TE] Fixed PythonSource 100% CPU bug
* [TE] VisTrails Next
** Updated [http://opendap.co-ops.nos.noaa.gov/axis/webservices/wind/ NOAA Web Service] examples
*** Now uses REST service, tabledata, and Google Maps
*** Web Service replaced with DownloadFile

'''Items to Discuss'''
* [RR] Couple of fixes are in for API, and tej&reprounzip on the Mac binary. Also new release of tej, and working on anonymous usage reports.
** New 2.2 release soon?
* [RR] Anonymous usage reports
** Sends out info like number of modules & versions, packages used, Python & libs versions, execution time, specific features [https://github.com/VisTrails/VisTrails/pull/1154 #1154]
* [JF] Bring in noWorkflow to track variable dependencies, for the considered Jupyter integration?
* noWorkflow - provenance for python scripts
** Recent work on tracking dependencies
* Also integrates ReproZip with Jupyter
** [http://mybinder.org mybinder]
*** Use with ReproZip to automatically build Jupyter notebook interfaces
* Daves comments on Jupyter integration
** It is possible to identify cell order on the server side
** Not trivial to track order of cells on client side
* How does Galaxy workflows relate to VisTrails?
** Packaging in Galaxy is hard
** Galaxy for biomedical workflows, difficulty making it general
* Action items
** How difficult to track cell dependencies in Jupyter notebooks?
** Use noWorkflow to track cell dependencies?
** How difficult to modify mybinder to use ReproZip packages?

=== February 17, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Fixed Group memory usage
** Modules in groups are supposed to be freed when done executing
*** Prevented by logger that stored references to the modules (fixed, now using id(module))
*** Prevented by list iterator bug that stored list of modules on the 'self' port bug (fixed)
* [TE] VisTrails Next
** Removed deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** PythonSources will be upgraded
*** Fixes for Python < 3
*** fixes for VTK < 6
** TODOs
*** Remove RemoteQ
**** Port Hadoop to tej (Already have pbs)
*** Merge package wrapper
*** Finish SQLAlchemy branch
*** Finish new bundle branch
** [JF] Will contact Jeff and Matthias about moving to Python 3
* [JF] Query by Example is broken
* [JF] VisTrails Data Cleaning Project
** Use VisTrails to process and explore task-specific data while keeping provenance.
** Remi's Idea
*** Use VisTrails as the backend in a Jupyter notebook
*** Overcome problems with executing cells in random order
**** Interesting research topic, but little interest has yet been noted
*** Interesting to study how such a notebook would be used (Is there notebook usage data available?)
*** Impose restrictions to notebook cell boundaries
*** It will only work for functional operations
*** Can we fix, or detect, non-functional (mutating) operations?
*** Analyse code and data flow and see if it mutates data in unexpected ways?
*** Mutable operations can be created in many ways in Python
* Next meeting Tuesday 11:30

=== February 10, 2016 ===
'''Updates'''

'''Items to Discuss'''
* VisTrails Next
** Test suite passes
*** Python 3 less deterministic, module upgrade order random.
** [RR] updating packages: Reprounzip (pushed), tej, persistent_archive, ...
** All of our packages should run fine :)
** VTK thumbnail comparison works
*** Rendering bug on some systems
**** QVTKCell now inherits QGLWidget
*** Old thumbnails had wrong height due to spreadsheetwindow being too small
**** Fixed by regenerating thumbnails
*** Silenced deprecation messages when generating modules
*** Many new classes in VTK 7
** Remove deprecated code
*** Core imports that should be gui imports
*** GetInputFromPort etc.
**** Will break existing PythonSources
**** Try to upgrade?
*** Old-style packages
**** Or only allow a new style, like __init__.py renamed to info.py? (merge with identifiers.py?)
***** Read info.py without importing package?
*** Fixes for Python < 3
*** Fixes for Qt < 5
*** fixes for VTK < 7
*** Remove self port?

=== February 3, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] [http://lists.vistrails.org/pipermail/vistrails-users/2016-January/000402.html Rendering a .pvd (ParaView) file?]

* VisTrails Next
** All tests but thumbnail comparison passes
** Still issues with gui and more packages needs to be tested
** PythonSource and MplSource upgraded with lib2to3
** Keep contrib packages? Update?
** [https://blog.kitware.com/vtk-7-0-0/ VTK 7 is released]
*** Supports Python 3
*** Will hopefully get into conda and others soon
*** Deprecates a bunch of modules

* [https://travis-ci.org/VisTrails/VisTrails/builds/106743348 Travis builder] for VisTrails Next
** Runs!
** Uses conda
*** Many levels of requirements
**** apt packages
**** conda packages
**** python packages in requirements.txt
**** python packages in setup.py
*** Can probably drop conda. Default builder does not have Qt5, but beta builder do!
*** But useful if we want to use conda in our own build process.
** Lots of errors I do not get locally?

* [http://goo.gl/forms/Z4HBrwaBWL User Survey]
** Have you used any alternatives to vistrails?
*** Relevant? More options?
** How often do you use any of these particular features in VisTrails?
*** Add/Remove alternatives?
** How important would you rank the following potential improvements to VisTrails?
*** Add alternatives?

=== January 27, 2016 ===
'''Updates'''
* New interpreter
** Working prototype soon
** Looping not completely done (and port combination mode: pairwise/cartesian...)
** Need to integrate with VisTrails
*** Compatibility with existing modules
*** Use log controller
*** Want to cache at multiple levels (whole stream/single element of stream)
*** Non-runtime attributes of modules (cache check, automatic conversion check, constant from/to string)

'''Items to Discuss'''
* User Survey

* ZMQ failing on windows (vistrails-users)

* [TE] [https://github.com/VisTrails/VisTrails/pull/1143 Python 3 branch]
** Testsuite almost passes
*** Failing are unicode filenames, some users guide examples, and thumbnail comparisons.
** Fixed issues
*** Signatures are now bytes (convert to string to show in widget)
*** Cannot compare different types, e.g., (None < 1)
**** PortSpec.depth and min/maxConn could be None. (Backport!)
**** cell.row could be None
*** Lots of unicode/bytes fixes to serializations
**** We have encryption implementations in the code! (keychain)
*** Lots of small fixes to package method differences
** Current issues
*** logging widget empty?
*** version tree signals messed up
*** provenance view legend icons black
*** Text do not fit in some widgets
*** VTK thumbnail comparison fails
**** VTK Cells have some faces in wrong direction?
**** Because running in VM?
** Installing on Ubuntu LTS/Latest Mint
*** Install latest matplotlib from pip
*** Install VTK 7.0.0rc2 from source
*** No QtWebEngine binary (controversial) (Must install sip/PyQt5/Qt5 from source)

=== January 20, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Backporting features from Python 3 + PyQt5 + Qt5
** Merged unicode with master ([https://github.com/VisTrails/VisTrails/tree/unicode unicode])
*** One unicode test failing
*** Problem saving to xml
** Used [http://python-future.org/ python-future] to run futurize stage 1 to update legacy (pre 2.6) code ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized unicode-futurized])
*** Updates print to functions 'from __future__ import print_function'
*** Updates exception calls to use 'as'
*** removes most usages of 'long' (mostly used unnecessarily)
**** Only needed for 32-bit support
*** Fixes relative imports (from __future__ import absolute_import)
** Fixing code that is deprecated in Qt 4.8 and removed in Qt 5 ([https://github.com/VisTrails/VisTrails/tree/unicode-futurized-qt5 unicode-futurized-qt5])
*** Updated all signals to new-style
* If we go 2 to 3, this could break packages
** means we should schedule any package format changes for the same time
** e.g., imports should be unrelated to code path (function to load module from package identifier?) (take them out of vistrails.* [https://github.com/VisTrails/VisTrails/pull/1002 #1002])
** any structural changes (e.g. the __init__ versus init thing) (RR thinks it makes sense, though having both named "init" is unfortunate)
** putting package identifier as xml?
*** Python not so bad, plus some stuff in there is Python code (checking dependencies)
** version the APIs?
*** RR planning on versioning vistrails_module.Module, no point versioning the whole package?
* file formats on 2 to 3:
** no real translation/upgrade, but non-ascii values that work on 3 won't load in 2

=== January 13, 2016 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://gist.github.com/rexissimus/dfd27e466427529c385c Porting to Python 3 / PyQt5]
** Basic GUI and execution works
** Minimal work to support 2to3
** Hard to support both PyQt4 and PyQt5

=== January 6, 2016 ===
'''Updates'''
'''Items to Discuss'''
* Updating VisTrails dependencies
** Successfully built [https://gist.github.com/rexissimus/f1a1aada7de1c00a57c7 Win7-64/Python3/PyQt5/Qt5/WebEngine/VTK7]
*** VTK 7 is the first supporting Python 3 but is only in release candidate phase.
**** Next version of VTK 6 is rumored to support Python 3
**** There is a development branch of VTK 6 supporting Python 3
*** Can travis build this?
**** We can skip tests for WebEngine and VTK if needed
** Python 3 [https://python3wos.appspot.com/ showstoppers]
*** No MySQL-python (sqlalchemy supports mysql through other drivers)
*** No suds (there are active forks but we could also drop support?)
* Options for python2/3 support:
** Interpreter could be python2/python3 based on packages
** six layer works but not the easiest to maintain (e.g. in reprozip)
* Drop support for win-64
* Update copyright headers to 2016

== 2015 ==

=== December 30, 2015 ===
'''Updates'''
* Bokeh package finished
** Can output to Browser/IPython/Spreadsheet (Limited functionality in spreadsheet)
'''Items to Discuss'''
* Updating VisTrails dependencies
** Bokeh needs QWebEngine (Chromium) in Qt5 which requires PyQt5
*** Many plotting libraries only work in browsers
*** But Chromium may be a big and controversial dependency
*** Or create a browser version of the spreadsheet?
** Some users have requested Python 3
** Not backwards compatible?
** Target for VisTrails 3.0 with new interpreter?

=== December 16, 2015 ===
'''Updates'''
'''Items to Discuss'''
* Users list question
* [TE] Wrapping Bokeh
** Added bokeh property parser
*** complements numpydoc parser
*** Not all attributes are available, partially because I am using a pre-release version.
** Wrapped modules
*** bokeh.plotting finished (Backwards like matplotlib: Create plot then draw on it)
*** bokeh.charts mostly done (Missing arguments)
** QWebView mostly works (but no zooming or buttons)
*** It would be better to use external browser or QWebEngineView
** Added improvements to wrapper
*** Generalized port translations (Color/Path to native types)
*** Can use multiple docstring/property parsers simultaneously

=== December 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Looking into wrapper
** Will port TensorFlow
** Doing a pass on the wrapper code & doc
*** UX improvements
** Factorize high-level docstring parsers into core.wrapper? (sphinx, numpy, google)
** Problem with name vs module_name (fails sklearn tests because class_by_name() is broken)
** Looking into compressing specs, lazy registration of modules

=== December 2, 2015 ===
'''Updates'''
* [TE] Package wrapping
** Wrapped most of numpy/scipy using __all__
** Added class attribute and method access for classes (Can add to class or to separate inspector module)
** TODO: Document wrapping procedure

'''Items to Discuss'''

=== November 25, 2015 ===
'''Updates'''
* [RR] New interpreter is coming along
** Everything is a stream
** Task system, eventually work-stealing parallelism
** Streams no longer advance in lock-step
*** Allows for constructions like filter, join, sorted-merge
** depth>1 still to be tested, no current plan to allow this through the module interface
*** Through looping though, can do streams of streams

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapped most numpy functions (no polynomials)
** and half of scipy classes and functions
** Added functions manually from documentation (no parseable lists?)
** Focusing on data flow constructs (no property/method access for classes)
*** Using spec diff (empty for now) and dynamic parser (stores spec in .vistrails/)
** Python class/function wrapper now stable
** Add google doc parser?
*** Is there a parser available?

=== November 18, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Numpy class wrapping works
*** Basic type is List, since most types are array_likes.
*** TODO: More classes and functions
*** Some operations are in-place and some aren't, and docstring not super clear
*** [RR] It seems only methods mutate, and most have a numpy.xx function equivalent; just manually go through the methods and remove the mutating ones?
** Class wrapper is modular
*** Docstring parser and type string parser can be customized
*** Classes can have optional attribute/method ports
**** Inspectors and attribute/method modules can be created separately
** Use PythonCalc as an example
*** Can be re-implemented as a function with a parseable docstring
*** [RR] PythonCalc is just an example, and it might actually make sense to get rid of it, or do a proper math package with scalar operations (as separate modules, no combobox)
** [RR] TensorFlow to use wrapping as well
*** Very simple (only types 'tensor' & 'variable')

=== November 11, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Package wrapping
** Wrapping numpy's classes using numpydoc (ndarray)
*** Wrapping constructor arguments, attribute getters/setters as module ports
**** Then how to access attributes afterwards?
***** Use input value port to class modules?
*** Wrap methods as modules? E.g., `ndarray.shape`.
*** Function wrapping is almost a subset of class wrapping
**** May be able to use the same parsing/execution methods
** VTK's non-getter/setter methods could be wrapped as modules
*** We could then remove extra logic in interpreter for keeping function order
** Bokeh uses autogenerated docstrings
*** We may be able to read the specification directly

* [RR] [https://github.com/VisTrails/VisTrails/pull/1138 TensorFlow package]
** Basic setup working, can execute the Mandelbrot example
** Will autogenerate the operations

=== November 4, 2015 ===
'''Updates'''
* [RR] Interpreter work requires a fix for [https://github.com/VisTrails/VisTrails/issues/1137 DB issue #1137]
* [DK] Kitware's Resonant [http://www.kitware.com/source/home/post/173]
** [https://github.com/girder/girder Girder]: data management system
** [https://github.com/Kitware/romanesco Romanesco]: execution engine, uses [http://www.celeryproject.org/ Celery] for task management
** Resonant Flow: web app for editing and executing workflows

'''Items to Discuss'''
* [TE] Added OSX Lion (10.7) VM on build machine using vagrant (seems ok with license?)
** New builds works on Lion
** Change the minimum requirement to 10.7?
* [TE] Package wrapping
* Added upgrade suggestions using 2 spec versions ([http://pastebin.com/30XUU8Gp example])
** using name edit distance to find matches
** Could use something better like port similarity for modules, and type similarity for ports
** Should write python upgrade code?
** Added spec to sklearn package
*** Can now diff spec versions and keep the spec static
*** There will be problems with downgrades and package versions

=== October 29, 2015 ===
'''Updates'''
* [TE] nightly-build-mac fixed (Needed to approve xcode license)

'''Items to Discuss'''
* [TE] matplotlib wrapper
** ported to general spec
** Diff can be used on general spec
*** Only needed minor changes
*** Fixed indexing bug that corrupted specs
*** Can now move diff tools to core/wrapper
** Add new plots?
*** New plots in mpl 1.3: eventplot
*** New plots in mpl 1.4: angle_spectrum, magnitude_spectrum, phase_spectrum', violinplot
*** No new plots in mpl 1.5 (from looking at boilerplate.py)

=== October 21, 2015 ===
'''Updates'''
* [RR] Alexis has arrived, will be working with [RR] on a more efficient interpreter

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package]
** Supporting multiple package versions
*** Check which version can be loaded [https://github.com/VisTrails/VisTrails/pull/1135 #1135]
*** We cannot show version requirements in the list of packages because old packages are loaded when importing the codepath
** Visual diff does not work well, but we can use the spec differ to see differences.
** Unifying vtk and matplotlib wrapping specs (WIP)
*** And porting matplotlibs spec differ to work on the general spec
*** Spec differ can then be used on vtk and other packages in the future
*** Will enable automatic upgrade generation
* [RR] Rework interpreter
** restore abstraction between interpreter/module code
** build looping, streaming, caching into the interpreter
** rework cache
** look into parallelism once basic functionality is there

=== October 14, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/pull/1133 New matplotlib package] (adding numpydoc parser)

=== October 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] [https://github.com/VisTrails/VisTrails/tree/fix-matplotlib-parser New matplotlib parser] (adding numpydoc parser)
** Added numpydoc attribute parser for plots.
*** TODO: Need better port spec reconciliation with call signature parser.
*** We can create a general numpydoc parser, but attribute types are unique to matplotlib.
** Needs package versioning
*** New spec will not support matplotlib < v1.4 due to changed path to axes classes.
*** Load spec version corresponding to installed matplotlib version?
*** Need version downgrades?

=== September 30, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Updating Matplotlib parser
** Matplotlib docstring parser fails on numpy docstrings
** I have [https://github.com/VisTrails/VisTrails/commit/eae8b0c16260810587e47c41cab53552cbb3cf0a added basic numpydoc parsing]
*** Only used by a few docstrings so far
*** Parsing uses many sources (class tables, signatures, ACCEPTS, method docstrings, definition parsing).
** Caswell said they were thinking about moving to traitlets, but this is not ready yet

=== September 23, 2015 ===
'''Updates'''
* [TE] VisTrails 2.2.3 released
** Also have pushed to PyPI, binstar, etc.
** Sourceforge vs. GitHub
*** should be able to host releases on GitHub
*** nightly binaries pushed to sf each night
*** old binaries?
* [TE] Re-wrapping MatPlotlib
** Keep static generation - Docstrings are brittle beween matplotlib versions
** Keep generating the executable classes - but create functions, not vistrails Modules
*** Why is there so much patching?
** Re-implemented Alternate PortSpec for InputPortSpec
*** It will now inherit specs from parent (No need to reimplement)
** Module upgrades?

'''Items to Discuss'''

=== September 16, 2015 ===
'''Updates'''
* [TE] Job Monitor tests and documentation done
** OK to leave document package in packages directory?

'''Items to Discuss'''
* [TE] Library wrapping: How to do code patching? [https://docs.google.com/drawings/d/1Sh3eOXot6v2y880jHKQrqXqAwr-0aoqYligg3z8G8MY/edit?usp=sharing Wrapping diagram]
** Insert code into module template (Old VTK code)
** Patch the library that is called (New VTK code)
** Somehow store code in spec and apply when executed?
*** Executed code needs at a minimum access to inputs, outputs, current class
*** Use standard input/output dict and obj reference that the code operates on?
*** Can this be done while keeping the execution abstract?

* Do new release now?

=== September 9, 2015 ===
'''Updates'''

'''Items to Discuss'''
* New release?
** [RR] wants reprounzip
** tej changes & doc
** job monitor & jobmixin fixes
** mongodb
** reprounzip
** warning: MplFigure type is int
** tabledata: add Reshape, DictoToTable & ListToTable, fix ListToTable with numpy arrays
** PythonSource can have same name for an input & output
** don't show spreadsheet at exit

=== September 2, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Limit autosaves? [https://github.com/VisTrails/VisTrails/pull/1126 #1126]

=== August 26, 2015 ===
'''Updates'''
* [TE] Added Job support to Parameter Explorations (Requested by Colin), and Mashups
** specify job ids, need to specify different ids for parameter explorations since they have the same version id
** how to deal with parameters passed in on command line
* [General] provenance: should be creating a new version when we execute workflow with changed parameters?
** currently, custom_params annotation stores this in provenance currently
** [RR] API doesn't record provenance if passing in parameters: http://git.io/vsAA5
'''Items to Discuss'''

=== August 19, 2015 ===
'''Updates'''
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [TE] Working on Job Monitor documentation

'''Items to Discuss'''
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [TE] Stop testing VisTrails 2.0?

=== August 12, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Internal docs [https://github.com/VisTrails/VisTrails/pull/1116 #1116]
** On ReadTheDocs: [http://vistrails.readthedocs.org/ vistrails.readthedocs.org]
* [RR] JobMixin and JobMonitor: stable now?
** Definitely needs more tests
* [RR] Improvements to tej, users' guide entry & example [https://github.com/VisTrails/VisTrails/pull/1105 #1105]
* [RR] Build broken on Travis; because of IPython 4 released today? ([https://travis-ci.org/VisTrails/VisTrails/builds/75279795 build 992]; [https://github.com/VisTrails/VisTrails/issues/1123 #1123])

=== August 5, 2015 ===
'''Updates'''
* [TE] Fixes to Jobs
** Could not delete jobs
** Could not run job in group
** Job not reset when calling ModuleSuspended
** Added deleting job from context menu
* [RR] Writing documentation for everything [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

'''Items to Discuss'''

=== July 29, 2015 ===
'''Updates'''
* RR still looking into new interpreter thing
** Goal is to take out scheduling logic from Module so it can be split in multiple processes, and so that smarter strategies can be added in time
** This means some work on packages
** Spreadsheet can live in kernel process? Still some UI stuff that will take work (changing configuration, persistent archive's viewer, ...)
* [TE] Problems running examples [https://github.com/VisTrails/VisTrails/pull/1111 #1111]
** Testing of more examples requires additional packages on the test machines.
** Fixed faulty line-ending in PythonSource:s failing on Python 2.6.
** Test suite now testing SUDSWebServices (If web service is down, test suite will fail)
** preferences.py test failed reloading 'dialogs' package, switched to using 'URL'.

'''Items to Discuss'''

=== July 22, 2015 ===
'''Updates'''
* [TE] mailing lists back online
* [TE] Working on [https://github.com/VisTrails/VisTrails/issues/1107 #1107]
* [RR] Working on ReproZip package

'''Items to Discuss'''
* [RR] MongoDB package [https://github.com/VisTrails/VisTrails/pull/1106 #1106]
* [RR] Example for tej docs? [https://github.com/VisTrails/VisTrails/pull/1105 #1105]

=== July 15, 2015 ===
'''Updates'''
* 2.2.2 released

'''Items to Discuss'''
* RR is considering executing everything in an IPython kernel (i.e. separate Python interpreter, like the one spawned for a notebook)
** It's a separate process that we can restart without restarting the app/gui
** We can isolate the execution environment (e.g. for the server)
** We can run the whole thing remotely (if your data is elsewhere, just run VisTrails locally and the pipeline elsewhere)
** Pipeline execution no longer makes the interface hang, it just makes the kernel hang (but that's fine)
** We can use notebooks as modules (probably way nicer than the PythonSource module)
** We can run multiple kernels so long as the ports carry things that are serializable
*** meaning we can put the multithreaded-interpreter without all the hacky parts it has now
*** we can run IPython kernels in all the languages IPython supports, [https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages currently 46]

=== July 8, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Buildbot github hook not working after IP address change
* [TE] No reference to VistrailsApplication ([https://github.com/VisTrails/VisTrails/issues/1103 #1103])
** [RR] Added PR [https://github.com/VisTrails/VisTrails/pull/1104 #1104]
* [TE] Reopening VT file after saving with bundled subworkflow won't offer subworkflow upgrade ([https://github.com/VisTrails/VisTrails/issues/1102 #1102])
** allow manual delete to fix right now
** fix this on top of the use-uuid branch
* [TE] Release VisTrails 2.2.1? ([https://github.com/VisTrails/VisTrails/blob/v2.2/CHANGELOG CHANGELOG])
** [https://github.com/VisTrails/VisTrails/pull/1093 output-modules-use-global-dir]
** [https://github.com/VisTrails/VisTrails/milestones/version%202.2 Current issues for 2.2]

=== July 1, 2015 ===
'''Updates'''
* [TE] PROV fixed
* [TE] Working on subworkflow issues
* [RR] Considering reworking the controller (log vs exception problem, retained upgrades causing interferences) and also the interpreter (IPython?)

'''Items to Discuss'''

=== June 24, 2015 ===
'''Updates'''

'''Items to Discuss'''
* UV-CDAT
* [TE] Can a cyclic workflow be valid? ([https://github.com/VisTrails/VisTrails/issues/1097 #1097])
** focus on disabling the ability to create cyclic pipelines because more things break than just this with a cyclic pipeline
* [RR] Relative paths ([https://github.com/VisTrails/VisTrails/pull/1057 #1057])
** This interacts with the new bundle; how do handle packing files inside the VT bundle?

=== June 17, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] current_version and reusing existing upgrades are broken ([https://github.com/VisTrails/VisTrails/issues/1095 ticket #1095])
** Could be that export to PROV is using an unflushed upgrade pipeline?
** current_version would then be correct.
** It may work to flush the actions before exporting?

=== June 10, 2015 ===
'''Updates'''
* DAT: fixed VTK issue on Linux and Mac
* Still crashes on Windows. Need help! Reminder: this works in the VisTrails spreadsheet (QCellPresenter), although no widget get changed there during a drag
** Is it a VTK bug?
** Is it simply impossible to change widgets during the drag, should we do it a different way?
** Did I miss something that is done in VisTrails but somehow not in DAT?
** Low prio, UV-CDAT doesn't run on Windows anyway

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 Updated pull request])
* Single instance code and batch mode

=== June 3, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] Executable Paper ([https://github.com/VisTrails/VisTrails/issues/1086 ticket #1088] [https://github.com/VisTrails/VisTrails/pull/1088 pr])
** Requires fixes to command line parameters, Output modules, and batch mode
** How to test this
** Updated missing/outdated flags
** Fixed view issues when generating graphs
* [TE] batch mode
** SpreadsheetOutput not enabled in batch mode. Should we check is_running_gui instead?
** Other instance setting flags from caller
** Is graphsAsPdf replacing spreadsheetDumpPdf?
** graphsAsPdf true by Default?
** Batch mode executing by default (Not needed when generating graphs)
** Re-added workflowInfo as withWorkflowInfo for writing graph and xml workflow
** [DK] batch mode should be outputting to files or stdout, shouldn't always trigger SpreadsheetMode
** execute flag, maybe make execution the default and allow a "--no-execute" if you only want to capture graphs, for example

=== May 27, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [vistrails-users] API question
** http://lists.vistrails.org/pipermail/vistrails-users/2015-May/000357.html
* Status of DAT
** Can add VCS plot to DAT but need to work on configuration windows
** Documentation for graphics templates for UV-CDAT/vcs?
* Qt support?

=== May 20, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Reviving the DAT, integrating scripting & porting UV-CDAT!
** On [https://github.com/VisTrails/DAT GitHub] ([https://github.com/VisTrails/DAT/issues issues])
** Merging 2 years of development taking longer than expected, but getting there. The plan is to get the patches in VisTrails and never fork again, we never want to get in UV-CDAT's situation (and don't need to).
** VTK cell works fine on Linux but there was flickering on Mac & Windows before; still issues on Mac (Windows status unknown)
** Can get a VCS plot soon (but will need VTK cell fix)
** Integrate in UV-CDAT's build system (so we have cdms, VCS, ...) -> RR can do this, low priority
** How do we integrate scripting?
*** We want to be able to seamlessly make changes to a plot by changing Python code
*** Define new plots by entering Python code without writing modules/packages?
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 13, 2015 ===
'''Updates'''
* [RR] Test skipping whitelist ([https://github.com/VisTrails/VisTrails/pull/1069 #1069]) -- low priority
* [RR] Custom matplotlib modules can't be compatible with both 2.1 and 2.2 ([https://github.com/VisTrails/VisTrails/issues/1067 #1067]); should be fixed for ALPS ([https://github.com/VisTrails/VisTrails/issues/1070 #1070])

'''Items to Discuss'''
* [RR] UV-CDAT [https://github.com/UV-CDAT/uvcdat/issues/1275 needs] [https://github.com/VisTrails/VisTrails/pull/1073 #1073], please take a look
* [RR] Subworkflow issues
** [https://github.com/VisTrails/VisTrails/issues/1065 #1065]: missing attribute (fixed)
** [https://github.com/VisTrails/VisTrails/issues/1066 #1066]: groups in subworkflows were ignored when finding dependencies (fixed)
** [https://github.com/VisTrails/VisTrails/issues/725 #725]: "upgrade subworkflow" button not popping up (fixed); also, namespace issue
** [https://github.com/VisTrails/VisTrails/issues/1071 #1071]: subworkflows don't go through upgrades
* [RR] [https://github.com/VisTrails/VisTrails/issues/1074 #1074]: can't load and edit a single pipeline if upgrade happen

=== May 7, 2015 ===
'''Updates'''
* [RR] Export/import workflow to Python working!

'''Items to Discuss'''
* [Claudio] UV-CDAT
** The UV-CDAT project is the biggest user base of VisTrails
** VisTrails package management provides a lot of friction towards people plugging in their code
** Need to make it easy to integrate your random Python scripts in the system without having to deal with all the boilerplate, at least in the first step
** [RR] argues that modules are still good; UV-CDAT shouldn't move towards a purely script-based backend
** [RR] export/import with Python could reduce a lot of that friction by allowing 1) to edit workflow as Python 2) to open up boxes automatically if needed code doesn't match actual modules
** ...

=== April 29, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] <strike>Abstractions</strike> subworkflows status ([https://github.com/VisTrails/VisTrails/labels/subworkflows tickets])
* [RR] matplotlib compatibility (2.1 & 2.2), [https://github.com/VisTrails/VisTrails/issues/1067 #1067]
** RR to try and fix ALPS matplotlib modules

=== April 22, 2015 ===
'''Updates'''
* 2.2.0 has been released!
* Windows issue (via email from Ryan)
** issue with manifest file (may be a new file in VTK6?)
** Tommy has regenerated new Windows builds
* Binaries, pypi, and conda released
* [RR] Export as script
* Python sources using VTK need to switch to SetInputData (users should be aware of this)

=== April 15, 2015 ===
'''Updates'''
* Ready for 2.2.0 (apart from binary/deps issues)
** Missing some libs (scikit-learn, tej, tdparser, SQLAlchemy+connectors
** Windows: runvistrails.py is no longer used, so the PATH is wrong
** Windows: pip is broken, but it probably wouldn't work anyway because of permission issues (disable this?)
* Queries, upgrades and getPipeline() usage ([https://github.com/VisTrails/VisTrails/issues/1054 #1054])
** Getting a pipeline with getPipeline() is not safe: it might return an invalid pipeline
** This is used in many places throughout the code, like queries
** Upgrading would require going through the controller, but that creates new actions
* [TC] Avoid copying a module's output if it's used as input by exactly one downstream module ([https://github.com/VisTrails/VisTrails/issues/1060 #1060]) (useful for big numpy arrays you can update in-place)

=== April 8, 2015 ===
'''Updates'''
* [DK] Merged RR's changes for output modules (1012 and 1013)
** RR will merge remaining changes, then create v2.2 branch!

'''Items to Discuss'''
* BNL need numpy array to VTK image
** Looks like VTK has some helpers for this
** We will help if issues arise
** Will contribute back to VisTrails package
* Upgrade issue: [https://github.com/VisTrails/VisTrails/issues/1017 #1017]
** Automatic upgrades should happen between versions of provided upgrades
** Our existing upgrades work around this so it doesn't need to be 2.2.0
* Corner-case VTK modules
** No longer need VTKCell input port, so don't interfere with registry and API anymore
** Still work weirdly, people probably shouldn't use them
** But we have lots of clunky modules since we wrap the whole of VTK; some people might rely on this and know how to use them, let's keep them anyway
** Ready for 2.2.0

=== April 1, 2015 ===
'''Updates'''
* [RR] UV-CDAT: bugfixing for 2.2, long-term plans: implement scripting import/export in VisTrails, port to UV-CDAT
* Possibly, try to move to regular VisTrails to use new features

'''Items to Discuss'''
* 2.2 release: nothing much is pending anymore, release next week?
** [TE] vtkExporter classes [https://github.com/VisTrails/VisTrails/issues/1032 #1032]
** [RR] Hiding upgrades in version tree might make it (or might be 2.2.1 so we can test it out) [https://github.com/VisTrails/VisTrails/issues/949 #949]
** Output modules changes to go in
* add note to documentation about order of parameters in VTK
* add issue about exporter upgrades if not already there

=== March 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* 2.2 release
** Checklist on Github: https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist
** Review output modules
** RR has a couple more issues to fix
** Ready to go -- sign app package for OSX? [https://github.com/VisTrails/VisTrails/issues/984 #984] We need access to the Apple Membership team

=== March 18, 2015 ===
'''Updates'''
* [TE] VTK6 works

'''Items to Discuss'''
* [RR] Release v2.1.5 with backported tabledata?
** MTA example needs updated tabledata (for JoinTables)
** Google Maps package still not available
* [RR] Work torward v2.2.0?
** changes:
*** new persistence
*** API changes
*** output module changes (upgrades?), maintain cells but try to upgrade
*** not wrapping stuff
*** VTK6? yes
*** JobSubmission stuff?
*** relabeling for upgrades [https://github.com/VisTrails/VisTrails/issues/949 #949]
** makes sense, needs the tree view code to be updated, check selection
** See [https://github.com/VisTrails/VisTrails/wiki/2.2-Release-Checklist 2.2 checklist]
* Discussion of [https://github.com/VisTrails/VisTrails/issues/1016 #1016]
** plumbing between outputs and output modes, how to define a mode that works for many outputs without writing for each output?

=== March 11, 2015 ===
'''Updates'''
* [RR] persistent_archive done; merge? ([https://github.com/VisTrails/VisTrails/pull/755 #755])
** note about the focus events for widgets
** TE be aware of file_archive for future binaries that include persistent_archive
* [TE] [https://github.com/VisTrails/VisTrails/pull/998 New VTK package] finished

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails? (see last week; decision needed)
** RR email to JF about this
** yes; email sent to Github
* [RR] Switching order of output ports ([https://github.com/VisTrails/VisTrails/pull/1006 #1006])
** added port specs are sorted at a separate spot (Module.*_port_specs properties) than those in the registry (which are sorted in the registry), but those two lists are just combined without respect to sort keys
** need to determine whether the two lists should be merged or remain distinct
** should make sure that order of input ports and output ports makes parallel connections for things with same order
** DK suggests breaking backward compatibility here: workflows still run, can fix easily if a problem in an existing package.
* [RR] Question about output modes ([https://github.com/VisTrails/VisTrails/pull/1007 #1007]), how to integrate in API ([https://github.com/VisTrails/VisTrails/pull/24 #24])
** Should ImageFileMode be removed? ("image" is not a mode, "file" is)
** ImageOutput missing?
** Feel free to change how formats works
* [TE] Test suite segfaults on Fedora 17 virtualbox. Install newer version? (Support ended in 2013)

=== March 4, 2015 ===
'''Updates'''
* [TE] VTK wrapper
** Works on VTK 5.10
** Still need to test VTK 6
** New general wrappers for python functions and classes

'''Items to Discuss'''
* [RR] Unmark UV-CDAT/VisTrails as a fork of VisTrails/VisTrails?
** When [http://i.imgur.com/UTY2qfg.png filing a pull request] from UV-CDAT/VisTrails, VisTrails/VisTrails is selected by default
** People keep forgetting to change the default ([https://github.com/VisTrails/VisTrails/pull/956 #956] [https://github.com/VisTrails/VisTrails/pull/968 #968] [https://github.com/VisTrails/VisTrails/pull/999 #999] [https://github.com/VisTrails/VisTrails/pull/1000 #1000] [https://github.com/VisTrails/VisTrails/pull/1003 #1003] [https://github.com/VisTrails/VisTrails/pull/1004 #1004] [https://github.com/VisTrails/VisTrails/pull/1005 #1005])
** Only way to change that is to not have it marked as a fork of VisTrails/VisTrails
** Github staff [https://gist.github.com/remram44/b364c24ef1e462ce6e2f can make that change for us]; should we do it?
** Juliana: comments on this? visibility vs. convenience/annoyance for developers
* [RR] What about [https://github.com/VisTrails/VisTrails/issues/991 #991]?

=== February 25, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [TE] vtkviewcell for infovis support, can we unify with VTKCell?
** need to test this
* [TE] vtk wrapping
** Mostly finished
** VTK 5.10 produce incorrect results with old wrapping
*** Old wrapper is based mostly on VTK 4
*** Most vtk_examples affected
*** [http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Replacement_of_SetInput]
*** should be able to upgrade from SetInput to SetInputData (need to drop GetOutput and replace with self ports)
*** can we change vtkInstance to just return self and not wrap things
** terminator example not working under 5.8?
* How does VTK wrapping fit into general wrapping framework?
* [RR] new persistence package

=== February 18, 2015 ===
'''Updates'''
* [RR] New VisTrails API and IPython integration ([https://github.com/VisTrails/VisTrails/pull/24 #24])

'''Items to Discuss'''
* [TE] VTK wrapping
** [https://gist.github.com/rexissimus/16b74693545b5e7c1035 Benchmarking vtk package]
*** Old: 24.7 seconds
*** New: 10.5 seconds (Except first time that adds 8 sec)
**** The parsing that calls is_abstract (that tries to instanciate all vtk classes) is now only run the first time.
**** get_items_from_sigstring takes 2 seconds, maybe we can use a lookup dict for already computed sigstrings?
** Now using a general python function wrapper
*** VTK classes are wrapped into python function that does not depend on vistrails
*** VTK functions can be executed without vistrails
*** The spec maps functions into vistrails modules, but can also describe wrapping
*** A general python function wrapper that supports
**** kwarg inputs
**** single, list, dict outputs
**** callback for progress reporting
**** temporary file generator for using FilePool
**** optional output generation
*** Creating specs:
***** Create spec by hand
***** Auto-create spec outline (TODO) and manually finish it
***** Dynamically create spec (VTK)
***** Implement documentation wrappers (Can use scikitlearn wrapper to wrap numpydoc) (TODO)
***** Classes as bad functions needs to be wrapped in new functions before they are wrapped. This is different for each package.
****** Classes is hard: Like VTK, and matplotlib. Scikit-learn does still not wrap classes
***** Spec diffing and patching could be done using code from matplotlib.
** Still needs upgrades from old VTK package
*** Is it possible to dynamically wrap functions, e.g, you see a SetFunc and just remove the 'Set' prefix. Or do you need to create a complete mapping?

=== February 11, 2015 ===
'''Updates'''
* Update from Friday's meeting
** discussed VisTrails internals
** discussed wrapping
*** xml discussion, hard to modify because tied to db code
*** TE has made it possible to add the schema-defined attributes to the intermediate representation
*** higher-level operations on the port specs
** make sure the simple case works
*** [JF] take a simple package with documentation and figure out what the base case for wrapping is

'''Items to Discuss'''
* [TE] VTK wrapping
** Dynamic loading works
** Reading XML is fast enough, but [https://gist.github.com/rexissimus/8272d3c776ccfa115d82 unserializing data is slow]
** Working on patterns for patching
** Matplotlib has many advanced patterns like argument ordering, nested arguments, alternateSpecs, output types.
*** Having all this in a general wrapper might confuse users?
** [RR] Delay module (except for identifiers) until you need it---e.g. don't deal with port specs, etc. until necessary
* Scripting Support [https://github.com/VisTrails/VisTrails/pull/950 #950]
** [RR] Issue with getting code from modules
** Design a simple solution
** [JF] Couldn't you use modules as black boxes without conversion, just to call into modules/subworkflows easily from e.g. IPython?
*** [RR] This is a job for the API, and a very separate use case. See [https://github.com/VisTrails/VisTrails/pull/24 #24]

=== February 4, 2015 ===
'''Updates'''

'''Items to Discuss'''
* Wrapping
** Format to use? Currently XML (like current matplotlib)
*** JSON and YAML have simple "to python dictionary" methods
*** But don't stream
*** YAML a lot easier for humans
** [DK] vtk-new-package also changes parameter names, creates enumerations
*** intermediate schema needs to be extensible
*** packages will want to store there specific infos for compute() method generation
*** also might have specs-altering info, like matplotlib's alternateSpec
** representation to code , registry already has schema for some aspects
** [RR] We might want to see if Module subclasses can be created lazily
*** no need to create all the classes just to register them in the registry and never actually use most of them
*** future effort
* [RR] Where should VisTrails packages live?
** tej installs as 'vistrailspkg.tej', TE installed it as 'userpackages.tej'
** Currently, standard packages are 'vistrails.packages.', user packages are 'userpackages.' and packages loaded through pkg_resources might be anything
** [RR] Use 'vistrailspkg.' everywhere?
** Long-term effort to simplify package distribution/installation (and have VisTrails get them automatically?)

=== January 28, 2015 ===
'''Updates'''
* T. Caswell to come visit on Fri 6 to discuss wrapping work

'''Items to Discuss'''
* [TE] New VTK wrapping
** Current code by DK seems a good deal faster
** Generates XML that can be patched/tweaked, generates Python code from it, VisTrails only loads generated Python code
** RR would rather have VisTrails load intermediate representation (= XML) directly, wants to make sure this is not slower
** The goal is to turn the intermediate step into something generic that would be used for every wrapped package (vtk, numpy, matplotlib, sklearn, java) instead of each having its own
** TC has its own code at [https://github.com/Nikea/VTTools/blob/master/vttools/wrap_lib.py github:VTTools] which parses numpy docstrings and generates modules, doesn't yet handle classes or persist anything
* Web crawler
** Right now, TE starts jobs for "start crawler", "stop crawler", "install classifier"
** RR would rather have the crawling be a job as far as VisTrails and tej are concerned
** The whole thing would be one pipeline: load examples, train classifier, start crawler [check for job, kill previous one, upload model, start processes], get snapshot, visualize
*** Need some support in tej and job submission system: long-running jobs, stop a job (wait for it to finish?), restart a job even though results are cached

=== January 21, 2015 ===
'''Updates'''

'''Items to Discuss'''
* [RR] Unified wrapping method discussion [https://github.com/VisTrails/VisTrails/issues/991 #991]
** TE to work on reusable method with intermediate representation, starting with VTK
* [RR] Examples for scikit-learn: JF has an old example using Weka with parameter exploration (not currently in source tree)
** AM's examples are enough
* [AM] scikit-learn package is done, merge it in? [https://github.com/VisTrails/VisTrails/pull/955#issuecomment-70286788 #955]
** RR will merge
* [RR] What should copyright headers say? [https://github.com/VisTrails/VisTrails/pull/994#issuecomment-70173935 #994]
** Let's keep everything in there: Utah/Poly/NYU

=== January 14, 2015 ===
'''Updates'''
* [TE] Working on classifier
* [RR] Scripting integration, work in progress

'''Items to Discuss'''
* [RR] Unified wrapping method discussion ([https://github.com/VisTrails/VisTrails/issues/991 #991])
** Let's talk next week, [AM] and [DK] are not here

=== January 7, 2015 ===
'''Updates'''

'''Items to Discuss'''
* make sure that we address critical issues, questions, and pending review branches in a timely manner
* scripting support
** [RR] no issues if we want to just keep annotations in the generated code to allow the link back to a workflow
** [RR] can translate from workflow to script, working on script to workflow
** will work for parameter value changes, structural changes require changes to the annotations
** need to publish best practices here
** would be cool to do looping in scripts (easier interface than with workflows)
* notebook support (convert form notebook to workflow)
** RR will sync with FC on this
* Issue with console in built-from-scratch
** [TC] iPython rearranged some of the completion stuff in 2.2 and 2.3
** binary has old version of iPython -> 1.0.0, should we update?
* [TC] automated wrapping of numpy and scipy
** discovered a bunch of malformed documentation in numpy and scipy
** has github repo for vistrails tools
** example modules wrap a bunch of R stuff (not baked in, just how things are)
** will be pushing wrapping logic up
** port names forbidden (window and domain)
** have an import hook to get from yaml directly to VisTrails Modules
** should work for any python modules with well-formed numpy docstrings.
* [Action] should make it clear in documentation that Constant now means serializable not that the value doesn't change (e.g. List)
* [TC] might be interesting to try to build components of matplotlib and accumulate in figure (long-term project, but thinking about how this might work)
* [TE] build and build scripts
** completely automatic, buildbot
** need to set the build machines for the environment we want for the binary
** would virtualenv work here?
** [TC] anaconda can pin versions, potential path to test different configurations
** Q: upload nightly binary builds? A: makes sense, make sure they are well-labeled
* sourceforge stats: e.g. http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07
* package issues (see Remi's message)
* [TE] Scope of tej
** Support single ssh commands?
** Queue can be used as a remote machine (crawler is using queue.call*)
* SourceForge stats: http://sourceforge.net/projects/vistrails/files/vistrails/nightly/vistrails-src-nightly.tar.gz/stats/timeline?dates=2014-01-01+to+2015-01-07

== Older meetings ==
* [[Development/2014]]
* [[Development/2013]]
* [[Development/2012]]
* [[Development/2011]]
* [[Development/2010]]