DVCS blessed repo replication among geographically distributed teams
My company is exploring the move from Perforce to a DVCS and we currently use lots of Perforce proxies because the software development teams are spread over Germany, China, USA and Mexico and sometimes bandwidth from one place to another is not that great.
Distributed Transaction Framework across webservices
I am designing a new system that has one central web service and several site web services which are spread across the country and some overseas. It has some data that must be identical on all sites.
Can Foswiki be used as a distributed Redmine replacement?
I am quite familiar with and love using git, among other reasons due to its distributed nature. Now I’d like to set up some similarly distributed (FOSS) Project Management software with features similar to what Redmine offers, such as
Design in one team, coding in another
I will be involved in a project where all the software design is made by a local team and these designs are sent to an offshore team for coding.
Design in one team, coding in another
I will be involved in a project where all the software design is made by a local team and these designs are sent to an offshore team for coding.
Design in one team, coding in another
I will be involved in a project where all the software design is made by a local team and these designs are sent to an offshore team for coding.
Design in one team, coding in another
I will be involved in a project where all the software design is made by a local team and these designs are sent to an offshore team for coding.
New nodes joining distributed genetic algorithm
I’m sort of torn on what to do for implementation of my distributed genetic algorithm problem. I would like to be able to have nodes join and part at will and not take down the whole system. But this introduces the problem of mismatch of generations. Often times a genetic algorithm simulation is capped by a certain amount of generations and if I have a node that is on 75 out of 100 generations and a brand new node joins the cluster I’m not sure if I should fake it and start at 75 and copy one of the other nodes as a starting point or have it start out at 0 and potentially have the results delayed until the end of execution of the new node. I was hoping someone had some input on what they could see as problems in addition to a long wait time with this new node if I start at 0, I am struggling to think of what could go wrong in both approaches other than that.
New nodes joining distributed genetic algorithm
I’m sort of torn on what to do for implementation of my distributed genetic algorithm problem. I would like to be able to have nodes join and part at will and not take down the whole system. But this introduces the problem of mismatch of generations. Often times a genetic algorithm simulation is capped by a certain amount of generations and if I have a node that is on 75 out of 100 generations and a brand new node joins the cluster I’m not sure if I should fake it and start at 75 and copy one of the other nodes as a starting point or have it start out at 0 and potentially have the results delayed until the end of execution of the new node. I was hoping someone had some input on what they could see as problems in addition to a long wait time with this new node if I start at 0, I am struggling to think of what could go wrong in both approaches other than that.
New nodes joining distributed genetic algorithm
I’m sort of torn on what to do for implementation of my distributed genetic algorithm problem. I would like to be able to have nodes join and part at will and not take down the whole system. But this introduces the problem of mismatch of generations. Often times a genetic algorithm simulation is capped by a certain amount of generations and if I have a node that is on 75 out of 100 generations and a brand new node joins the cluster I’m not sure if I should fake it and start at 75 and copy one of the other nodes as a starting point or have it start out at 0 and potentially have the results delayed until the end of execution of the new node. I was hoping someone had some input on what they could see as problems in addition to a long wait time with this new node if I start at 0, I am struggling to think of what could go wrong in both approaches other than that.