Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Development Meeting notes from 9/17/15 #70

Open
bhowes-tt opened this issue Oct 13, 2015 · 0 comments
Open

Development Meeting notes from 9/17/15 #70

bhowes-tt opened this issue Oct 13, 2015 · 0 comments

Comments

@bhowes-tt
Copy link
Member

@mnaugle-tt @mostaphaRoudsari @JonatanS Justin Nardone and myself met on 9/17/15, and discussed the following. If any topic deserves further discussion here on Github, please feel free to break it out into a new issue. Just want to be sure all of this is in the record:

  • We need more examples for public consumption. Examples in product design, architecture, and engineering should be included to show (and test!) the versatility of the platform. For example in engineering, it would be cool to show the results of a number of different load combinations ... something more like an analysis results possibility space, all using the same design but under different loads.
  • main problem this work is trying to solve: it is hard to present/explain design iterations, and difficulty increases as the number of iterations increases.
  • new graph ideas: 2d scatterplot where X and Y are user defined variables. Optionally assign color gradient as a third variable.
  • modular charts UI. The interface should be able to be customized to fit the problem domain. For example, a user might only want the PCP and the 3d model (like me!) or they may want a number of 3d model viewers for their favorite iterations (like matt!) or they may want a PCP, a radar chart, and some optional sliders (like mostapha!). They should be able to easily lace up solutions like these to fit their problem domain.
  • repo structure ... how can people contribute to this as an open project? Right now I think that would be a tough question to answer. People (including us) should be able to contribute and customize easily. This strategy should be designed along with the modular charts item above.
  • @mostaphaRoudsari mentioned vega - a d3 grammar.
  • Justin thinks this should exist in Catia, Solidworks, Inventor. And it should be able to be used upstream ... in other words, set up a design space you'd like to evaluate using a PCP filter, press go and let solidworks crunch models and run analyses all night. When you come in the next day, you know something new about your design space. I thought this idea was goddamn awesome.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant