Am I the only one for whom documentation reindexing happens every time F1 is fired in a new section? Very often causing front end hand with 'abort dynamic updating'?

@P.Fonseca 'client' not 'clients' :) and it is rather 'happens sometimes' as opposed to 'it is the case now' :p

Hi everybody!

Is there a way to remove some set of values from the list

In here, not terrify. I have a list of numbers, which need to be plotted. Is there a way to remove those with inderminate values. I have {x,y,Inderminate} for some couple of values. I want to remove the, keeping other things intact

@L.K. DeleteCases

Indeterminate can be matched perfectly, so you have a pattern like {_, _, Indeterminate}

@halirutan Thanks. Yes this the pattern

I have them scattered here and there, trying to painstackling remove using Except

@halirutan does it work even for nested lists? Like the matrix I have

@halirutan I am just checked the documentation

@L.K. Look up the doc of DeleteCases. You can specify on which level it should operate

@halirutan Sorry, sure let me do that

@L.K. If your pattern is narrow enough so that it won't match anything other that your inner lists, you can safely use Infinity as levelspec

@halirutan You mean using /. (ReplaceAll)?

test = {{1, 2, Indeterminate}, {3, 4, 5}, {{1, 2, 3}, {1, 3, Indeterminate}}};
DeleteCases[test, {_, _, Indeterminate}, Infinity]

@halirutan Thanks again. Because I was doing DeleteCases[dataToPlot, {_Integer, _Integer, Indeterminate}]

And it didn't work

@halirutan I even tried DeleteCases[test, {_, _, Indeterminate}, Infinity], seems no success :(

@L.K. You numbers are not Integers

@halirutan My ignorance

Thanks a lot @halirutan. Life saver. My ignorance is just too much.

Is the only way to get this to work is with multiple function defintions?

 ClearAll[f]
f[ts_, maxError_, fitAlgorithm_: LinearModelFit,
  algorithmParams_: {\[FormalX], \[FormalX]},
  opts : OptionsPattern[]] :=
 <|"fitAlgorithm" -> fitAlgorithm,
  "algorithmParams" -> algorithmParams, "opts" -> {opts}|>`

This does not work for f[1, 2, StepMonitor :> (a = # &)] as it takes the StepMonitor option to be fitAlgoritm instead of the first item of OptionsPattern

I was kinda amazed to see how serious design decisions are taken with respect to adding new features in MMA. twitch.tv/videos/207012986 the deciding authority has forgotten much of pure maths and gets confused well too often. An example how Buzzword mania can doom even someone so qualified. Many chilling videos are available for us to get a hint on the new bunch of functions that will increase the MMA installation size.