948 reputation
29
bio website
location
age
visits member for 2 years, 10 months
seen 15 hours ago

I do software engineering at a civil engineering firm. I work with C# and Wolfram Language (i.e. "The Language Formerly Known As Mathematica").

I recently learned some Go. You should, too. It's quite nice.


1d
revised How to subtract one list from another, treating each elements as distinct?
Added (a) a third fun solution and (b) an important note to alternative solutions
1d
revised How to subtract one list from another, treating each elements as distinct?
Added a much faster alternative that still respects the suggested constraints.
1d
answered How to subtract one list from another, treating each elements as distinct?
Sep
30
awarded  Explainer
Sep
30
revised Join lists with nested list
Added some basic timing checks.
Sep
26
comment Join lists with nested list
@GordonCoale ref/Apply, Details and Options: "A negative level -n consists of all parts of expr with depth n." See ref/Depth for more explanation.
Sep
25
answered Join lists with nested list
Sep
24
comment How to open *.sif files with Mathematica
It isn't supported if it isn't listed here. Unfortunately, I don't think SIF is listed. Someone might have written an import converter for SIF, though. You may want to edit your question to ask that specifically.
Aug
17
revised $RecursionLimit::reclim: Recursion problem
Important note/caveat about my attempt at `captureValues`...
Aug
17
comment $RecursionLimit::reclim: Recursion problem
@LuisFernandoMoura, I'm not sure what the expression NumericQ[tmedNum] is trying to accomplish, but yes, it should evaluate to False because tmedNum is only a symbol denoting part of a transformation rule, not itself a numeric value.
Aug
15
comment $RecursionLimit::reclim: Recursion problem
@LuisFernandoMoura, I'm not sure unfortunately, since I don't encounter that error here. In the code above, tmedNum is permanently defined to always "hand off" to tmed, so I can only guess a problem would be with whatever current function that tmed is defined as during the iteration in which you see that error. Try enabling the Debugger (under the Evaluation menu) and enable "Break at Messages" and "Show Stack", then run your code again. When the message occurs and the stack window fills, inspect the value of tmed to verify its value is what you were expecting.
Aug
9
comment $RecursionLimit::reclim: Recursion problem
@LuisFernandoMoura, no problem, glad to have been able to help. You might want to take a look at the edit I just made to introduce an updated helper function. My first attempt at the helper function was bloated and wrong in an important case that it was trying to cover (when a Function has a parameter with the same name as a previously set symbol). It still worked for your example because that case didn't come up. Anyway, fixed now. And best of luck in your master's!
Aug
9
revised $RecursionLimit::reclim: Recursion problem
Fixed my flat-out wrong code... with a much simpler version, too.
Aug
8
answered $RecursionLimit::reclim: Recursion problem
Aug
8
comment DatabaseLink Example for DB2 and Mathematica
@RickQI, glad to be able to help! If this post answered your question to your satisfaction, feel free to click the check mark next to the post to mark it as "accepted". If it didn't, definitely feel free to (a) comment on things specific to this answer here or (b) clarify your question further by editing it with clearly marked updates. (It's important to the good functioning of this site that all posts are accurately marked up to represent their actual status.) Thanks, and hope you're enjoying the community!
Aug
7
answered DatabaseLink Example for DB2 and Mathematica
Jul
28
awarded  Critic
Jul
24
comment Problems with NMinimize
What input code defines xy3d?
Jul
18
revised How to refuse close de Dialog when press Enter Key
Duh moment for me. Second argument of Overlay makes Invisible unnecessary (and seems to eliminate some extra spacing below the InputField)
Jul
18
comment How to refuse close de Dialog when press Enter Key
@d555, no problem, glad to help. I updated the answer a bit, turns out the second argument of Overlay can be used to make the DefaultButton "present" yet invisible still. So it's simpler than I'd originally explained.