|
Re: FRC Simulator Features Ideas
BXD Guys,
Is this diagram "What's in a simulated match?" close enough to the way you have viewed robots, fields and matches, for us to use it describing what you have/haven't produced?
I dislike the description I wrote when I posted the diagram, but at the time I uploaded the diagram, that description was the best compromise between work-in-progress and results-of-past-progress that my brain and fingers would type for me.
I do think that it is a useful diagram. I also fully realize that there is more than one way to skin the cat, and I'm curious if the diagram matches your group's approach.
If there is a match (or if you/we can create an different agreed diagram), then (I think) contributors to this thread will be able to post better suggestions and questions. I know that will be the case for me.
Blake
__________________
Blake Ross, For emailing me, in the verizon.net domain, I am blake
VRC Team Mentor, FTC volunteer, 5th Gear Developer, Husband, Father, Triangle Fraternity Alumnus (ky 76), U Ky BSEE, Tau Beta Pi, Eta Kappa Nu, Kentucky Colonel
Words/phrases  I avoid: basis, mitigate, leveraging, transitioning, impact (instead of affect/effect), facilitate, programmatic, problematic, issue (instead of problem), latency (instead of delay), dependency (instead of prerequisite), connectivity, usage & utilize (instead of use), downed, functionality, functional, power on, descore, alumni (instead of alumnus/alumna), the enterprise, methodology, nomenclature, form factor (instead of size or shape), competency, modality, provided(with), provision(ing), irregardless/irrespective, signage, colorized, pulsating, ideate
|