Problem 44819. Relative pose in 2D: problem 1

@goc3 that broke my test! Seems there is some implicit scoping rule, by adding the %% it means that T is not available in subsequent %% cells. Fixed it by calling the user function multiple times. This stuff is not well documented: the scoping rules, the need for a leading %% etc.

Sorry for any confusion that may have been caused. Yes, there may be a need for more detailed explanations of some site functioning, but that is beyond my power. For what it's worth, the scoping rule is consistently applied for all problems on the site: variables called within each test case are only available to that test case. I (and many other problem creators) end up repeating lines for any required variables within each test case.

The %% is an issue because it is so poorly documented and hence poorly understood (or even not understood). The following seems to be how it works. [Note: in the following I will use "↲" to indicate the end of a line in the code/output.]
     
~~~~~~~~~~
Creator writes this TEST SUITE:
~~~~~~~~~~
-----
commandA↲
commandB↲
↲
%% test 1↲
commandX↲
↲
%% test 2↲
commandY↲
-----
     
~~~~~~~~~~
Cody RUNS the following tests:
~~~~~~~~~~
Test 1: (i) commandA; (ii) commandB; and (iii) commandX.
Test 2: (i) commandA; (ii) commandB; and (iii) commandY.
     
~~~~~~~~~~
Cody DISPLAYS the following output:
~~~~~~~~~~
-----
%%commandA↲
commandB↲
↲
%% test 1↲
commandX↲
↲
[output from commandX only]↲
↲
%% test 2↲
commandY↲
↲
[output from commandY only]↲
↲
-----
~~~~~~~~~~
     
Notice: (i) any commands before the first %% [namely commandA and command] are run at the beginning of every test; (ii) output of any commands before the first %% is suppressed [never displayed]; (iii) for the player, a spurious "%%" is displayed on the first line of the Test Suite if there were any commands before the first "%%".
     
It is actually a very clever structure for Problem Creators writing a Test Suite. Therefore I'd be keen to retain it. See e.g. https://www.mathworks.com/matlabcentral/cody/problems/44655
     
The annoyances are: (i) lack of documentation; (ii) suppression of output; and (iii) insertion of a spurious "%%" in the display.
Although none of these three issues affect the running, they cause a lot of confusion and misunderstanding.