You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by "Leo Simons (JIRA)" <ge...@gump.apache.org> on 2005/03/27 23:37:16 UTC
[jira] Created: (GUMP-100) gump.plugins.ModelDumper component for persisting the model on disk
gump.plugins.ModelDumper component for persisting the model on disk
-------------------------------------------------------------------
Key: GUMP-100
URL: http://issues.apache.org/jira/browse/GUMP-100
Project: Gump
Type: New Feature
Components: Python-based Gump
Versions: Gump3-alpha
Reporter: Leo Simons
Fix For: Gump3-beta
A plugin should be written that runs after all others that modify the model at all. This plugin would visit_workspace and create a huge pickle dump (probably) of the entire processed model and write that out to disk. So far, we've found it very difficult to store exactly what we need in a database. By keeping pickle dump files around, we are "sure" to be able to write tools later to retroactively perform intelligent work on the data gump has generated.
Might be as simple as (code sketch):
def visit_workspace(w):
import pickle
date = w.startdate
filename = "pickledump_%s" % date
file = open(filename, 'w')
pickle.pickle(w,file)
but I have no idea what the API for all this stuff is.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
[jira] Closed: (GUMP-100) gump.plugins.ModelDumper component for persisting the model on disk
Posted by "Leo Simons (JIRA)" <ge...@gump.apache.org>.
[ http://issues.apache.org/jira/browse/GUMP-100?page=all ]
Leo Simons closed GUMP-100:
---------------------------
Resolution: Duplicate
Assign To: Leo Simons
> gump.plugins.ModelDumper component for persisting the model on disk
> -------------------------------------------------------------------
>
> Key: GUMP-100
> URL: http://issues.apache.org/jira/browse/GUMP-100
> Project: Gump
> Type: New Feature
> Components: Python-based Gump
> Versions: Gump3-alpha-4
> Reporter: Leo Simons
> Assignee: Leo Simons
> Fix For: Gump3-alpha-5
>
> A plugin should be written that runs after all others that modify the model at all. This plugin would visit_workspace and create a huge pickle dump (probably) of the entire processed model and write that out to disk. So far, we've found it very difficult to store exactly what we need in a database. By keeping pickle dump files around, we are "sure" to be able to write tools later to retroactively perform intelligent work on the data gump has generated.
> Might be as simple as (code sketch):
> def visit_workspace(w):
> import pickle
> date = w.startdate
> filename = "pickledump_%s" % date
> file = open(filename, 'w')
> pickle.pickle(w,file)
> but I have no idea what the API for all this stuff is.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org