Developer Quiz

What command would not checkout code from the repository?
1. fcm co
2. fcm ct
3. fcm checkout
D
Which commands would commit code to the repository?
1. fcm commit|ct|ci
2. fcm commit|ct
3. fcm commit|ci
4. fcm ct|ci
C
What is the best command for finding out in what files or directories your working copy are different from the repository, i.e. what has been modified etc?
1. fcm update
2. fcm trunk
3. fcm status
4. fcm info
C
How would you find out if you are working on the trunk or a branch version and if a branch what it is called?
1. From the Revision number via fcm lookup
2. From the Relative URL via fcm lookup
3. From the Relative URL via fcm info
4. From the Revision number via fcm info
C
What does "?" mean when you issue the fcm status command?
1. Item is missing and was there previously
2. Item is not under version control
3. Item is conflicted
4. Item is modified
B
What does "!" mean when you issue the fcm status command?
1. Item is missing
2. Item is not under version control
3. Item is conflicted
4. Item is modified
A
Why would you need to use the command "fcm switch" or "fcm sw"?
1. After creating a JULES-Rose suite branch and then to move to it
2. After checking out a JULES-Rose suite branch
3. Before committing your JULES-Rose suite change
4. Before creating a JULES-Rose suite branch from the trunk when on the trunk
A
Which of these commands can you use to create a branch?
1. fcm branch-create|bc|create
2. fcm branchcreate|bcreate
3. fcm branchcreate|bc|bcreate
4. fcm branch-create|bc|bcreate
D
What command would you use to pull your changes from one area in the repository into another?
1. fcm merge
2. fcm import
3. fcm pull
4. fcm fetch
A
What commands would you use to see the line-by-line or file-by-file differences between two versions or revisions of the repository?
1. fcm diff|di
2. fcm difference|di
3. fcm difference|diff|di
4. fcm difference|di
A
What option would you add to your fcm "difference" command to use the graphical tool to display the differences?
1. --graphical, --g
2. -graphical, -g
3. --graphical, -g
4. -graphical, --g
C
How can we run a JULES-Rose suite?
1. rose suite-run
2. Use the "Play/Run" button in rose edit
3. rose suite-run or Use the "Play/Run" button in rose edit
4. rose run
5. rose run or Use the "Play/Run" button in rose edit
C
How can we look at JULES Rose-suite or JULES rose stem job output/errors?
1. gcylc GUI, right click on the task, View, job.*
2. rose bush
3. cylc-run/log/job/1/<TASKNAME>/NN/job.*
4. cylc-run/work/1/<TASKNAME>/output/
5. All of the above
6. A-C
7. A, B, D
F
What is JULES rose stem?
1. A testing system for JULES code to check that new science or tech changes do not break existing code
2. A testing system for JULES code to check the UM
3. A testing system for JULES-Rose suites to test all suites ever
4. A testing system for JULES-Rose suites to test the UM
A
How would you update your branch to match the trunk?
1. fcm sw trunk; fcm update trunk; fcm sw <BRANCHNAME>; fcm merge trunk
2. fcm sw trunk; fcm update trunk; fcm merge trunk
3. fcm merge trunk
4. fcm update trunk; fcm merge trunk
A
How could you resolve an "!" returned from the "fcm st" command which is because you deleted the file without using fcm?
1. fcm rm <FILENAME>
2. You cannot
3. fcm rm --check|-c <FILENAME>
4. fcm rm -f <FILENAME>
C
What two repositories will you be using and needing for JULES only work?
1. JULES code and JULES suites
2. JULES code and roses u suites
3. UM code and JULES suites
4. UM code and roses u suites
B
How can you find out what the FCM keywords for are on your system?
1. fcm kp
2. fcm keywords-print
3. fcm keywords-point
4. A and B
5. A and C
D
How can you get a copy of the JULES code?
1. fcm ci fcm:jules.x_tr@vn#.# or fcm ci https://code.metoffice.gov.uk/svn/jules/main/trunk@vn#.#
2. fcm co fcm:jules.x_tr@vn#.# or fcm co https://code.metoffice.gov.uk/svn/jules/main/trunk@vn#.#
3. fcm copy fcm:jules.x_tr@vn#.# or fcm copy https://code.metoffice.gov.uk/svn/jules/main/trunk@vn#.#
4. fcm get fcm:jules.x_tr@vn#.# or fcm get https://code.metoffice.gov.uk/svn/jules/main/trunk@vn#.#
5. fcm fetch fcm:jules.x_tr@vn#.# or fcm fetch https://code.metoffice.gov.uk/svn/jules/main/trunk@vn#.#
B

