Simple pattern matching - Revision history

WikiSysop: /* Exercises to be handed in */

2025-10-03T13:57:10Z

Exercises to be handed in

← Older revision		Revision as of 15:57, 3 October 2025
Line 16:		Line 16:
	== Exercises to be handed in ==		== Exercises to be handed in ==
	The first 7 exercises will all have to do with the files ''data1-4.gb'', which are various Genbank entries of genes. First you should study the files, notice the structure of the data. In all exercises you will have to parse (read and find the wanted data) the files using pattern matching. Every exercise adds to the previous ones, so the final program grow big and can do a lot. It is part of the practice to be able to keep an overview of the elements of a large program. Use structure and comments to help you keep track.<br>Your program should be able to handle all files, but just one at a time.		The first 7 exercises will all have to do with the files ''data1-4.gb'', which are various Genbank entries of genes. First you should study the files, notice the structure of the data. In all exercises you will have to parse (read and find the wanted data) the files using pattern matching. Every exercise adds to the previous ones, so the final program grow big and can do a lot. It is part of the practice to be able to keep an overview of the elements of a large program. Use structure and comments to help you keep track.<br>Your program should be able to handle all files, but just one at a time.
	# Extract the accession number, the definition and the organism (and print it).
	# Extract and print all MEDLINE article numbers which are mentioned in the entries.		# Extract the accession number, the definition and the organism (and print it).<br><br>
	# Extract and print the translated gene (the amino acid sequence). Look for the line starting with /translation=. Generalize; An amino acid sequence can be short, i.e. only one line in the feature table, or long, i.e. more than one line in the feature table. Use stateful parsing.		# Extract and print all MEDLINE article numbers which are mentioned in the entries.<br><br>
	# Extract and print the DNA (whole base sequence in the end of the file). Use stateful parsing.		# Extract and print the translated gene (the amino acid sequence). Look for the line starting with /translation=. Generalize; An amino acid sequence can be short, i.e. only one line in the feature table, or long, i.e. more than one line in the feature table. Use stateful parsing.<br><br>
	# Your program already extracts the DNA. Make it also extract the positions of the coding sequence. Display them. You can recognize it by the line that starts with "     CDS     join("		# Extract and print the DNA (whole base sequence in the end of the file). Use stateful parsing.<br><br>
	# Now that you have the DNA and the positions in the DNA for the coding sequence, extract the coding DNA directly from the DNA, such that you can display the actual gene. Verify that you have done so correctly by thinking about the properties of coding DNA sequence.		# Your program already extracts the DNA. Make it also extract the positions of the coding sequence. Display them. You can recognize it by the line that starts with "     CDS     join("<br><br>
	# Find all titles and authors using stateful parsing. Put every author/title record (i.e. all authors/title in one string) in one list. Display all neatly with title on one line, authors on the next and a separator line.		# Now that you have the DNA and the positions in the DNA for the coding sequence, extract the coding DNA directly from the DNA, such that you can display the actual gene. Verify that you have done so correctly by thinking about the properties of coding DNA sequence.<br><br>
			# Find all titles and authors using stateful parsing. Put every author/title record (i.e. all authors/title in one string) in one list. Display all neatly with title on one line, authors on the next and a separator line.<br><br>
	# Returning all the way back to lesson 6, Stateful parsing, exercise 6. Given the content of today's lecture, how would you improve this exercise now (shorter, more efficient code) ?		# Returning all the way back to lesson 6, Stateful parsing, exercise 6. Given the content of today's lecture, how would you improve this exercise now (shorter, more efficient code) ?

WikiSysop: /* Required course material for the lesson */

2025-09-22T10:02:57Z

Required course material for the lesson

