{"id":829,"date":"2011-12-21T17:54:33","date_gmt":"2011-12-21T17:54:33","guid":{"rendered":"http:\/\/eccv2012.unifi.it\/?page_id=829"},"modified":"2012-04-03T19:28:57","modified_gmt":"2012-04-03T19:28:57","slug":"eccv-2012-review-process","status":"publish","type":"page","link":"http:\/\/eccv2012.unifi.it\/documents\/eccv-2012-review-process\/","title":{"rendered":"ECCV 2012 Review process"},"content":{"rendered":"
ECCV 2012 REVIEW PROCESS<\/strong> Additional features\/innovations<\/strong><\/p>\n IMPORTANT DATES<\/strong><\/p>\n ECCV 2012 REVIEW PROCESS The process is traditional but for two main innovations: \u00a0\u00a0We eliminated the in-person plenary AC meeting (with some regret). Those meetings have become too big and expensive, and much of the feedback has been that the … Continue reading
\nThe process is traditional but for two main innovations: \u00a0\u00a0We eliminated the in-person plenary AC meeting <\/strong>(with some regret). Those meetings have become too big and expensive, and much of the feedback has been that the most valuable part of the meeting is the discussion in pairs. \u00a0Having successfully experimented with Area Chair (AC) triplets for BMVC 2011, \u00a0we replaced the meeting with AC triplets <\/strong>who will meet in person (or online) and produce ranked lists of ~90 papers. The final consolidation of the lists will be done by the PCs in consultation with the ACs.<\/p>\n\n
\n\n
\n DATE (2012)<\/em><\/strong><\/td>\n action<\/em>\/event<\/em><\/strong><\/td>\n Notes<\/em><\/strong><\/td>\n<\/tr>\n \n Feb 2012 or before<\/td>\n Every researcher who wishes to be considered for reviewing or submission registers with Google Scholar & Microsoft Academic, and submits his\/her unique ID
\nEach AC triplet arranges two meetings, one in the period 13-21 March, one in the period 29 May-10 June.<\/td>\n<\/td>\n<\/tr>\n \n 5 March 2012<\/td>\n EVENT: authors submit<\/strong><\/td>\n <\/td>\n<\/tr>\n \n 5-12 March<\/td>\n PC assigns papers to AC triplets, possibly tweaking triplet partition<\/td>\n <\/td>\n<\/tr>\n \n 12 March<\/td>\n EVENT: papers to ACs<\/strong><\/td>\n <\/td>\n<\/tr>\n \n 12-22 March<\/td>\n ACs meet and, suggest 7+ reviewers \/ paper
\nEVENT: AC TRIPLET MEETINGS<\/strong><\/td>\n<\/td>\n<\/tr>\n \n 22 March<\/td>\n EVENT: ACs supply reviewer proposals<\/strong><\/td>\n <\/td>\n<\/tr>\n \n 22-26 March<\/td>\n PC makes final reviewer assignment<\/td>\n Matching suggestions, conflicts, load balancing<\/td>\n<\/tr>\n \n 4 April<\/td>\n EVENT: Papers to reviewers<\/strong><\/td>\n <\/td>\n<\/tr>\n \n 4 April – 11 May<\/td>\n Reviewers write reviews<\/td>\n Review period<\/td>\n<\/tr>\n \n 11 May<\/td>\n DEADLINE: Return reviews<\/strong><\/td>\n <\/td>\n<\/tr>\n \n 11-21 May<\/td>\n ACs go over reviews, initiate discussions<\/td>\n <\/td>\n<\/tr>\n \n 21 May<\/td>\n EVENT:
\nReviews to authors<\/strong><\/td>\n<\/td>\n<\/tr>\n \n 21-28 May<\/td>\n Authors write rebuttals<\/td>\n <\/td>\n<\/tr>\n \n 28 May<\/td>\n EVENT: Authors submit rebuttals<\/strong><\/td>\n <\/td>\n<\/tr>\n \n 28 May – 11 June<\/td>\n ACs read rebuttals, update consolidation reports, rank their 90 papers, produce thresholds for oral and poster<\/td>\n <\/td>\n<\/tr>\n \n 11-17 June<\/td>\n PC looks at consolidations, spot problems, interact with AC triplets to obtain missing info.
\nCombine lists, suggests shifts of thresholds to AC triples if needed. \u00a0Finalizes oral\/poster\/reject on agreement of ACs.<\/td>\n<\/td>\n<\/tr>\n \n 17 June<\/td>\n EVENT: ACs finalize consolidations<\/strong><\/td>\n <\/td>\n<\/tr>\n \n <\/td>\n PCs check consolidations<\/td>\n <\/td>\n<\/tr>\n \n < 25 June<\/td>\n EVENT: Author notification<\/strong><\/td>\n <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"