256 reputation
18
bio website linkedin.com/pub/…
location San Francisco, CA
age 29
visits member for 3 years
seen 2 days ago

PhD, Chemical Engineering, MIT, 2013.

Pro Tem moderator on SciComp.SE.


Dec
29
awarded  Autobiographer
Jan
17
awarded  Informed
Dec
17
awarded  Yearling
Nov
26
awarded  Nice Question
Feb
22
comment Optimization as a branch: is that a thing?
Computational scientists frequently struggle with the question of whether optimization is worth it; see "How much should scientific software be optimized?" on SciComp.SE for the computational science perspective. Little of the code I write for research purposes needs to be optimized, but it would not surprise me that scientific applications would invest this effort, since I know of a few software packages that tout performance as a selling point.
Feb
16
awarded  Self-Learner
Feb
6
awarded  Teacher
Feb
6
answered Real world implementation of functional programming?
Feb
6
comment What are good ways to organize input files (Makefiles, SConstruct, CMakeLists.txt, etc.) to build automation software?
Yeah, that's what I was trying to do when I filtered out a lot of files, because the SConstruct dependency parser picks up a huge number of files. So I filtered those out, and used the Python script at the link to make a dotfile so I could visualize the parts of the DAG that I thought were important. It worked, and I got a small enough graph so I could pick out what was important, but I didn't see a whole lot I could use there. I suspect this strategy is a lot easier to use with Make because it's easier to find repeated rules in Makefiles, as you can see from the source I posted.
Feb
6
revised What are good ways to organize input files (Makefiles, SConstruct, CMakeLists.txt, etc.) to build automation software?
Added an example with syntax highlighting.
Feb
6
answered What are good ways to organize input files (Makefiles, SConstruct, CMakeLists.txt, etc.) to build automation software?
Feb
5
revised What are good ways to organize input files (Makefiles, SConstruct, CMakeLists.txt, etc.) to build automation software?
added 2 characters in body
Feb
5
revised What are good ways to organize input files (Makefiles, SConstruct, CMakeLists.txt, etc.) to build automation software?
Added examples of my build scripts based on Thorbjørn's suggestion.
Feb
5
awarded  Editor
Feb
5
comment What are good ways to organize input files (Makefiles, SConstruct, CMakeLists.txt, etc.) to build automation software?
I've added examples to illustrate what I'm working with right now.
Feb
5
revised What are good ways to organize input files (Makefiles, SConstruct, CMakeLists.txt, etc.) to build automation software?
Added examples of my build scripts based on Thorbjørn's suggestion.
Feb
5
revised What are good ways to organize input files (Makefiles, SConstruct, CMakeLists.txt, etc.) to build automation software?
Added "best-practices" and "refactoring" tags, because I am looking at best practices for refactoring and streamlining builds.
Feb
5
comment What are good ways to organize input files (Makefiles, SConstruct, CMakeLists.txt, etc.) to build automation software?
+1 for the idea of looking at the DAG. I agree that there are potential opportunities to refactor there. Visualizing the DAG can be a pain in the ass. For Makefiles, there's Makefile::GraphViz, and for SCons, there's a Python script here that may require a bit of hacking, depending on the project. The graphs that script gave me were sometimes heinously large, so I found that I had to filter carefully what I wanted to visualize.
Feb
5
comment What are good ways to organize input files (Makefiles, SConstruct, CMakeLists.txt, etc.) to build automation software?
I agree that GNU Autoconf was made for portability and maintainability of builds. At one point, I investigated learning Autoconf and found that it was going to take more time than I was willing to invest. (I'm finishing my PhD, so building this software needs to happen sooner rather than later.) Perhaps in the future? Portability isn't even the main issue for me, it's the length and lack of modularity in the build scripts, and I'm not sure that porting to Autoconf will solve those problems.
Feb
5
awarded  Supporter