K.I.S.S. is what the initial release of ModuOps is all about. The software is a random car generator with a scale factor added so that one can make it appear as though cars arrive a one location at a different rate than another.
In my book, when a layout that only exists for a couple of days, KISS is a perfect way to get the operating session up and functioning in as little time as possible. We came to run trains, right?
Keeping it simple also implies that complex jobs may be hard to setup, or just not possible. One of my biggest concerns with the approach I've taken is with folks who are looking for this app to solve complex routing problems. That's not what it is.
ModuOps (right now) randomly generates weighted car requests and adds those cars to trains. That's it. Nothing more nothing less. This approach does have the advantage of significantly less administrative requirements to get to the point where you are generating trainlists.
So, KISS is the rule with version 1.0.
Friday, January 16, 2015
Sunday, January 4, 2015
Answers to early questions
What is the name of the software?
ModuOps, short for Modular Operations
Are you going to add additional features to ModuOps?
ModuOps, short for Modular Operations
Does ModuOps require any additional software to run?
It is a compiled, free-standing Application
What OS's does it run on?
ModuOps runs on Mac OS-X, Windows and Linux
Is ModuOps Open Source?
YES! Licensed as GPL v3 Open Source
How much will ModuOps Cost?
ModuOps is FREE to download and use
Can I make a donation to the Project?
Donations are gladly accepted to help me cover costs of development/training. However at this time I do not have any mechanism setup to take donations. I will soon.
What development language are you using?
ModuOps is written in Livecode. If you know what that is and you want to help please contact me.
Can I test/use it now?
ModuOps is in development now and is not ready for public use
Is there any place I can see it used?
ModuOps' first live test is 1/24 & 1/25 at the West Springfield Model train show.
Can ModuOps be used for Home layout operations?
ModuOps is PERFECT for home layouts too!
What's the release schedule?
Things could change but here's my plan as of today. ModuOps first test release (Alpha) February 2015. ModuOps version 1.0 Spring 2015 (fyi-spring ends on 6/20/2015 ;-)
Can I make suggestions for the software.
Version 1.0 feature set is frozen. I need to figure out what the best way to get feature requests will be. For now, jot them down and hold on to them.
Is MRBT really that good for Free-mo layouts?
Yes, I think MRBT a great for Modular layouts.Are you going to add additional features to ModuOps?
Yes, I have bigger plans than an MRBT clone.
Feature: No Reporting Marks
What? Are you crazy? Well, maybe. But I'm sticking by the decision to not use reporting marks in ModuOps.
For a Modular setup typically at a train show, reporting marks add a significant burden in getting the layout to a point where it is operating (pre-show and during the event), and adds some aggravation when things don't go as the Ops Software thought it should.
Free-mo setups by definition are dynamic and to some extent unknown. Having a software system that is tolerant of general car types is an advantage to getting this style of layout working and looking like it's a railroad doing real work.
ModuOps moves generic "Car Types" around the layout. It is up to the yard and train crews to select specific cars to meet the requirements that are called for on in a Manifest. When using the MRBT mode with Set Outs only, instructions are added to the Manifest to pickup all cars when dropping. This enables the operating session to effectively "clean up" mistakes made by folks.
Yes, in the real world, reporting marks are used on all the paperwork. To me the operations are real enough for my liking without the reporting marks. Preparation for the Ops Plan is much quicker without having to coordinate with all the individuals coming exactly what cars including reporting marks are they bringing to an event.
It's takes a little to get used to not seeing reporting marks on Manifests. But give it a chance and you'll see it actually works pretty good.
For a Modular setup typically at a train show, reporting marks add a significant burden in getting the layout to a point where it is operating (pre-show and during the event), and adds some aggravation when things don't go as the Ops Software thought it should.
Free-mo setups by definition are dynamic and to some extent unknown. Having a software system that is tolerant of general car types is an advantage to getting this style of layout working and looking like it's a railroad doing real work.
ModuOps moves generic "Car Types" around the layout. It is up to the yard and train crews to select specific cars to meet the requirements that are called for on in a Manifest. When using the MRBT mode with Set Outs only, instructions are added to the Manifest to pickup all cars when dropping. This enables the operating session to effectively "clean up" mistakes made by folks.
Yes, in the real world, reporting marks are used on all the paperwork. To me the operations are real enough for my liking without the reporting marks. Preparation for the Ops Plan is much quicker without having to coordinate with all the individuals coming exactly what cars including reporting marks are they bringing to an event.
It's takes a little to get used to not seeing reporting marks on Manifests. But give it a chance and you'll see it actually works pretty good.
Saturday, January 3, 2015
ModuOps Development Progressing
Contrary to what you see on this Blog, I've been moving forward with the software. In fact the software is likely to be used at the NE Free-mo setup later this month (January 2015) in its first large scale test.
Here's some screen shots so you can see what ModuOps looks like right now.
First step in getting the software going is to enter Car Types.
My hope is the format of the screens is modern looking and easy to read.
Here's the Module screen.
As you can see things are looking pretty good right now.
I'm hoping to release an alpha in February with beta in March and 1.0 final before summer 2015. If you're interested in the software, bookmark this Blog to stay updated on the release schedule.
Bob
Here's some screen shots so you can see what ModuOps looks like right now.
First step in getting the software going is to enter Car Types.
Here's the Module screen.
Clicking the "Consignees" button takes you to the details of the Module. Here you'll see a list of Consignees (Industries), Spots where cars can be set out, and a list of cars the spot can take. A track chart of the module displays a high level diagram of the module.
Next up is a Trains screen. This is where trains are created. The Route is selected form available modules and can easily be re-ordered. Crew Instructions are added here as well.
Below is a section of the manifest created for the train listed above.
As you can see things are looking pretty good right now.
I'm hoping to release an alpha in February with beta in March and 1.0 final before summer 2015. If you're interested in the software, bookmark this Blog to stay updated on the release schedule.
Bob
Sunday, December 29, 2013
Some History
Way back when in the late 1990s, a software application called "Mad River and Big Timber" was developed for the The Sacramento Modular Railroaders. The software took into considerations the nuances of a modular layout and the impact this would have on operations.
For many modular layouts, especially Free-mo setups, the layout changes at every setup. Also, rollingstock most likely is not know until module owners add cars to their modules.
Mad River and Big Timber (MRBT) solved this problem for modular clubs by creating a system that did not track car details during an operation session the way other software packages do. This methodology works well with some home setups as well.
The last active effort on MRBT was in 2001 with a minor update made to the software. A lot has changed since then with computers -- Heck an iPad or Smartphone was a Buck Rogers fantasy back then.
I do love operations as it pertains to model railroading. I personally followed along articles and wrote the program in Model Railroader back in the early 90s as they published articles using the Basic programming language to create a switchlist for operating your layout. MRBT is used by my local Free-mo club, the New England Free-mo's, and it's limitations are apparent.
My goal for the first version of ModuOps is to bring the ideas of MRBT to a modern platform. I'd love to see a Mac, Linux and Windows version of the software on day 1. ModuOps is an Open Source project and will be FREE to download. ModuOps incorporates a modern interface by today's standard and is ready for future expansion (tablets and smartphones are on the white board).
Version 1 of ModuOps will attempt to replicate the logic of MRBT with a couple of upgrades (detailed in later Blog posts). While MRBT is the inspiration, you will see that ModuOps looks nothing like the original software.
If you'd like to stay up to date on the progress of the application, please follow this Blog. I am progressing quite nicely with the software and I'm getting close to version 0.1.0! Stay tuned...
For many modular layouts, especially Free-mo setups, the layout changes at every setup. Also, rollingstock most likely is not know until module owners add cars to their modules.
Mad River and Big Timber (MRBT) solved this problem for modular clubs by creating a system that did not track car details during an operation session the way other software packages do. This methodology works well with some home setups as well.
The last active effort on MRBT was in 2001 with a minor update made to the software. A lot has changed since then with computers -- Heck an iPad or Smartphone was a Buck Rogers fantasy back then.
I do love operations as it pertains to model railroading. I personally followed along articles and wrote the program in Model Railroader back in the early 90s as they published articles using the Basic programming language to create a switchlist for operating your layout. MRBT is used by my local Free-mo club, the New England Free-mo's, and it's limitations are apparent.
My goal for the first version of ModuOps is to bring the ideas of MRBT to a modern platform. I'd love to see a Mac, Linux and Windows version of the software on day 1. ModuOps is an Open Source project and will be FREE to download. ModuOps incorporates a modern interface by today's standard and is ready for future expansion (tablets and smartphones are on the white board).
Version 1 of ModuOps will attempt to replicate the logic of MRBT with a couple of upgrades (detailed in later Blog posts). While MRBT is the inspiration, you will see that ModuOps looks nothing like the original software.
If you'd like to stay up to date on the progress of the application, please follow this Blog. I am progressing quite nicely with the software and I'm getting close to version 0.1.0! Stay tuned...
Monday, October 28, 2013
Welcome to the ModuOps Blog!
As part of getting the public side of ModuOPs going, I've created this Blog for the software. ModuOPs is an application in development to assists in the operations of Modular Layouts, especially Free-mo. The software takes into considerations of a setup where the layout changes from setup to setup, and the rollingstock is not known in advance.
We also think ModuOPs can be used for home layouts as well. The system's design is very easy to learn and very forgiving of mistakes made by operators.
I'll be posting more details as the software moves forward. I've got lots of ideas for this software and I hope we can help make operating your Modular layout more interesting and manageable.
We also think ModuOPs can be used for home layouts as well. The system's design is very easy to learn and very forgiving of mistakes made by operators.
I'll be posting more details as the software moves forward. I've got lots of ideas for this software and I hope we can help make operating your Modular layout more interesting and manageable.
Subscribe to:
Posts (Atom)