Developer Meetings/20130212 - Revision history

Grundlett: convert email tags to template

2019-11-27T05:02:31Z

convert email tags to template

2019-11-27T04:59:42Z

Text replacement - "<email>(.*?)@(.*?)<\/email>" to "$1{{@}}$2"

2013-02-18T23:06:49Z

2013-02-18T22:16:07Z

Conclusion

2013-02-18T21:58:17Z

Conclusion

2013-02-18T21:57:09Z

Conclusion

2013-02-18T21:52:59Z

Conclusion

2013-02-18T21:45:49Z

Conclusion

2013-02-18T21:41:33Z

Conclusion

2013-02-18T21:39:03Z

Conclusion

@@ Line 80: / Line 80: @@
 On Slicer side, the integration of Twisted need to be reviewed.
-All of that said, if you believe this could benefit your projects. Make sure to drop a line to Jim (millerjv@ge.com</email>) and myself (<email>jchris.fillionr{{@}}kitware.com).
+All of that said, if you believe this could benefit your projects. Make sure to drop a line to Jim (millerjv{{@}}ge.com) and myself (jchris.fillionr{{@}}kitware.com).
 * JsonCpp Extension has been merged and is all green :-): http://slicer.cdash.org/index.php?project=Slicer4&filtercount=1&showfilters=1&field1=buildname/string&compare1=63&value1=Json

@@ Line 80: / Line 80: @@
 On Slicer side, the integration of Twisted need to be reviewed.
-All of that said, if you believe this could benefit your projects. Make sure to drop a line to Jim (<email>millerjv@ge.com</email>) and myself (<email>jchris.fillionr@kitware.com</email>).
+All of that said, if you believe this could benefit your projects. Make sure to drop a line to Jim (millerjv@ge.com</email>) and myself (<email>jchris.fillionr{{@}}kitware.com).
 * JsonCpp Extension has been merged and is all green :-): http://slicer.cdash.org/index.php?project=Slicer4&filtercount=1&showfilters=1&field1=buildname/string&compare1=63&value1=Json

← Older revision		Revision as of 23:06, 18 February 2013
Line 81:		Line 81:

	All of that said, if you believe this could benefit your projects. Make sure to drop a line to Jim (<email>millerjv@ge.com</email>) and myself (<email>jchris.fillionr@kitware.com</email>).		All of that said, if you believe this could benefit your projects. Make sure to drop a line to Jim (<email>millerjv@ge.com</email>) and myself (<email>jchris.fillionr@kitware.com</email>).
		+
		+	* JsonCpp Extension has been merged and is all green :-): http://slicer.cdash.org/index.php?project=Slicer4&filtercount=1&showfilters=1&field1=buildname/string&compare1=63&value1=Json

@@ Line 69: / Line 69: @@
 The API associated with the Slicer server would be:
   slicer.cli.list()
-  slicer.cli.list(name)
+  slicer.cli.describe(name)
-  slicer.cli.run(name)
+  slicer.cli.run(name, parameters)
 The "server" running in Slicer would be [http://twistedmatrix.com/trac/ Twisted], the event-driven networking engine written in Python and licensed under the open source MIT license.
-The prototype code of the corresponding midas module is currently available here:
+The prototype code of the corresponding midas module is currently available [https://github.com/midasplatform/pyslicer/tree/slicerweb here].
 On midas side, work is required to implement the "slicer.reserve / release()" method. Currently, as a first implementation it could return the "id" of a Slicer instance running along side the midas server. Moving forward, the idea would be to be able to either have existing Slicer instance registered as available or spawning virtual machine on the amazon cloud ...

@@ Line 62: / Line 62: @@
   slicer.cli.run(instance_id, name, parameters) # run cli
   slicer.release(instance_id)            # release a given instance
 Each Slicer instance would also run its own web server exposing also a simple API to "talk" with either a midas instance or any other client being on the same network. It could for example be an other Slicer instance.

@@ Line 61: / Line 61: @@
   slicer.cli.describe(instance_id, name) # describe the cli available on a given instance
   slicer.cli.run(instance_id, name, parameters) # run cli
-  slicer.reserve(instance_id)            # release a given instance
+  slicer.release(instance_id)            # release a given instance
 Each Slicer instance would also run it's own web server exposing also a simple API to "talk" with either a midas instance or any other client being on the same network. It could for example be an other Slicer instance.

@@ Line 44: / Line 44: @@
 ** This could also motivate a feature allowing to pass CMake option that would be listed in a extension description file.
-* Julien presented his work regarding the CLI AutoRun feature.
+* Julien presented his work regarding the CLI AutoRun feature. See http://www.na-mic.org/Bug/view.php?id=2940
 * Presented to Jim the work (prototype) did at Kitware regarding remote execution of modules:

← Older revision		Revision as of 21:39, 18 February 2013
Line 64:		Line 64:
	The "server" running in Slicer would be [http://twistedmatrix.com/trac/ Twisted], the event-driven networking engine written in Python and licensed under the open source MIT license.		The "server" running in Slicer would be [http://twistedmatrix.com/trac/ Twisted], the event-driven networking engine written in Python and licensed under the open source MIT license.

−	The prototype code is currently available here:	+	The prototype code of the corresponding midas module is currently available here:
		+
		+	On midas side, work is required to implement the "slicer.reserve / release()" method. Currently, as a first implementation it could return the "id" of a Slicer instance running along side the midas server. Moving forward, the idea would be to be able to either have existing Slicer instance registered as available or spawning virtual machine on the amazon cloud ...
		+
		+	On Slicer side, the integration of Twisted need to be reviewed.
		+
		+	All of that said, if you believe this could benefit your projects. Make sure to drop a line to Jim (<email>millerjv@ge.com</email>) and myself (<email>jchris.fillionr@kitware.com</email>).