Dec. 12, 2012 ProActive V5.3.2 is out!
|
Studio 1.2
The goal of ProActive Matlab Connector is to equip Matlab with a generic interface to Grid and Cloud computing. It is composed of a Matlab toolbox. It allows the deployment of Matlab instances on several nodes of various infrastructures, and to use these instances like computing engines. The submission of Matlab tasks to be distributed over nodes is achieved seamlessly and directly from the usual Matlab interactive environments.
This package features :
-
Run functions on remote computers, Grids, and Clouds.
-
Do not block the local session while remote results are being produced.
-
Seamlessly retrieve results when you need them, just as if the functions were run locally.
-
Provide you with detailed remote log/output information, altogether with errors if any occurred.
-
Disconnected mode, where the local session doesn't need to remain open while the job is processing.
-
Automatic source transfer, data file transfer, transfer of local workspace, and other configurable options.
| Matlab Connector 1.1
The goal of ProActive Scilab Connector is to equip Scilab with a generic interface to Grid and Cloud computing. It is composed of a Scilab toolbox. It allows the deployment of Scilab instances on several nodes of various infrastructures, and to use these instances like computing engines. The submission of Scilab tasks to be distributed over nodes is achieved seamlessly and directly from the usual Scilab interactive environments.
This package features :
-
Run functions on remote computers, Grids, and Clouds.
-
Do not block the local session while remote results are being produced.
-
Seamlessly retrieve results when you need them, just as if the functions were run locally.
-
Provide you with detailed remote log/output information, altogether with errors if any occurred.
-
Disconnected mode, where the local session doesn't need to remain open while the job is processing.
-
Automatic source transfer, data file transfer, transfer of local workspace, and other configurable options.
| Scilab Connector 1.1
ProActive Java Active Objects (Programming) is an open source Java library aiming to simplify the programming of multithreaded, parallel, and distributedapplications for Clouds, Grids, multi-cores, clusters, and data-centers.
Java Active Objects features a concurrent and parallel programming model, offers distributed and asynchronous communications, mobility and a deployment framework. | Java Active Objects 5.3
The ProActive Scheduler allows easy distribution of all your applications (Native, Java, Scripts, Matlab, Scilab, GPU, etc.), together withDynamic Workflows. It provides automatic input and output file transfer, fault tolerance, resource selection and configuration through scripting (Javascript, Ruby, Python), multi-core and topology control.
| Scheduler 3.3
The Scheduling and Resource Management Rest APIs provide a language-independent access to the Scheduler.
Use this interface to seamlessly integrate orchestration and scheduling in you own portal.
Main Features:
| Rest API 1.3
The Scheduler Web portal provides a platform-independent access to the Scheduler.
Main Features:
-
Full visualization of Job and Task details
-
Full access to output and logs in streaming mode
-
GUI and Activation for Data Servers (File Transfer)
-
Remote Visualization of Graphical Tasks
-
Graphical monitoring of Workflow execution directly from the portal.
| Scheduler Web Portal 1.3
The Cloud & Grid IaaS Web portal provides a platform-independent access to the Resource Manager.
Main Features:
- Full visualization of resources, physical and virtual machines
- Full control on resources, deploy or remove resources on desktop PCs, clusters, clouds...
- Graphical monitoring of resource usage
| Cloud & Grid IaaS Web Portal 1.3
The ProActive Cloud & Grid IaaS Server is the software for coupling distributed resources in order to solve large-scale problems. The distributed resources are represented by Java virtual machines launched on desktop computers, clusters or clouds.
The Cloud & Grid IaaS Server provides a single point of access to all resources enabling an effective way of selecting them for computations with different criteria.
| Resource Manager 3.3
The ProActive Linux Agent allows to automatically start and monitor resources on Linux machines.
Main Features:
-
Automatic start, stop according to a weekly schedule.
-
Automatic monitoring and restart of forked processes.
-
Limit available system resources (cpu, I/O, memory).
-
Integrated with ProActive Cloud & Grid IaaS.
-
Same XML configuration file than the ProActive Windows Agent.
-
Can be started as a system daemon or as a regular executable without any special permissions.
| Linux Agent 1.0
ProActive Windows Agent is a Windows Service: a long-running executable designed not to require user intervention. The agent is able to create a ProActive computational resource on the local machine. This resource will be provided to ProActive applications (such as the Cloud & Grid IaaS Server) according to the user defined planning.
Main features:
-
User defined weekly planning.
-
Local Registration of a ProActive node.
-
Cloud & Grid IaaS Server registration of a ProActive node.
-
Automatic restart of the spawned java process in case of failures.
-
RAM limitation of the spawned processes.
-
CPU limitation (throttling) of the spawned processes.
| Windows Agent 2.4
|
|
July 2011 : Matlab Connector 3.1
The goal of ProActive Matlab Connector is to equip Matlab with a generic interface to Grid and Cloud computing. It is composed of a Matlab toolbox. It allows the deployment of Matlab instances on several nodes of various infrastructures, and to use these instances like computing engines. The submission of Matlab tasks to be distributed over nodes is achieved seamlessly and directly from the usual Matlab interactive environments.
This package features :
-
Run functions on remote computers, Grids, and Clouds.
-
Do not block the local session while remote results are being produced.
-
Seamlessly retrieve results when you need them, just as if the functions were run locally.
-
Provide you with detailed remote log/output information, altogether with errors if any occurred.
-
Disconnected mode, where the local session doesn't need to remain open while the job is processing.
-
Automatic source transfer, data file transfer, transfer of local workspace, and other configurable options.
Main New Features
-
Simpler Matlab engines deployment and configuration.
-
Capability to execute Matlab or Scilab engines under original User Id (RunAsMe).
-
Interface with the new ProActive License Saver for automatic license token management.
-
Scilab extension now works asynchronously and provides similar features as Matlab extension.
|
| Maintenance Release Notes: | (click to expand note) | Download ProActive Parallel Suite: |  |
28 July 2011 : Matlab Connector 3.1.0
Bug
- [SCHEDULING-358] - Matlab's engOpenSingleUse or engOpen calls hang when available Matlab licence cannot be found
- [SCHEDULING-414] - ProActive Scilab extension requires Scilab bin directory to be put in the system path (Windows)
- [SCHEDULING-415] - Scilab extension can't handle dual Scilab/Matlab installation on the same host (Windows)
- [SCHEDULING-579] - Matlab extension on Windows faces random crashes of the Matlab engine
- [SCHEDULING-735] - In Scilab integration PAsolve('func',list_args) may return incorrect result
- [SCHEDULING-736] - Scilab integration doesn't work with Scilab 5.2
- [SCHEDULING-926] - Ptolemy interface truncates matlab's double results
- [SCHEDULING-1025] - Matlab Extension on Windows 64 bits requires a patch
- [SCHEDULING-1108] - Improve Starting stability of Matlab Engine on Windows
- [SCHEDULING-1296] - BadFileDescriptor Exception occurs sometimes when closing IOThreads
- [SCHEDULING-1300] - Typo in TestPATask (test fails because of that)
- [SCHEDULING-1305] - Error when displaying PATasks(Scilab)
- [SCHEDULING-1308] - If matlab client uses RunAsMe option the matlab task must define a forkEnvScript that transmits a valid java.io.tmpdir property to the forked jvm
- [SCHEDULING-1309] - If matlab client uses RunAsMe option the matlab worker jvm can crash if the client user has never started any matlab session on the worker host
- [SCHEDULING-1319] - Fix Multiple Submits in Scilab extension
- [SCHEDULING-1328] - In KeepEngine mode (scilab), errors in remote scilab code are not reported
- [SCHEDULING-1329] - Log files must be in "append mode"
- [SCHEDULING-1331] - Typo in PAResult_PAwaitFor.sci Java exceptions not printed
- [SCHEDULING-1333] - Set PA_scheduler_dir in loader.sce
- [SCHEDULING-1338] - StreamCorruptedException when using Fork or RunAsMe in Matlab and Scilab extensions (with Nodes deployed in rmi)
Improvement
- [SCHEDULING-1145] - Add compilation information for ptolemy on Scheduling manual
- [SCHEDULING-1293] - Make Scilab extension run in asynchronous mode
- [SCHEDULING-1310] - The selection script "MatlabReservationScript" should not be added to the matlab task if no "LicenseServerURL" is defined
- [SCHEDULING-1311] - It seems that the file_matlab_finder.rb selection script doesn't close the opened FileOutputStream to the file CheckMatlabXXXXXXX.log
- [SCHEDULING-1324] - Avoid reloading PAoptions.ini file each time PAoption function is called
- [SCHEDULING-1330] - Scilab Extension must support RunAsMe
- [SCHEDULING-1332] - The MATLAB task with RunAsMe requires a js prescript
Task
|
14 November 2011 : Matlab Connector 3.1.1
Bug
- [SCHEDULING-1380] - Fix PAsolve(task1,task2, ... taskn) syntax in Scilab toolbox
- [SCHEDULING-1392] - PAResult_DB is not initialized properly (Scilab)
- [SCHEDULING-1393] - Use of predef can cause unexpected behaviour of Scilab
- [SCHEDULING-1394] - Sources files are not updated when using the "Sources" PATask attribute (Scilab)
- [SCHEDULING-1397] - add lines(0) command in generated scilab script (Scilab Executable) to prevent pagination
- [SCHEDULING-1399] - Typo in PAsolve when using custom Selection Script(Scilab)
- [SCHEDULING-1400] - MatLab should register listener with "myEventsOnly" by default.
- [SCHEDULING-1422] - successive logs of PATask should be appended
Improvement
- [SCHEDULING-1379] - Handle Scheduler disconnection in Matlab/Scilab toolboxes
- [SCHEDULING-1381] - Improve PATask display in Matlab and Scilab extensions
- [SCHEDULING-1382] - Overload matrix concatenation for PATask in Matlab and Scilab toolboxes
- [SCHEDULING-1388] - Harmonize Matlab and Scilab's PATask syntax
- [SCHEDULING-1398] - add PAdisconnect and PAisConnected functions (Matlab & Scilab)
- [SCHEDULING-1419] - add the PAconnect(url, credpath) syntax (Matlab & Scilab)
- [SCHEDULING-1420] - Add val, logs, iserror and jobid attribute to PAResult objects (Scilab)
- [SCHEDULING-1421] - Improve memory handling in Scilab toolbox
- [SCHEDULING-1427] - return result index in PAwaitAny(Matlab)
- [SCHEDULING-1428] - add PAarrayfun function (Matlab)
- [SCHEDULING-1429] - add TestTransferEnv test (Matlab)
- [SCHEDULING-1430] - Improve PAsolve and PAwaitFor calls speed
- [SCHEDULING-1436] - Add jobRemove calls to Matlab&Scilab jobs once results have been retrieved by the user
- [SCHEDULING-1443] - Matlab and Scilab selection scripts should be static
- [SCHEDULING-1445] - Rearrange PAsolve and remove "jremove" for loaded classes due to a JIMS class loading change (Scilab)
New Feature
Task
|
18 January 2012 : Matlab Connector 3.1.2
|
|