IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an email to s dot adaszewski at gmail dot com. User accounts are meant only to report issues and/or generate pull requests. This is a purpose-specific Git hosting for ADARED projects. Thank you for your understanding!
Browse Source

Missing 'the'.

pull/2/head
parent
commit
5cfdc38491
1 changed files with 1 additions and 1 deletions
  1. +1
    -1
      README.md

+ 1
- 1
README.md View File

@@ -7,7 +7,7 @@ Workbench Advanced can be used as either a replacement or an addition to the Wor
WBA wouldn't make much sense if it wasn't different from the existing tools in several key aspects. In no particular order those differentiating factors are:
- Speed: At every stage of the development, performance was in the center of my attention. A premium user experience calls for responsiveness, progress feedback whenever possible and moving computations outside of the main browser thread in order to never EVER block the GUI. WBA checks all these boxes and contains numerous other optimizations in the way it talks to the Arvados API server in order to make your experience as instantaneous as possible.
- Huge Collections Support: WBA effortlessly supports collections with millions of files and hundreds of terabytes of data. Thanks to the optimized manifest parser and paginated listing display, it doesn't suffer from performance problems you might have encountered in WB1 or WB2.
- Huge Collections Support: WBA effortlessly supports collections with millions of files and hundreds of terabytes of data. Thanks to the optimized manifest parser and paginated listing display, it doesn't suffer from the performance problems you might have encountered in WB1 or WB2.
- Volume Browser Support: WBA incorporates [Papaya](http://ric.uthscsa.edu/mango/papaya.html) volumetric data browser for Nifti files (and hopefully DICOM in the future).
- Support for arrays of files, directories or a mix of both in the Workflow configuration interface (browse dialog).
- Ability to automatically start processes in a sub-project where they are further organized by date (day of launch). This allows to avoid all the clutter that usually accumulates in the Home directory.


Loading…
Cancel
Save