--
Has recibido este mensaje porque estás suscrito al grupo "bio4j-user" de Grupos de Google.
Para anular la suscripción a este grupo y dejar de recibir sus correos electrónicos, envía un correo electrónico a bio4j-user+...@googlegroups.com.
Para obtener más opciones, visita https://groups.google.com/groups/opt_out.
Hi,
About the examples: we are in the middle of a pretty big refactoring including how we make releases, code structure, repositories, etc. It’s been a bit inconvenient for new people (sorry about it) but we think that it’s better to change things now before any actual GSoC work will take place than later. Anyway, you can keep track of how things are going here
We expect that all this will be fixed during next week. So, I think it’d be better to wait before all that if you want to test things etc. You can of course see what’s going on and help with tasks that don’t require a lot of knowledge (like reafctorings and the like)
Re 3) data import only happens once, and client tools don’t need to care about that. Simplifying a bit, the plugin should just create an EC2 instance through Bio4j-specific (already developed) libs who would do all the work of retrieving already imported data (DB binaries) from S3, configuring the DB etc.
About 4) it will depend on the scope and features; the current situation is that in the neo4j version we had the need to significantly alter the model due to serious performance problems with a more natural approach, something which we don’t have the need to do in the (still in-progress) Titan implementation. If the set of queries/data access patterns is going to be determined beforehand in some way, then I’d rather use the abstract model directly which would yield good performance in all cases; if not, the default Blueprints impl could be OK. Another option would be to code everything in Blueprints but for the client to access the raw data model of each particular implementation; this would have other downsides in terms of queries working for one technology but not for the other etc.
best
--
Has recibido este mensaje porque estás suscrito a un tema del grupo "bio4j-user" de Grupos de Google.
Para anular la suscripción a este tema, visita https://groups.google.com/d/topic/bio4j-user/t705kBB-tI0/unsubscribe. Para anular la suscripción a este grupo y todos sus temas, envía un correo electrónico a bio4j-user+...@googlegroups.com.
Hi,
I'm grateful if you can help me with the following questions inline.
By the way, please keep me posted on your refactoring work. I'm still
in trouble of not finding the new documents and the new examples.
On Sat, Mar 1, 2014 at 9:56 PM, Eduardo Pareja-Tobes
<eparej...@ohnosequences.com> wrote:
>
> Hi,
>
> About the examples: we are in the middle of a pretty big refactoring including how we make releases, code structure, repositories, etc. It's been a bit inconvenient for new people (sorry about it) but we think that it's better to change things now before any actual GSoC work will take place than later. Anyway, you can keep track of how things are going here
>
> https://github.com/bio4j/bio4j/issues/15
>
> We expect that all this will be fixed during next week. So, I think it'd be better to wait before all that if you want to test things etc. You can of course see what's going on and help with tasks that don't require a lot of knowledge (like reafctorings and the like)
>
> Re 3) data import only happens once, and client tools don't need to care about that. Simplifying a bit, the plugin should just create an EC2 instance through Bio4j-specific (already developed) libs who would do all the work of retrieving already imported data (DB binaries) from S3, configuring the DB etc.
Is the Bio4j-specific instance supposed to be created using the
template [1] following the instructions [2]? The instructions [2] show
how to make it in the AWS console. But how to do that through Java
coding in the Cytoscape plugin? Creating the EC2 instance would take
several minutes? So the user of the plugin is require to wait for that
long time before querying? Every time using bio4j EC2 instance would
be charged for a user? I'm afraid long-time-waiting and not-free-using
would hamper the wide adoption of the plugin.
[1] https://s3-eu-west-1.amazonaws.com/bio4j-public/Bio4jBasicInstanceTemplate.txt
[2] http://blog.bio4j.com/2011/12/bio4j-aws-cloudformation-your-own-fresh-baked-db-in-less-than-a-minute/
>
> About 4) it will depend on the scope and features; the current situation is that in the neo4j version we had the need to significantly alter the model due to serious performance problems with a more natural approach, something which we don't have the need to do in the (still in-progress) Titan implementation. If the set of queries/data access patterns is going to be determined beforehand in some way, then I'd rather use the abstract model directly which would yield good performance in all cases; if not, the default Blueprints impl could be OK. Another option would be to code everything in Blueprints but for the client to access the raw data model of each particular implementation; this would have other downsides in terms of queries working for one technology but not for the other etc.
>
I'd prefer to code in the abstract model of bio4j for this plugin.
Because there may be other Cytoscape plugins for Blueprints and graph
database (see Cytoscape GSoC 2014 idea 23: Graph Database Support for
Cytoscape 3 by TinkerPop Software Stack [3]). The abstract model is
specified for bio4j, which I think we should focus on in this bio4j
GSoC project. If the user wants to query and visualize bio4j data
through Blueprints/neo4j directly, they may choose other TinkerPop
based Cytoscape plugins instead. Any comments?