Conversation
…rogramming language to process, analyze, and visualize large biological datasets efficiently Very hard to tell!
There was a problem hiding this comment.
Excellent work, Nadine! You have set up both PyCharm and GitHub and connected the two with a push and pull request. The only thing left to do is to copy and paste the poem that is output by the "import this" command, and that will tell me that your Python is able to access libraries correctly.
Remember, Nadine, in the world of bioinformatics, the only limit is your imagination (and maybe your computer's RAM). So go forth and conquer those datasets – your future discoveries are waiting in those lines of code!
I will award full points once this change is made.
Score: pending/0.5
There was a problem hiding this comment.
Hello
I dont know how to do the "import this" command
should i write it as a code in function of x and print?
There was a problem hiding this comment.
In the original .py file, there was a line that simply said "import this" before the prompts to fill in, however, it appears to be deleted on your commit. Simply write "import this" in the first line on the .py file, run it again, and it should output all of the requested text.
There was a problem hiding this comment.
Your Python obviously works, so I will give full points for this component.
Score: 0.5/0.5
…rogramming language to process, analyze, and visualize large biological datasets efficiently Very hard to tell! The Zen of Python, by Tim Peters Beautiful is better than ugly. Explicit is better than implicit. Simple is better than complex. Complex is better than complicated. Flat is better than nested. Sparse is better than dense. Readability counts. Special cases aren't special enough to break the rules. Although practicality beats purity. Errors should never pass silently. Unless explicitly silenced. In the face of ambiguity, refuse the temptation to guess. There should be one-- and preferably only one --obvious way to do it. Although that way may not be obvious at first unless you're Dutch. Now is better than never. Although never is often better than *right* now. If the implementation is hard to explain, it's a bad idea. If the implementation is easy to explain, it may be a good idea. Namespaces are one honking great idea -- let's do more of those! Process finished with exit code 0
Enter final count: 20 Enter time elapsed: 2 Growth rate: 5.0 Process finished with exit code 0
Enter final count: 20 Enter time elapsed: 2 invalid numbers Process finished with exit code 0
Sequence Length: 15 A: 3, C: 4, G: 5, T: 3 GC Content: 60.00% Process finished with exit code 0
nathanielpolley
left a comment
nathanielpolley
left a comment
There was a problem hiding this comment.
Beginner objectives satisfied.
Intermediate objectives pending.
Advanced objectives satisfied.
Final score: pending/3
There was a problem hiding this comment.
I am liking what I am seeing here. A creative way to test for only As, Ts, Cs, and Gs in the absence of list structures. This is EXACTLY the type of out-of-the-box and creative thinking that I wish to encourage.
All objectives satisfied.
Score: 2/2
There was a problem hiding this comment.
For this, you will need to use the "import math" library in order to implement the growth function as described using math's log() function. A very good effort to filter out negatives in your conditional. However, you will also need to deal with the cases of the user providing a final count that is less than the initial count, as well as to parse through any non numerical input that may be provided.
For this, I would recommend an outer if/else structure that uses the ".isdigit()" method to sort out any negative or decimal values (as both "-" and "." in the input string would return a FALSE), as well to use a nested if/else statement within that to test if the final is greater than the initial (after having converted your objects to ints), and then prompting to the user the corresponding error for each of those instances.
Very close, I will revisit this once all of that has been implemented.
Score: pending/1
There was a problem hiding this comment.
Very spectacular work integrating the theory you learned at office hours. The code does what it is supposed to do, is compact with no redundant elements.
Full score.
Score: 1/1
There was a problem hiding this comment.
Your Python obviously works, so I will give full points for this component.
Score: 0.5/0.5
nathanielpolley
left a comment
nathanielpolley
left a comment
There was a problem hiding this comment.
Week_0
Beginner objectives satisfied
Intermediate objectives satisfied
Advanced objectives satisfied
Total score: 3.5/3.5
Week_1
Beginner objectives satisifed
Intermediate objectives pending
Advanced objectives pending
Total score: pending/3.5
There was a problem hiding this comment.
Very spectacular work integrating the theory you learned at office hours. The code does what it is supposed to do, is compact with no redundant elements.
Full score.
Score: 1/1
There was a problem hiding this comment.
Everything functions as it should here. Nice handling with list types and the enumerate function call in your for loop.
Score: 0.5/0.5
2 participants
No description provided.