Skip to main content

programming - Using Goto and Label in different cells?


I'd like to solve an optimization problem, which involves changing the parameters and re-evaluating. The problem is that I can't find a way to jump from one cell to another.


For example:



  1. Set some parameters


  2. Define a system

  3. Evaluate with current parameters

  4. Check if a condition is met

  5. Change parameters and re-evaluate if necessary


I know that Goto[] does not work when Label[] is not in the same compound expression but here is what I want to do:


Example code with Goto and Label


The real code is a bit more lengthy thus Goto[] and Label[] cannot be written in the same compound expression. Is there a simple way to solve this problem or do I have to create a separate notebook/package for the iterative parts of the code?



Answer



I think you are in a context where you have a "real life" problem and you don't care about computer science, good practise for program developpers etc...



Your program is not aimed to be shared, to be reusable, except by you, later, assuming that you have memorized (partly in mind) some traces of what you have done.


Briefly summarized, you write code for yourself, and there's "no holds-barred", only the result of your calculus is interesting.


So you develop some code, interactively, like a script, until you have the result ( - period)


Say you want to use a formula you have found in a book, for example, the calculus of altitude of a geostationary satellit.


Here is the code :


(* constants *) 
gravitationConstant=6.6 10^-11;
earthMass=5.9 10^24;
earthRotationalSpeed= 2 Pi/(3600 24.);
earthRadius=12.700 10^6/2;


(* formula *)
geostationaryAltitude=(earthMass gravitationConstant/(earthRotationalSpeed^2))^(1/3);
result=(geostationaryAltitude-earthRadius) /1000


35563.6



Until here you think of gravitationConstant, earthMass, earthRotationalSpeed as constants. But now you want to try with different values of the earthMass (generally speaking, according to Murphy' s law N°III.3. : "a constant is always variable")


Here is how to modify the code with minimum typing effort :



(* constants *) 
gravitationConstant=6.6 10^-11;
earthMass=5.9 10^24;
earthRotationalSpeed= 2 Pi/(3600 24.);
earthRadius=12.700 10^6/2;

(* formula *)
automatisedScript00[]:=(
geostationaryAltitude=(earthMass gravitationConstant/(earthRotationalSpeed^2))^(1/3);
result=(geostationaryAltitude-earthRadius) /1000

)

and then :


earthMass=5.8 10^24;
automatisedScript00[]
earthMass=6.0 10^24;
automatisedScript00[]


35325.4

35799.



Notes :




  • No need to use Module[...]. Module is intended to localize some variables, it is not a kind of box for automatised-code embedding (function, module, routine etc... in other languages).




  • You could write automatisedScript00 instead of automatisedScript00[]. So far I know, Mathematica's interpretation is the same, but using [] allows you to easily pass the Symbol name without unintentional evaluation.





  • It is easy to "debug" : you can afterward inspect the final state of the variables. Thanks to Dynamic[], you can even observe the variables in "real time".




  • These are informations for computer users, not programmers, for people who want to automatize some action in the way they want, not in the way some people think they "should" use computer with predefined automatized processes, finally for people who refuse to be computer victims.




Comments

Popular posts from this blog

mathematical optimization - Minimizing using indices, error: Part::pkspec1: The expression cannot be used as a part specification

I want to use Minimize where the variables to minimize are indices pointing into an array. Here a MWE that hopefully shows what my problem is. vars = u@# & /@ Range[3]; cons = Flatten@ { Table[(u[j] != #) & /@ vars[[j + 1 ;; -1]], {j, 1, 3 - 1}], 1 vec1 = {1, 2, 3}; vec2 = {1, 2, 3}; Minimize[{Total@((vec1[[#]] - vec2[[u[#]]])^2 & /@ Range[1, 3]), cons}, vars, Integers] The error I get: Part::pkspec1: The expression u[1] cannot be used as a part specification. >> Answer Ok, it seems that one can get around Mathematica trying to evaluate vec2[[u[1]]] too early by using the function Indexed[vec2,u[1]] . The working MWE would then look like the following: vars = u@# & /@ Range[3]; cons = Flatten@{ Table[(u[j] != #) & /@ vars[[j + 1 ;; -1]], {j, 1, 3 - 1}], 1 vec1 = {1, 2, 3}; vec2 = {1, 2, 3}; NMinimize[ {Total@((vec1[[#]] - Indexed[vec2, u[#]])^2 & /@ R...

functions - Get leading series expansion term?

Given a function f[x] , I would like to have a function leadingSeries that returns just the leading term in the series around x=0 . For example: leadingSeries[(1/x + 2)/(4 + 1/x^2 + x)] x and leadingSeries[(1/x + 2 + (1 - 1/x^3)/4)/(4 + x)] -(1/(16 x^3)) Is there such a function in Mathematica? Or maybe one can implement it efficiently? EDIT I finally went with the following implementation, based on Carl Woll 's answer: lds[ex_,x_]:=( (ex/.x->(x+O[x]^2))/.SeriesData[U_,Z_,L_List,Mi_,Ma_,De_]:>SeriesData[U,Z,{L[[1]]},Mi,Mi+1,De]//Quiet//Normal) The advantage is, that this one also properly works with functions whose leading term is a constant: lds[Exp[x],x] 1 Answer Update 1 Updated to eliminate SeriesData and to not return additional terms Perhaps you could use: leadingSeries[expr_, x_] := Normal[expr /. x->(x+O[x]^2) /. a_List :> Take[a, 1]] Then for your examples: leadingSeries[(1/x + 2)/(4 + 1/x^2 + x), x] leadingSeries[Exp[x], x] leadingSeries[(1/x + 2 + (1 - 1/x...

What is and isn't a valid variable specification for Manipulate?

I have an expression whose terms have arguments (representing subscripts), like this: myExpr = A[0] + V[1,T] I would like to put it inside a Manipulate to see its value as I move around the parameters. (The goal is eventually to plot it wrt one of the variables inside.) However, Mathematica complains when I set V[1,T] as a manipulated variable: Manipulate[Evaluate[myExpr], {A[0], 0, 1}, {V[1, T], 0, 1}] (*Manipulate::vsform: Manipulate argument {V[1,T],0,1} does not have the correct form for a variable specification. >> *) As a workaround, if I get rid of the symbol T inside the argument, it works fine: Manipulate[ Evaluate[myExpr /. T -> 15], {A[0], 0, 1}, {V[1, 15], 0, 1}] Why this behavior? Can anyone point me to the documentation that says what counts as a valid variable? And is there a way to get Manpiulate to accept an expression with a symbolic argument as a variable? Investigations I've done so far: I tried using variableQ from this answer , but it says V[1...