SHARE
TWEET

8f27082a54659c8f8f8be9226b7822b2

a guest Oct 21st, 2019 70 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. Review for team 8f27082a54659c8f8f8be9226b7822b2
  2.  
  3. Legend:    
  4.   + Positive    
  5.   ~ Neutral    
  6.   - Negative    
  7.  
  8. Given a scale with quarter points I would award:
  9.     Textual description:    5.25 / 6
  10.     Code quality:               5.75 / 6
  11.     Results:                        5.25 / 6
  12.  
  13. The grades given are based on the comments below. The negative and positive points are comments about either something lacking or which impressed me. A lack of comment on something is indicative that I considered it good or reasonably good.
  14.  
  15. Overall comments:
  16.   + Clear and sufficient textual description.
  17.   + Code comments are clear when present.
  18.   + Good use of the libraries given.
  19.   - Some areas are lacking code comments.
  20.   - A few minor typos in some of the textual description though which do not reduce readability.
  21.  
  22.     Comments per section:
  23.  
  24. Section A:
  25.  
  26. A1:
  27.   - For loops for dataframe operations doesn’t make the most of pandas' vectorization. Using Filter or some other provided method should speed up execution. (Later on you use apply which is good.)
  28.  
  29. A2:
  30.   + Nice use of the in-place attribute for dataframe operations.
  31.   + Good checking that the index is correct after modifications to it.
  32.  
  33. A3.1:
  34.   + Use of a boxplot to show outliers is very appropriate.
  35.   + Good explanations as to why the extra outlier shown in the boxplot graph is not considered.
  36.   + Logical explanation of why the outliers considered are to be dropped.
  37.   - The last outlier in the boxplot not being considered is not explained.
  38.  
  39. A3.2:
  40.   + Printing unique year values give an exhaustive list of everything to be considered.
  41.   - No code comments during this sub-exercise, code is still quite easy to follow but a comment or two on the parser would be appreciated.
  42.  
  43. A3.3
  44.   - Not immediately clear as to why it is concluded that the papers from 2010 and 2011 are not referenced, a bit more textual description as to what is going on would help.
  45. A3.4
  46.   - The ‘.’ from the paper titles is not taken into account when comparing titles.
  47. Good comments in the scraper.
  48.  
  49. A4
  50.   - The ‘period’ comment and equivalent code conflict, the code has a +1 while the comment ignores it.
  51.   - The division function checking for 0 is rendered redundant due to the +1.
  52.   - Law not found or guessed.
  53.  
  54.  
  55. Section B:
  56.  
  57. B1
  58.   - Unconvincing argument as to the limitations of the naïve scores. The quality of papers or conferences is not discussed.
  59.  
  60. B2.1
  61.   + Very good comments in this section.
  62.  
  63. B2.2
  64.   ~ Perhaps use a bar graph for more readability rather than a long list.
  65.  
  66. B2.3
  67.   + Once again, the comments in this section are very much sufficient.
  68.   + Complete analysis of naïve vs H5 ranking.
  69.  
  70. B2.4
  71.   + Great analysis as to the problems with naïve ranking.
  72.   - The textual description with ‘about a 1000 ranks’ is referencing a difference of 2000-3000 ranks which can lead to confusion.
  73.  
  74. B2.5
  75.   + Nice and clear, the potential limitations of the H5 index were found.
  76.   ~ No code comments but the textual description is enough to know what is being done. However the actual implementation would be easier to follow with comments.
  77.  
  78. B3
  79.   + The use of H5 per year is justified and the following analysis reflects the results found.
  80.  
  81. Section C:
  82.  
  83. C
  84.   - The symbolic versus connectionist plots were asked to be in 2 different graphs.
  85.   + The symbolic versus connectionist plots show the trends to be analysed very well.
  86.   ~ When modifying a plot as the last line of a cell, you can for example write ‘_ = ax.set_title(...)’ to eliminate the automatic print of the return of the function.
  87.   - Hard to follow exactly why authors per paper means the connectionist approach does not weaken.
RAW Paste Data
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!
 
Top