Revision as of 00:55, 13 July 2016 edit Headbomb (talk \| contribs) Edit filter managers, Autopatrolled, Extended confirmed users, Page movers, File movers, New page reviewers, Pending changes reviewers, Rollbackers, Template editors 473,335 edits m →P-NCAS: clean up, use arxiv parameter, remove url redundant with arxiv using AWB ← Previous edit		Revision as of 17:06, 10 October 2016 edit undo John of Reading (talk \| contribs) Autopatrolled, Extended confirmed users, Pending changes reviewers 787,576 edits m →The Framework: Removed repeated words using AWB Next edit →
Line 50: PSE Park provides these through its repository of functions. the repository contains modules required to build PSEs. Some of the most basic modules, called Cores, are used as the foundation of PSEs. More complex modules are available for use by programmers. Users access PSE Park through a console linked to the programmers. Once the user is register, he/she has assess to the repository. A PIPE server is used as the mediator between the user and PSE Park. It grants access to modules and constructs the selected functions into a PSE.<ref name=":5" /> Developers ~~can developers~~ can develop functions, or even whole PSEs, for inclusion into the repository. Entry-level and expert users can access these pre-made PSEs for their own purposes. Given this architecture, PSE Park requires a cloud computing environment to support the enormous data sharing that occurs during PSe ~~use~~ use and development.<ref name=":5" /> === The PIPE Server ===

Problem solving environment: Difference between revisions