← Older revision		Revision as of 12:02, 22 September 2025
Line 5:		Line 5:
	\|}		\|}
	== Required course material for the lesson ==		== Required course material for the lesson ==
	Powerpoint: [https://teaching.healthtech.dtu.dk/material/22116/~~22116_08~~-PatternMatch.ppt Simple pattern matching]<br>		Powerpoint: [https://teaching.healthtech.dtu.dk/material/22116/22116_09-PatternMatch.ppt Simple pattern matching]<br>
	<!-- Video: [https://panopto.dtu.dk/Panopto/Pages/Viewer.aspx?id=4a8a478b-33e4-4a7a-bc38-af27012cf23f Pattern matching in Python]<br> -->		<!-- Video: [https://panopto.dtu.dk/Panopto/Pages/Viewer.aspx?id=4a8a478b-33e4-4a7a-bc38-af27012cf23f Pattern matching in Python]<br> -->
	[[Example code - Wrong parsing]] What many do, and is sooo bad.<br>		[[Example code - Wrong parsing]] What many do, and is sooo bad.<br>

WikiSysop: /* Exercises to be handed in */

2025-09-03T10:05:25Z

Exercises to be handed in

← Older revision		Revision as of 12:05, 3 September 2025
Line 15:		Line 15:

	== Exercises to be handed in ==		== Exercises to be handed in ==
	The first 7 exercises will all have to do with the files ''data1-4.gb'', which are various Genbank entries of genes. First you should study the files, notice the structure of the data. In all exercises you will have to parse (read and find the wanted data) the files using pattern matching. Every exercise adds to the previous ones, so the final program can do a lot. ~~Remember~~. Your program should be able to handle all files, but just one at a time.		The first 7 exercises will all have to do with the files ''data1-4.gb'', which are various Genbank entries of genes. First you should study the files, notice the structure of the data. In all exercises you will have to parse (read and find the wanted data) the files using pattern matching. Every exercise adds to the previous ones, so the final program grow big and can do a lot. It is part of the practice to be able to keep an overview of the elements of a large program. Use structure and comments to help you keep track.<br>Your program should be able to handle all files, but just one at a time.
	# Extract the accession number, the definition and the organism (and print it).		# Extract the accession number, the definition and the organism (and print it).
	# Extract and print all MEDLINE article numbers which are mentioned in the entries.		# Extract and print all MEDLINE article numbers which are mentioned in the entries.

WikiSysop: /* Required course material for the lesson */

2025-09-01T06:21:22Z

Required course material for the lesson

← Older revision		Revision as of 08:21, 1 September 2025
Line 7:		Line 7:
	Powerpoint: [https://teaching.healthtech.dtu.dk/material/22116/22116_08-PatternMatch.ppt Simple pattern matching]<br>		Powerpoint: [https://teaching.healthtech.dtu.dk/material/22116/22116_08-PatternMatch.ppt Simple pattern matching]<br>
	<!-- Video: [https://panopto.dtu.dk/Panopto/Pages/Viewer.aspx?id=4a8a478b-33e4-4a7a-bc38-af27012cf23f Pattern matching in Python]<br> -->		<!-- Video: [https://panopto.dtu.dk/Panopto/Pages/Viewer.aspx?id=4a8a478b-33e4-4a7a-bc38-af27012cf23f Pattern matching in Python]<br> -->
			[[Example code - Wrong parsing]] What many do, and is sooo bad.<br>

	== Subjects covered ==		== Subjects covered ==

WikiSysop: /* Exercises to be handed in */

2025-08-31T19:09:10Z

Exercises to be handed in

← Older revision		Revision as of 21:09, 31 August 2025
Line 14:		Line 14:

	== Exercises to be handed in ==		== Exercises to be handed in ==
	The first 4 exercises will all have to do with the files ''data1-4.gb'', which are various Genbank entries of genes. First you should study the files, notice the structure of the data. In all exercises you will have to parse (read and find the wanted data) the files using pattern matching. Every exercise adds to the previous ones, so the final program can do a lot. Remember. Your program should be able to handle all files, but just one at a time.		The first 7 exercises will all have to do with the files ''data1-4.gb'', which are various Genbank entries of genes. First you should study the files, notice the structure of the data. In all exercises you will have to parse (read and find the wanted data) the files using pattern matching. Every exercise adds to the previous ones, so the final program can do a lot. Remember. Your program should be able to handle all files, but just one at a time.
	# Extract the accession number, the definition and the organism (and print it).		# Extract the accession number, the definition and the organism (and print it).
	# Extract and print all MEDLINE article numbers which are mentioned in the entries.		# Extract and print all MEDLINE article numbers which are mentioned in the entries.

WikiSysop: /* Exercises to be handed in */

2025-08-31T19:07:37Z

Exercises to be handed in

← Older revision		Revision as of 21:07, 31 August 2025
Line 22:		Line 22:
	# Now that you have the DNA and the positions in the DNA for the coding sequence, extract the coding DNA directly from the DNA, such that you can display the actual gene. Verify that you have done so correctly by thinking about the properties of coding DNA sequence.		# Now that you have the DNA and the positions in the DNA for the coding sequence, extract the coding DNA directly from the DNA, such that you can display the actual gene. Verify that you have done so correctly by thinking about the properties of coding DNA sequence.
	# Find all titles and authors using stateful parsing. Put every author/title record (i.e. all authors/title in one string) in one list. Display all neatly with title on one line, authors on the next and a separator line.		# Find all titles and authors using stateful parsing. Put every author/title record (i.e. all authors/title in one string) in one list. Display all neatly with title on one line, authors on the next and a separator line.
	# Returning all the way back to lesson 6, Stateful parsing, exercise 6. Given the content of today's lecture, how would you ~~make~~ this exercise now?		# Returning all the way back to lesson 6, Stateful parsing, exercise 6. Given the content of today's lecture, how would you improve this exercise now (shorter, more efficient code) ?

	== Exercises for extra practice ==		== Exercises for extra practice ==

WikiSysop: /* Exercises to be handed in */

2025-08-29T14:21:23Z

Exercises to be handed in

← Older revision		Revision as of 16:21, 29 August 2025
Line 22:		Line 22:
	# Now that you have the DNA and the positions in the DNA for the coding sequence, extract the coding DNA directly from the DNA, such that you can display the actual gene. Verify that you have done so correctly by thinking about the properties of coding DNA sequence.		# Now that you have the DNA and the positions in the DNA for the coding sequence, extract the coding DNA directly from the DNA, such that you can display the actual gene. Verify that you have done so correctly by thinking about the properties of coding DNA sequence.
	# Find all titles and authors using stateful parsing. Put every author/title record (i.e. all authors/title in one string) in one list. Display all neatly with title on one line, authors on the next and a separator line.		# Find all titles and authors using stateful parsing. Put every author/title record (i.e. all authors/title in one string) in one list. Display all neatly with title on one line, authors on the next and a separator line.
			# Returning all the way back to lesson 6, Stateful parsing, exercise 6. Given the content of today's lecture, how would you make this exercise now?

	== Exercises for extra practice ==		== Exercises for extra practice ==

WikiSysop: /* Exercises to be handed in */

2025-08-29T14:17:57Z

Exercises to be handed in

← Older revision		Revision as of 16:17, 29 August 2025
Line 19:		Line 19:
	# Extract and print the translated gene (the amino acid sequence). Look for the line starting with /translation=. Generalize; An amino acid sequence can be short, i.e. only one line in the feature table, or long, i.e. more than one line in the feature table. Use stateful parsing.		# Extract and print the translated gene (the amino acid sequence). Look for the line starting with /translation=. Generalize; An amino acid sequence can be short, i.e. only one line in the feature table, or long, i.e. more than one line in the feature table. Use stateful parsing.
	# Extract and print the DNA (whole base sequence in the end of the file). Use stateful parsing.		# Extract and print the DNA (whole base sequence in the end of the file). Use stateful parsing.
	# In the files ''data1-4.gb'' find all titles and authors using stateful parsing. Put every author/title record (i.e. all authors/title in one string) in one list. Display all neatly with title on one line, authors on the next and a separator line.		# Your program already extracts the DNA. Make it also extract the positions of the coding sequence. Display them. You can recognize it by the line that starts with "     CDS     join("
	~~# Continue with exercise 4:~~ Your program already extracts the DNA. Make it also extract the positions of the coding sequence. Display them. You can recognize it by the line that starts with "     CDS     join("		# Now that you have the DNA and the positions in the DNA for the coding sequence, extract the coding DNA directly from the DNA, such that you can display the actual gene. Verify that you have done so correctly by thinking about the properties of coding DNA sequence.
	# ~~Continue with exercise 4:~~ Now that you have the DNA and the positions in the DNA for the coding sequence, extract the coding DNA directly from the DNA, such that you can display the actual gene. Verify that you have done so correctly by thinking about the properties of coding DNA sequence.		# Find all titles and authors using stateful parsing. Put every author/title record (i.e. all authors/title in one string) in one list. Display all neatly with title on one line, authors on the next and a separator line.
	# ~~Given that you have a string containing some DNA~~ (~~ask for input or hardcode it~~ in ~~the program~~), ~~how would you check that it actually only contains ATCG using~~ the ~~methods of today's lesson?~~
	~~# Given that you have~~ a ~~string of comma separated values, like "1,22,333,4,5"~~. ~~How would you find the positions of the commas in the string?~~

	== Exercises for extra practice ==		== Exercises for extra practice ==

WikiSysop: /* Exercises to be handed in */

2025-08-29T14:12:22Z

Exercises to be handed in

← Older revision		Revision as of 16:12, 29 August 2025
Line 19:		Line 19:
	# Extract and print the translated gene (the amino acid sequence). Look for the line starting with /translation=. Generalize; An amino acid sequence can be short, i.e. only one line in the feature table, or long, i.e. more than one line in the feature table. Use stateful parsing.		# Extract and print the translated gene (the amino acid sequence). Look for the line starting with /translation=. Generalize; An amino acid sequence can be short, i.e. only one line in the feature table, or long, i.e. more than one line in the feature table. Use stateful parsing.
	# Extract and print the DNA (whole base sequence in the end of the file). Use stateful parsing.		# Extract and print the DNA (whole base sequence in the end of the file). Use stateful parsing.
	# <font color="#AA00FF">Improve exercise 5.8 using all you have learned. The program shall now take a DNA FASTA file (asking interactively for it), and reverse and complement all entries in the file. There can be more than one entry, study ''dna7.fsa''. Hint: Use substitution or translation for complementing the DNA. I will point out that the reading and writing of fasta files with many entries is a regular occurrence in bioinformatics (and exam), so be sure to get it right. Many people mistakenly believe that they should use a form of stateful parsing with a flag for this - doing so confuses the issue, so abstain from that.</font>		# In the files ''data1-4.gb'' find all titles and authors using stateful parsing. Put every author/title record (i.e. all authors/title in one string) in one list. Display all neatly with title on one line, authors on the next and a separator line.
	* Given that you have a string containing some DNA (ask for input or hardcode it in the program), how would you check that it actually only contains ATCG using the methods of today's lesson?		# Continue with exercise 4: Your program already extracts the DNA. Make it also extract the positions of the coding sequence. Display them. You can recognize it by the line that starts with "     CDS     join("
	* Given that you have a string of comma separated values, like "1,22,333,4,5". How would you find the positions of the commas in the string?		# Continue with exercise 4: Now that you have the DNA and the positions in the DNA for the coding sequence, extract the coding DNA directly from the DNA, such that you can display the actual gene. Verify that you have done so correctly by thinking about the properties of coding DNA sequence.
	* In the files ''data1-4.gb'' find all titles and authors using stateful parsing. Put every author/title record (i.e. all authors/title in one string) in one list. Display all neatly with title on one line, authors on the next and a separator line.		# Given that you have a string containing some DNA (ask for input or hardcode it in the program), how would you check that it actually only contains ATCG using the methods of today's lesson?
	* Continue with exercise 4: Your program already extracts the DNA. Make it also extract the positions of the coding sequence. Display them. You can recognize it by the line that starts with "     CDS     join("		# Given that you have a string of comma separated values, like "1,22,333,4,5". How would you find the positions of the commas in the string?
	* Continue with exercise 4: Now that you have the DNA and the positions in the DNA for the coding sequence, extract the coding DNA directly from the DNA, such that you can display the actual gene. Verify that you have done so correctly by thinking about the properties of coding DNA sequence.

	== Exercises for extra practice ==		== Exercises for extra practice ==

WikiSysop: /* Exercises for extra practice */

2025-08-29T14:01:14Z

Exercises for extra practice

← Older revision		Revision as of 16:01, 29 August 2025
Line 27:		Line 27:

	== Exercises for extra practice ==		== Exercises for extra practice ==
			You will program a [https://en.wikipedia.org/wiki/Reverse_Polish_notation reverse polish notation] calculator. This is somewhat complicated, so I will split up the job in a number of smaller exercises, where the one exercise builds on the previous. Shortly, reverse polish notation is a mathematical notation in which operators follow their operands, i.e. adding two numbers is written by "3 4 +" instead of "3 + 4". We will utilize a [https://en.wikipedia.org/wiki/Stack_(abstract_data_type) stack], which is simply a list, where elements are added to and removed from the bottom.
			* Let's start with making the overall structure; a loop that asks for input, which is one item/command at a time. Inside the loop, there can be a number of operations depending on the input. If you enter a number, it should be simply appended to your list (the stack, which is the word I will use in the rest of the exercises here). If you enter commands '''STOP''', '''EXIT''' or '''QUIT''', the loop should end and the program stop. If you enter something that the program does not understand it should write "Illegal command", but otherwise do nothing.
			* Add the following commands: '''PEEK''', which displays the last number in the stack, and '''SHOW''' which will display the entire stack.
			* Add the standard math operations, '''+''', '''-''', '''*''' and '''/''': These remove 2 numbers from the stack (the last number in stack is the first operand and the second last number is the second operand), perform the operation and appends the result back to the stack. You notice operand order matters for - and /. At this point we have a simple but functional calculator.
			* Add single number operations '''LOG''' and '''SQRT''', which replaces the last number in the stack with the log/square root of the number.
			* Solidify your program by ensuring any operations first check if the required number of operands are on the stack before trying to perform the operation. Display "Not enough operands on the stack" and otherwise do nothing if the check fails. Hint: Maybe lists of zero, one and two operands commands could be useful.
			* Add the commands: '''DROP''' which simply removes the last number on the stack, '''=''', which removes the last number on the stack and displays it, '''SWITCH''', which switches the last two numbers on the stack, and '''DUP''' which duplicates the last number on the stack, i.e stack consists of 1, after DUP it consists of 1 1.
			* Add the commands: '''ABS''', '''NEG''' which replaces the last number on the stack which the absolute/negative value of the number.
			* At this point you can probably work out some mathematical operations to add that require one or 2 operands by yourself. I can think of the '''SIN''', '''COS''' & '''TAN''' operations, the '''INT''' taking the integer part of a number, '''EXP'''onential and '''SQUARE'''. Modulo operation with '''%'''. '''FAC'''torial. You could add constants like '''PI''' and '''E''' that simply puts an appropriate value on the stack.
			* Add stack control with '''CLEAR''' to empty the stack and extend the '''SWITCH''' to switch the numbers as two given position like "SWITCH 2 4" if given positions.