26

IMO, best answered by the community. My attempt is primarily so we aren't starting from a blank slate. Guidelines for helping others help you with your code ordered according to importance for reproducibility and attracting help. Try to focus in on the issue. Do not copy all the contents of your notebook. Do not try to explain all the irrelevant parts. ...


20

"If I'm the first to post, I'll bet my answer will get at least three up-votes." Posted at 3:24 AM local time.


13

If you click on the blue In[1]:= on the web documentation page you should get a pop-up containing the code for it, as well as a short URL that links to the source. For your section I get http://wolfram.com/xid/0i1lib1d8-vcqdub which when followed redirects to http://reference.wolfram.com/language/ref/Classify.html#1273900033


11

Before deciding on posting a large dataset, try the followings: Analyze your problematic data some further. It is almost always reducable to a smaller set that still demonstrates the issue - it is of course more work on your behalf. But it also gives you more understanding, and ultimately, pleasure if you could accidentally discover the culprit. Try to test ...


10

Why and how to construct a minimal example? – A case study Let us look at a recently posted question as an example. The question, as originally posted, did not have a complete example. The definitions of functions like beta were not shown. Thus people could not run this code, and could not see the error on their own computers. Always make your ...


8

Edit the question, possibly adding your own explanations as to why the extant answers are inadequate. This assumes your question is not "substantially" different from the older one. (What "substantial" is in that case can of course be subjective.)


7

"It is certainly a duplicate, the answer is {##, f[##2]} & @@@ list, let me just look this up quickly..."


7

My thoughts: You can't stop people asking the question Some will just lazily ask without searching at all. Some will search but not find, because no matter how crystal clear you make the title of the original, they will be thinking of the problem in different terms ("matrix operation", "lump data", "interpolate duplicate abscissa values" etc) You can't ...


6

My opinion : It's a good idea to bring the subject up in chat, preferably in a special room dedicated to the subject. So if the discussion takes several days, as it is often the case, the relevant informations stay together. But one can also have a discussion without restrictions in these dedicated rooms. Maybe the problem with these rooms is that they are ...


6

Advice on where to post Wolfram Cloud questions New users of the Wolfram Language and the Wolfram Cloud may not be aware that there are at least three good places to get questions answered: Mathematica StackExchange, Wolfram Community, and Wolfram Support. Even long time users who have some experience with one or more of these resources, may be uncertain ...


5

I have such a system, but I made it complicated and it's not something that really scales out to other users. You see part of it in action here; notifications are shared between my iPhone and Apple Watch. There, it is hooked up to one of Charcoal's WebSockets, for getting notified of potential spam posts; I also use it to monitor new questions in certain ...


5

This is how "activity-sort" questions lists work. You'll notice a similar behavior on the active questions list and the various hot lists. The change you propose would make this extremely verbose; in practice, it would require two lines and be considerably more difficult to scan. Several people have suggested changes that would add a small bit of text ...


5

Can I suggest a format for Wolfram Community cross-posts? I see no problem with cross-posting - many hands make light work - but suggest that we label cross-posts in the question, near the top, rather than in a comment. (If this isn't acceptable, you can revert my edit here.)


5

You are right that a posting such as you propose risks being closed as too-broad or mainly-opinion-based. However, here are some suggestions: Post it anyway. If the post is intriguing enough to produce a lively discussion in the form of answers, it will probably survive. After all, there are a few precedents for such discussions on our main QA site. Bring ...


4

Ignore this and see Mr. Wizard's answer instead. I am not aware of any ways to link to subsection in the symbol documentation pages. You could refer to a subsection as Classify documentation page -> Options -> Feature Types -> In[3] There is a userscript that automatically inserts the documentation page link for a given symbol, but it is only for your ...


3

I think editing titles to give more accurate description of the real problem posed in the question is likely to help. This is the reason I already put some effort into editing question titles. I think most of this effort goes for nought, at least as far as those who ask questions are concerned. The software that suggests similar questions can't really match ...


3

What do you all think about creating more canonical lists of recurring problems, similar to 18393? There could be one for common list manipulation tasks, and perhaps others if the need is there. Each answer in such a Q&A would contain a statement of the problem that is general (unlike most real questions), links to where this problem has previously been ...


2

What if we had a tutorial tag that is added at some point after a particular question has received a variety of well-thought-through answers and provides a meaningful complement or expansion of the documentation? This approach may address the problems that community members have: Experienced users wasting time looking for duplicates - a question that is ...


Only top voted, non community-wiki answers of a minimum length are eligible