Reputation
12,291
Top tag
Next privilege 15,000 Rep.
Protect questions
Badges
20 49
Newest
 Nice Answer
Impact
~107k people reached

1d
answered Notebook cells space on disk profiler
1d
comment How to make async functions?
isn't your description of what you want more or less in contradiction with the async in the questions title? Please elaborate what you try to achieve, probably giving an example to play with...
1d
comment Problem with NDSolve: derivative interpreted as square
@jon: the only answer so far suggested that this might be a formatting issue. It can happen in rare cases (e.g. by accidentially using some unknown keyboard shortcuts) that some of the formatting gets into a state where it is difficult to understand what happens. Could you select the cell which contains the equations and then choose the menu entry Cell -> Show Expression? This will show the plain box expression in the FrontEnd. If you would copy that and put it here as code we could probably understand what has happened...
1d
revised Notebook cells space on disk profiler
added notes about what to do to create list of links ordered by cell-size
1d
answered Notebook cells space on disk profiler
Jun
27
answered How can I timestamp a notebook?
Jun
26
comment Convert spreadsheet (Excel) to *.csv during import
I've seen you have accepted my answer. Would you mind to let us know what you ended up to do and if that worked? I think this kind of feedback is what makes the site valuable and keeps people motivitated to answer questions. It is also encouraged to answer own questions in such cases describing in more detail what you did. My answer is kind of vague and probably only of limited value, so I would even be happy if you'd accept your own answer instead of mine :-)
Jun
26
comment Convert spreadsheet (Excel) to *.csv during import
@SjoerdC.deVries: I added that link to my answer, thanks for the hint, I was too lazy to do the obvious and search this site...
Jun
26
revised Convert spreadsheet (Excel) to *.csv during import
added link to .NET example as suggested by Sjoerd
Jun
26
comment Manipulate code crashes V10.1
it doesn't crash for me (10.1 on Windows 7), but it does continuously update as Aloghi mentioned. I think chances are good that this will not crash if you avoid that continuous updating. That can easily be achieved by extracting the body into a function which only has the actual parameters as arguments and use that instead: Manipulate[calculate[ts,f, Z0, RL,T],...]. If you need this inclosed in the Manipulate use SaveDefinitions. Would you let us know if that solves your problem?
Jun
26
revised Convert spreadsheet (Excel) to *.csv during import
added 136 characters in body
Jun
26
answered Convert spreadsheet (Excel) to *.csv during import
Jun
25
answered What is the role of the pattern object in this implementation?
Jun
25
comment What is the role of the pattern object in this implementation?
@abrentonc: Mathematica is at its core a symbolic system, so it will evaluate a function for non-numeric arguments, e.g. f[x_]:=x^3;y=.;f[y]. If you call something like NDSolve which only handle those parameters as numeric input, then you have to restrict the function pattern to numeric parameters.
Jun
25
revised ToExpression in Manipulate
added 733 characters in body
Jun
25
answered ToExpression in Manipulate
Jun
25
comment Disabling a Button
if the data is just numeric values I think either would work well. I guess that csv is probably somewhat faster to load (importing excel has somewhat more overhead, especially for the first import in a session)...
Jun
25
comment Disabling a Button
@user38498: Ah, ok then the question makes more sense: xls/xlsx vs. csv. I don't think it is easy to give general advice for xls/xlsx vs. csv. I think both can be imported reasonably well in Mathematica, at least for "standard" content, that is not very large, only numbers and strings etc. It should be easy to test whether your data can be imported in either format and how long that tests...
Jun
25
comment Disabling a Button
my comment wasn't meant as critizism: when I saw your answer I just was seeing advantages (concerning robustness and flexibility) if one would not restict the check to an exact match of the initial value as I did. Of course your solution also has the advantage fo being shorter, but I wouldn't trade that for robustness. Concerning that I noticed that you'd actually need something like TrueQ@Quiet@DirectoryQ@DirectoryName[b1] as DirectoryQ doesn't comply with the usual *Q function conventions as it gives a message and returns unevaluated in certain cases...
Jun
25
comment Disabling a Button
but that would start disabled if b1 happend to have a value, for whatever reason. To be more robust one could test for something like: StringQ[b1]&&DirectoryQ[DirectoryName[b1]], which would also keep the button enabled if the user cancelles the file choose dialog. I think the most robust solution would be to use that test and still initialize with something well defined :-).