Complete the JULES-Rose code branch create sequence:

fcm ____ <BRANCH_NAME> fcm:jules.x_tr@vn#.#
fcm ____ fcm:jules.x_br/dev/<USERNAME><BRANCH_NAME>
cd <BRANCH_NAME>
#make changes and add a new file
fcm ___ 
fcm ____ <NEW_FILE> 
fcm ___ 
#nothing unknown
fcm ___
#add commit message
y
fcm ___ 
#no local changes, changes on the JULES code branches repository

bc, co, st, add, st, ci, st
bc, ci, st, add, st, co, st
co, bc, st, add, st, ci, st
ci, bc, st, add, st, co, st

Complete the JULES rose suite copy sequence:

rosie ____ <SUITE_ID> #add to description, save and close cd <NEW_SUITE_ID> #make changes to the suite including deleting a file fcm ___ fcm ____ ___ <NEW_FILE> fcm ___ #nothing unknown fcm ___ #add commit message y fcm ___ #no local changes, changes on the rosie u repository

copy, st, rm, st, ci, st
copy, st, rm, st, co, st
co, st, rm -c, st, ci, st
copy, st, rm -c, st, ci, st

Complete the JULES rose suite branch create sequence:

rosie ____ <SUITE_ID>
cd <SUITE_ID>
fcm ___ <BRANCH_NAME>
#add commit message, save and close
fcm ___
#incase the branch name is forgotten
fcm ___ <BRANCH_NAME>
#make changes to the suite
fcm ___
fcm ___
#add commit message
y
fcm ___
#nothing unknown
#no local changes, changes on the suite branch of the rosie u repository
fcm ___ trunk
#back to the trunk of the suite ID

checkout, bc, blt, sw, info, st, ci, st, sw
checkout, bc, blt, sp, info, st, ci, st, sw
checkout, bc, bls, sw, info, st, ci, st, sw
checkout, bc, bls, sp, info, st, ci, st, sw

