On Tue, Feb 22, 2011 at 9:31 AM, nathan binkert <[email protected]> wrote:
> > Oh, actually, this made me think of something I wanted to bring up. What > > we're talking about now is basically a config file, but we already have > > something called that. I was describing M5 to some folks at work a little > > while ago, and there seemed to be some confusion about how configuration > > worked. I think they may have assumed ahead of time a config would be > more > > like a static file of values (like the ini-s used to be). > > > > So to straighten out both of those issues, what if we called these > default > > and command line values the configuration, and then call the python > scripts > > simulation scripts? That disambiguates the term and hopefully makes it > more > > obvious what, say, se.py is for and how to set up a simulation. I think > it's > > something people usually figure out relatively quickly, but it wouldn't > hurt > > to make it a little more obvious. > > Makes sense, but would probably require renaming the directory. > Some of us already do call them "simulation scripts", e.g., see http://m5sim.org/wiki/index.php/Simulation_Scripts_Explained Renaming the directory from "configs" to "scripts" would help reinforce this though. It might be good to couple that with some other restructuring, if any is planned, to make those scripts more reusable. Right now things are not factored out that well IMO (though I haven't used them in a while). Steve
_______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
