modularity

I used the fastgreedy algorithm in igraph for my community detection in a weighted, undirected graph. Afterwards I wanted to have a look at the modularity and I got different values for different methods and I am wondering why. I included a short example, which demonstrates my problem: library(igraph) d<-matrix(c(1, 0.2, 0.3, 0.9, 0.9, 0.2, 1, 0.6, 0.4, 0.5, 0.3, 0.6, 1, 0.1, 0.8, 0.9, 0.4, 0.1, 1, 0.5, 0.9, 0.5, 0.8, 0.5, 1), byrow=T, nrow=5) g<-graph.adjacency(d, weighted=T, mode="lower",diag=FALSE, add.colnames=NA) fc<-fastgreedy.community(g) fc$modularity[3] #[1] -0.05011095 modularity(g

My scenario I have to implement a "modular" android app. There is a core module from which I should be able to invoke other modules. Each module provides a different feature to the user. Imagine I am making a city guide, then one module may contain a map with POIs, another one an event calendar and a third one pre-defined city guides. The modules contain views to be loaded in activities of the core module (like dashboards where each module puts its item/picture). They also contain activities which should be invoked (like when a user taps an item on the dashboard). As far as I know, I will need

I'm looking for a way to modularize Rails applications. As I've seen there is no built-in way of accomplishing it. I've found different plugins/core hacks but I feel untrusted about the way they work and their maturity. Do you have any experience on this? So far I found this ones: Desert: http://github.com/pivotal/desert Rails engines: http://rails-engines.org/ Rails engines are part of the current stable rails 2.X and so aren't really "hacks" anymore. They seem like a good fit if you want to add fairly course-grained application functionality to an application - a good example might be adding

I have an Activity A hosting two main Fragment F1 and F2 . Both F1 and F2 have nested Fragment , each with its own Listener interface for exchanging data. From what I understood from the answer to this question , the activity A : needs to know every single interface declared by the fragments hosted by F1 and F2 needs to route the events generated by the fragments in F1 and F2 to the correct main fragment, F1 or F2 . If I understood correctly, there is no modularity in this approach: the activity needs to know everything about both the fragments it hosts ( F1 and F2 ) and the fragments that are

By modular applications I mean applications in which base functionality and data model can be extended without modifying core application code. It's a popular approach with eg. open source CRMs like SugarCRM or VTiger. This approach may be followed in asp.net mvc application using Areas or (portable areas from MVC contrib) which allow adding new controllers and views in separate assemblies, without impacting core dlls. The problem arises when one wants to extend the base application's data model. It's not possible in any practical sense with entity framework where the model definition is

Recently we decided to refactor our old web ASP.NET MVC project. We decided to use modular architecture and build it around the ASP.NET WebAPI to write dependent and independent modules for it. Is there any tutorial or explanation or library helping build modular web applications? If so, can you point me to this? Thanks in advance!! Depends on your necessity. If you need to provide service to the world outside your app domain go for SOA. If you need only project organization, just fallow Microsoft Application Architecture , or some Business Architecture Guide for .NET . You should see some of