What does KGO mean?
1. Known Good Output
2. Kept Good Output
3. Kept Good Origin
4. Kept Good Origin
A
When can KGO be different and tests/tasks fail in the JULES rose stem?
1. Bug fix and very small changes
2. Bug fix and improve Science and very small changes
3. Never
4. Improve Science and very small changes
5. Big changes only
B
Why create a ticket?
1. Report a bug
2. Fix a bug
3. Improve science
4. Add functionality to the code
5. Add functionality to rose stem
6. Add rose stem tests
7. Add to docs
8. All of above
9. All of above except the rose stem ones
H
Who can commit to the trunk of the JULES code?
1. Anyone
2. Anyone with a MOSRS account
3. Anyone with a JULES MOSRS account
4. Only the branch owner of the branch that they want to commit to the trunk
5. JULES System Manager and UM Systems Team
6. JULES System Manager only
E
Who can commit to the branch of the JULES code?
1. Anyone
2. Anyone with a MOSRS account
3. Anyone with a JULES MOSRS account
4. Only the branch owner of the branch that they want to commit to the trunk
5. JULES System Manager and UM Systems Team
6. JULES System Manager only
D
Who can commit to a JULES-Rose suite on rosie u repository?
1. Anyone
2. Anyone with a JULES MOSRS account
3. Only the owner of the JULES-Rose suite
4. Only the owner of the JULES-Rose suite branch
5. JULES System Manager and UM Systems Team
6. JULES System Manager only
C
What should be in the Ticket Description before the review is requested?
1. Description of what the ticket is to address
2. Description of how the ticket is to address the change
3. [wiki:ticket/###/TicketSummary Ticket Summary]
4. [log:main/branches/dev/USERNAME/BRANCH_NAME BRANCH_NAME]
5. [log:doc/branches/dev/USERNAME/BRANCH_NAME doc BRANCH_NAME] as required
6. All of the above
F
Where is the evidence for the Ticket Summary page from the JULES rose stem tests located for copying?
1. cylc-run/<SUITE_ID>/trac.log
2. cylc-run/<SUITE_ID>/log/trac.log
3. cylc-run/<SUITE_ID>/log/suite/log
4. cylc-run/<SUITE_ID>/log/suite/err
5. rose bush
A
What is the review process?
create ticket -> changes -> ____________ > ___________ > ask for sci/tech rev and code rev > _________ > address comments > sci/tech approve > ___________ > ____________ > code approved > JULES system manager or UM systems team to commit code
1. rose stem tests, complete ticket summary, assign code rev, assign sci/tech rev, address comments
2. rose stem tests, complete ticket summary, assign sci/tech rev, assign code rev, address comments
3. complete ticket summary, rose stem tests, assign sci/tech rev, assign code rev, address comments
4. complete ticket summary, rose stem tests, assign code rev, assign sci/tech rev, address comments
B
Who can do a sci/tech rev?
1. Anyone
2. Anyone who has worked on the ticket
3. Anyone who has NOT worked on the ticket
4. Person with relevant understanding and background on the area
5. Anyone who has been trained to do a sci/tech review
6. A & D
7. B & D
8. C & D
9. A & C
H
Who can do a code rev?
1. Anyone
2. Anyone who has worked on the ticket
3. Anyone who has NOT worked on the ticket
4. Person with relevant understanding and background on the area
5. Anyone who has been trained to do a code review
6. E & A
7. E & B
8. E & C
9. E & D
H
What does a HoT branch mean?
1. Head of Trunk
2. Head of Top
3. Hand of Trunk
4. Hand of Top
A
How can you make a HoT branch using FCM?
1. fcm bc fcm:jules.x_tr
2. fcm bc fcm:jules.x_tr@HEAD
3. fcm bc fcm:jules.x_tr@vn#.#
4. A or B
5. A or C
6. B or C
7. A or B or C
D
How can you merge your original branch into your new HoT branch?
fcm ___ fcm:jules.x_br/dev/<USERNAME>/<HoT_BRANCH> ; cd <HoT_BRANCH> / fcm ___ <ORIGINAL_BRANCH> ;fcm ___ ; fcm ___ ; y
1. ci, merge, diff -g, co
2. co, merge, diff -g, ci
3. co, squash, diff -g, ci
4. co, pull, diff -g, ci
B
What files are edited when adding a namelist
1. rose-meta/jules-standalone/HEAD/rose-app.conf, src/control/shared/???_mod.F90, src/science/<scheme>/<routine>.F90
2. src/control/shared/???_mod.F90, src/science/<scheme>/<routine>.F90
3. rose-meta/jules-standalone/versions.py, src/control/shared/???_mod.F90, src/science/<scheme>/<routine>.F90
4. rose-meta/jules-standalone/HEAD/rose-app.conf, rose-meta/jules-standalone/versions.py, src/control/shared/???_mod.F90, src/science/<scheme>/<routine>.F90
D
When you change metadata in anyway what command or commands must you run to check it?
1. rose app-upgrade -M /path/to/the/metadata/for/testing/ app/fcm_make HEAD && rose macro --fix -M /path/to/the/metadata/for/testing/; ./bin/upgrade_jules_test_apps vn#.#_t###
2. rose app-upgrade -M /path/to/the/metadata app/fcm_make <version> && rose macro --fix -M /path/to/the/metadata; ./bin/upgrade_jules_test_apps vn#.#_t###
3. rose app-upgrade -M /path/to/the/metadata/for/testing/ app/fcm_make && rose macro --fix -M /path/to/the/metadata/for/testing/; ./bin/upgrade_jules_test_apps vn#.#_t###
4. rose app-upgrade -M /path/to/the/metadata/for/testing/ app/fcm_make <version> && rose macro --fix -M /path/to/the/metadata/for/testing/; ./bin/upgrade_jules_test_apps vn#.#_t###
A

JULES Developer quiz

JULES questions

Developer quiz

Answers