GSoCIdeas: Difference between revisions

From GNU Radio
Jump to navigation Jump to search
(Add Sebastian Müller als co-mentor for SigMF idea)
(rearranged ideas and tidying)
Line 1: Line 1:
= Summer of Code 2020: Project ideas list =
== Summer of Code 2020: Project ideas list ==


This is the list of project ideas for the summer of code 2019 within GNU Radio.<br />
This is the list of project ideas for the summer of code 2019 within GNU Radio.<br />
Line 19: Line 19:
* Both OOTs and in-tree improvements are welcome
* Both OOTs and in-tree improvements are welcome


== Ideas ==
 
 
=== GRC: Build-in sub flowgraphs ===
 
GNU Radio has the hierarchical blocks to build reuseable sub flowgraphs. These hier_blocks can be designed in GRC, however, they have to be compiled to code and GRC bindings, before they can be used in other GRC files. While this is great for reuseablity across flowgraphs, it is quite cumbersome when the main use is to structure a single (larger) flowgraph. The goal of this project is to ease this use-case by embedding sub flowgraphs directly in the main GRC file. Instead of creating bindings and code and then parsing them back again, this process shall be done in-place to allow quickly editing sub flowgraphs on-the-fly. 
 
'''Prerequisites'''
 
* GRC is written in Python which is (almost) all you need to know for this project.
 
'''Outcome'''
 
* A vastly improved workflow for structuring flowgraphs
 
'''Mentor(s)'''
 
* Sebastian Koslowski
 




Line 26: Line 43:
Idea: Wrap the Qt GUI sinks to appear in QtCreator, including the GUI aspects of their parameterization
Idea: Wrap the Qt GUI sinks to appear in QtCreator, including the GUI aspects of their parameterization


==== Prerequisites ====
'''Prerequisites'''


* C++, Python proficiency
* C++, Python proficiency
* Qt experienced
* Qt experienced


==== Outcome ====
'''Outcome'''


* Qt GUI Sinks usable as widgets in QtCreator (not necessarily already showing an "empty" GUI, just placeholders)
* Qt GUI Sinks usable as widgets in QtCreator (not necessarily already showing an "empty" GUI, just placeholders)
Line 38: Line 55:
* Integration of that into GRC-generated Python code
* Integration of that into GRC-generated Python code


==== Mentor ====
'''Mentor(s)'''
 
* Marcus Müller & Sebastian "GRC-Man" Koslowski


Marcus Müller & Sebastian "GRC-Man" Koslowski




Line 47: Line 65:
When a flowgraph from an untrusted source is opened if GRC, arbitrary Python code can be executed. This poses a potential security risk. Storing the all evaluated values of all parameters within a flow graph (.grc) file would allow us to open such flow graphs without compromising security. No code would be have to executed to draw the flow graph and block parameters can be viewed safely. Only if the flow graph is modified the user would have to choose to trust the flow graph thus enabling normal eval operations.
When a flowgraph from an untrusted source is opened if GRC, arbitrary Python code can be executed. This poses a potential security risk. Storing the all evaluated values of all parameters within a flow graph (.grc) file would allow us to open such flow graphs without compromising security. No code would be have to executed to draw the flow graph and block parameters can be viewed safely. Only if the flow graph is modified the user would have to choose to trust the flow graph thus enabling normal eval operations.


===== Prerequisites =====
'''Prerequisites'''
 
GRC is implemented using Python. So, Python should be known pretty well.
 
===== Outcome =====
 
Safely view other people's flowgraphs without putting your PC at risk.
 
===== Mentor(s) =====
 
Sebastian Koslowski
 
 
 
 
=== GRC: Build-in sub flowgraphs ===
 
GNU Radio has the hierarchical blocks to build reuseable sub flowgraphs. These hier_blocks can be designed in GRC, however, they have to be compiled to code and GRC bindings, before they can be used in other GRC files. While this is great for reuseablity across flowgraphs, it is quite cumbersome when the main use is to structure a single (larger) flowgraph. The goal of this project is to ease this use-case by embedding sub flowgraphs directly in the main GRC file. Instead of creating bindings and code and then parsing them back again, this process shall be done in-place to allow quickly editing sub flowgraphs on-the-fly. 


===== Prerequisites =====
* GRC is implemented using Python. So, Python should be known pretty well.


GRC is written in Python which is (almost) all you need to know for this project.
'''Outcome'''


===== Outcome =====
* Safely view other people's flowgraphs without putting your PC at risk.


A vastly improved workflow for structuring flowgraphs
'''Mentor(s)'''


===== Mentor(s) =====
* Sebastian Koslowski


Sebastian Koslowski




Line 90: Line 90:
* Multi-antenna radar techniques
* Multi-antenna radar techniques


===== Prerequisites =====
'''Prerequisites'''


Signal processing and some radar basics are required. Code is written in C++ with some Python on the side, so the student must be able to handle these languages at the least.
* Signal processing and some radar basics are required.
* Code is written in C++ with some Python on the side, so the student must be able to handle these languages at the least.


===== Outcome =====
'''Outcome'''


Based on the student's interest, a subset of the radar techniques listed above (or others) are chosen as milestones for this project. All code must be merged back into gr-radar by the end of the summer.
* Based on the student's interest, a subset of the radar techniques listed above (or others) are chosen as milestones for this project.  
* All code must be merged back into gr-radar by the end of the summer.


===== Mentor(s) =====
'''Mentor(s)'''


Stefan Wunsch, Martin Braun
* Stefan Wunsch, Martin Braun




Line 124: Line 126:
** Allow to build full GUI applications from, say, GRC
** Allow to build full GUI applications from, say, GRC


===== Prerequisites =====
'''Prerequisites'''


Familiarity with QT is essential. Widgets are written in C+'', so some C''+ knowledge is also required. Python skills are highly useful.
* Familiarity with QT is essential.
* Widgets are written in C+'', so some C''+ knowledge is also required.
* Python skills are highly useful.


===== Mentor(s) =====
'''Mentor(s)'''


Tim O'Shea
Tim O'Shea
=== Standardized High Throughput FEC Codes ===
Channel coding is essential to modern communications. Also, it is computationally very heavy. As of now, there exist implementations in GNU Radio which are too slow to be integrated into high throughput applications. GNU Radio would benefit from integration of standardized decoders for Turbo and LDPC codes. These codes would only support a certain subset of the whole code class but would be well optimized.
'''Prerequisites'''
* Understanding of ''gr-fec'' API. Knowledge on channel coding. Understanding of C++.
'''Outcome'''
* Standardized Codes, e.g. LTE Turbo Codes, 5G Polar Codes, 5G LDPC Codes, CCITT Convolutional Codes etc. are available in ''gr-fec''.
* The preferred goal is to find a highly optimized implementation and integrate these into GNU Radio.
'''Mentor(s)'''
* Johannes Demel


=== Android ===
=== Android ===
Line 148: Line 173:
You can find a summary of the work that has been done on this (years ago) here: [[Android]]
You can find a summary of the work that has been done on this (years ago) here: [[Android]]


===== Prerequisites =====
'''Prerequisites'''


* Some Android experience
* Some Android experience
Line 154: Line 179:
* C++/Java experience
* C++/Java experience


===== Mentor(s) =====
'''Mentor(s)'''
 
* Ben Hilburn
 


Ben Hilburn


=== Filter Design Tool Enhancements ===
=== Filter Design Tool Enhancements ===
Line 171: Line 198:
** Better support for creating PFB filters
** Better support for creating PFB filters


===== Prerequisites =====
'''Prerequisites'''


Strong DSP background required. Python and QT knowledge highly useful (at least one of those is a must).
* Strong DSP background required.
* Python and QT knowledge highly useful (at least one of those is a must).
 
'''Mentor(s)'''
 
* Marcus Leech


===== Mentor(s) =====


Marcus Leech


=== Implement SigMF functionality for GNU Radio ===
=== Implement SigMF functionality for GNU Radio ===
Line 190: Line 220:
* Static analysis tools using SigMF
* Static analysis tools using SigMF


===== Prerequisites =====
'''Prerequisites'''
 
* Basic understanding of how to write GNU Radio blocks is required.
* Also, the student needs to explain that she or he has understood the concepts of SigMF, although SigMF is a very simple, JSON-based file format.
* Depending on the precise path that the student and the mentor define, experience in GUI development would also be useful.
 
'''Outcome'''


Basic understanding of how to write GNU Radio blocks is required. Also, the student needs to explain that she or he has understood the concepts of SigMF, although SigMF is a very simple, JSON-based file format.<br />
* The source and sink blocks are by the far the most important outcomes of this project. We estimate it would take about a third of the active coding time to implement those, and have them merged around the midterms.<br />
Depending on the precise path that the student and the mentor define, experience in GUI development would also be useful.
This leaves plenty of time for further development.
* The next most important task are the converters, so existing metadata files will continue to be useful. After that, the student should define own tasks based on their interests. A very relevant problem is the ability to effectively visualize metadata in combination with signals.


===== Outcome =====
'''Mentor(s)'''


The source and sink blocks are by the far the most important outcomes of this project. We estimate it would take about a third of the active coding time to implement those, and have them merged around the midterms.<br />
* Bastian Bloessl, Sebastian Müller
This leaves plenty of time for further development. The next most important task are the converters, so existing metadata files will continue to be useful. After that, the student should define own tasks based on their interests. A very relevant problem is the ability to effectively visualize metadata in combination with signals.


===== Mentor(s) =====


Bastian Bloessl, Sebastian Müller


=== Statistical Toolbox for GRC ===
=== Statistical Toolbox for GRC ===
Line 208: Line 242:
A statistical toolbox for GRC would enable GUI-based statistical analysis. Currently, such analysis can be done by writing an independent program (e.g., with Scipy), but there is no actual integration with GNU Radio. By developing the statistical toolbox, we provide blocks for probability distribution fitting, hypothesis testing, extracting statistical parameters for one-dimensional as well as multi-dimensional data. This would significantly expand GNU Radio users' ability to perform datascience analysis and modeling on signal data.
A statistical toolbox for GRC would enable GUI-based statistical analysis. Currently, such analysis can be done by writing an independent program (e.g., with Scipy), but there is no actual integration with GNU Radio. By developing the statistical toolbox, we provide blocks for probability distribution fitting, hypothesis testing, extracting statistical parameters for one-dimensional as well as multi-dimensional data. This would significantly expand GNU Radio users' ability to perform datascience analysis and modeling on signal data.


===== Prerequisites =====
'''Prerequisites'''


Understanding of existing GNU Radio tools (e.g., GRC), GNU Radio Out-of-Tree Modules, and statistics / datascience modeling.
* Understanding of existing GNU Radio tools (e.g., GRC), GNU Radio Out-of-Tree Modules, and statistics / datascience modeling.


===== Outcome =====
'''Outcome'''


An OOT module that provides statistical analysis capabilities for GNU Radio.
* An OOT module that provides statistical analysis capabilities for GNU Radio.


===== Mentor(s) =====
'''Mentor(s)'''


Ben Hilburn
* Ben Hilburn


=== Standardized High Throughput FEC Codes ===


Channel coding is essential to modern communications. Also, it is computationally very heavy. As of now, there exist implementations in GNU Radio which are too slow to be integrated into high throughput applications. GNU Radio would benefit from integration of standardized decoders for Turbo and LDPC codes. These codes would only support a certain subset of the whole code class but would be well optimized.
===== Prerequisites =====
Understanding of ''gr-fec'' API. Knowledge on channel coding. Understanding of C++.
===== Outcome =====
Standardized Codes, e.g. LTE Turbo Codes, 5G Polar Codes, 5G LDPC Codes, CCITT Convolutional Codes etc. are available in ''gr-fec''. The prefered goal is to find a highly optimized implementation and integrate these into GNU Radio.
===== Mentor(s) =====
Johannes Demel


=== Digital Pre-Distortion ===
=== Digital Pre-Distortion ===
Line 243: Line 262:
DPD is widely used and is increasingly necessary as many multicarrier signals such as what are seen in DVB and LTE exhibit high peak to average power ratios (PAPRs). DPD implementations are not widely available in the open source community. This is a deficit that this project hopes to correct. Over the course of the project the student would implement standard DPD algorithms in to a GNU Radio out of tree module so that they can be available for use directly or as reference designs.
DPD is widely used and is increasingly necessary as many multicarrier signals such as what are seen in DVB and LTE exhibit high peak to average power ratios (PAPRs). DPD implementations are not widely available in the open source community. This is a deficit that this project hopes to correct. Over the course of the project the student would implement standard DPD algorithms in to a GNU Radio out of tree module so that they can be available for use directly or as reference designs.


===== Prerequisites =====
'''Prerequisites'''


Workable C++ proficiency, basic knowledge of radio systems, ideally familiarity with GNU Radio and/or Digital Pre-Distortion
* Workable C++ proficiency, basic knowledge of radio systems, ideally familiarity with GNU Radio and/or Digital Pre-Distortion


===== Outcome =====
'''Outcome'''


* Implement standard memory-less and memory based DPD algorithms
* Implement standard memory-less and memory based DPD algorithms
Line 253: Line 272:
* Implement a GUI tool or testbench for viewing the AM-AM and AM-PM responses of an amplifier
* Implement a GUI tool or testbench for viewing the AM-AM and AM-PM responses of an amplifier


===== Mentor(s) =====
'''Mentor(s)'''
 
* Derek Kozel


Derek Kozel




== Application process ==
== Application process ==


* Students interested in participating, read the [[GSoCStudentInfo|student instructions]] and the [[GSoCManifest|rules of conduct]].
Students interested in participating, read the [[GSoCStudentInfo|student instructions]] and the [[GSoCManifest|rules of conduct]].
* Please introduce yourself on the [https://lists.gnu.org/mailman/listinfo/discuss-gnuradio GNU Radio mailing list]
* Please introduce yourself on the [https://lists.gnu.org/mailman/listinfo/discuss-gnuradio GNU Radio mailing list]
* Fill in the formal application for GNU Radio
* Fill in the formal application for GNU Radio
* Pick some items from the list above or feel free to suggest another piece of work relevant to this theme. Give us a detailed, week-by-week plan for completing the task over the summer.
* Pick some items from the list above or feel free to suggest another piece of work relevant to this theme. Give us a detailed, week-by-week plan for completing the task over the summer.

Revision as of 10:24, 26 January 2020

Summer of Code 2020: Project ideas list

This is the list of project ideas for the summer of code 2019 within GNU Radio.
Remember that these are ideas and are merely meant as an inspiration for you to write your own proposal.

Students who do not find a fit among these projects are encouraged to engage with us and suggest new ones. The GNU Radio discussion mailing list is the best place to contact all of us. Please do not contact us off-list for the sake of discussing the summer of code, unless you're contacting a mentor listed here to get feedback on a proposal.

Reviewing the Google GSoC FAQ page for a broader understanding of project, mentor, and student responsibilities is recommended.

If you need a USRP or other radio hardware to complete the project, we will be able to arrange something.

Please add ideas to this list (you may cannibalize old ideas, of course!).

Guidelines for good projects (when suggesting projects, please consider these):

  • Clearly defined scope, with a main target that can be done in 3 months
  • Clear benefits for the GNU Radio project
  • Not specific to a certain hardware. No specific embedded devices, either, please.
  • Both OOTs and in-tree improvements are welcome


GRC: Build-in sub flowgraphs

GNU Radio has the hierarchical blocks to build reuseable sub flowgraphs. These hier_blocks can be designed in GRC, however, they have to be compiled to code and GRC bindings, before they can be used in other GRC files. While this is great for reuseablity across flowgraphs, it is quite cumbersome when the main use is to structure a single (larger) flowgraph. The goal of this project is to ease this use-case by embedding sub flowgraphs directly in the main GRC file. Instead of creating bindings and code and then parsing them back again, this process shall be done in-place to allow quickly editing sub flowgraphs on-the-fly.

Prerequisites

  • GRC is written in Python which is (almost) all you need to know for this project.

Outcome

  • A vastly improved workflow for structuring flowgraphs

Mentor(s)

  • Sebastian Koslowski


Qt5 GUI Integrations

Idea: Wrap the Qt GUI sinks to appear in QtCreator, including the GUI aspects of their parameterization

Prerequisites

  • C++, Python proficiency
  • Qt experienced

Outcome

  • Qt GUI Sinks usable as widgets in QtCreator (not necessarily already showing an "empty" GUI, just placeholders)
  • Possible to import generate Qt GUI description file (UIC) into GRC
  • Interface to map placeholders from GUI design to Qt GUI sinks in Flow graph
  • Integration of that into GRC-generated Python code

Mentor(s)

  • Marcus Müller & Sebastian "GRC-Man" Koslowski


GRC: View-Only Mode (Secure)

When a flowgraph from an untrusted source is opened if GRC, arbitrary Python code can be executed. This poses a potential security risk. Storing the all evaluated values of all parameters within a flow graph (.grc) file would allow us to open such flow graphs without compromising security. No code would be have to executed to draw the flow graph and block parameters can be viewed safely. Only if the flow graph is modified the user would have to choose to trust the flow graph thus enabling normal eval operations.

Prerequisites

  • GRC is implemented using Python. So, Python should be known pretty well.

Outcome

  • Safely view other people's flowgraphs without putting your PC at risk.

Mentor(s)

  • Sebastian Koslowski


Extending and Updating gr-radar

gr-radar (https://github.com/kit-cel/gr-radar/) was a great and successful GSoC project that provided a few methods of radar in GNU Radio. This module is heavily used by academics, researchers, cybersecurity folks, and hobbyists. This project would work to improve upon the concepts already in there as well as add more radar techniques.

There are uncountable methods and techniques that could be added to this project, such as:

  • SAR / InSAR methods
  • Better passive radar support
  • Speed camera applications
  • Multi-antenna radar techniques

Prerequisites

  • Signal processing and some radar basics are required.
  • Code is written in C++ with some Python on the side, so the student must be able to handle these languages at the least.

Outcome

  • Based on the student's interest, a subset of the radar techniques listed above (or others) are chosen as milestones for this project.
  • All code must be merged back into gr-radar by the end of the summer.

Mentor(s)

  • Stefan Wunsch, Martin Braun


QT Widgets Improvements

The gr-qtgui in-tree component provides some QT widgets for signal visualization. This component needs some improvement to become more useful.
This project is cleanly divided into several sub-projects:

  • Add new widgets
    • Compass display (e.g. for direction-finding applications)
    • MPEG display (e.g. for video demod output)
    • Matrix sink (e.g. for radar Doppler/range plane visualization, or 2D-equalizer taps visualization)
  • Improve current widgets
    • Better code structure to make the current widgets more manageable, extensible and remove code duplication between widgets
    • More Control Panels on other widgets (follow lead on the frequency sink)
    • Improve UI, make more intuitive, more power to mouse users
    • Set trigger point with mouse
  • Integration / Support for QT Creator
    • QML design
    • Allow to build full GUI applications from, say, GRC

Prerequisites

  • Familiarity with QT is essential.
  • Widgets are written in C+, so some C+ knowledge is also required.
  • Python skills are highly useful.

Mentor(s)

Tim O'Shea


Standardized High Throughput FEC Codes

Channel coding is essential to modern communications. Also, it is computationally very heavy. As of now, there exist implementations in GNU Radio which are too slow to be integrated into high throughput applications. GNU Radio would benefit from integration of standardized decoders for Turbo and LDPC codes. These codes would only support a certain subset of the whole code class but would be well optimized.

Prerequisites

  • Understanding of gr-fec API. Knowledge on channel coding. Understanding of C++.

Outcome

  • Standardized Codes, e.g. LTE Turbo Codes, 5G Polar Codes, 5G LDPC Codes, CCITT Convolutional Codes etc. are available in gr-fec.
  • The preferred goal is to find a highly optimized implementation and integrate these into GNU Radio.

Mentor(s)

  • Johannes Demel


Android

One effort of the past years was to improve Android support for GNU Radio. We're getting to a point where we've figured out how to do it, so the next step is to make it more accessible to users and developers.

The Android ecosystem is an entirely different beast from the rest of GNU Radio. To make writing Android/GR apps easy, the following needs to happen (and shall be part of this project):

  • Improve support for development environment
    • Create Dockers for easy start of development
  • Visualization classes for PSD, spectrogram and oscilloscope
    • Easy reuse in other apps, like the gr-qtgui widgets, but for Android SDKs
  • Interactivity concepts
    • Gestures and config for radio params (e.g., freq, gain, bandwidth)
    • Create an example FM receiver app that allows easy channel selection etc. through motions and gestures

You can find a summary of the work that has been done on this (years ago) here: Android

Prerequisites

  • Some Android experience
  • Enjoy writing GUI widgets
  • C++/Java experience

Mentor(s)

  • Ben Hilburn


Filter Design Tool Enhancements

GNU Radio provides many tools to design and use digital filters. Using these tools requires both some expertise in these areas as well as an understanding of the performance on the given platform. One example is the selection between FIR (convolution-based) and FFT (fast convolution-based) filters for different resampling rates. Another example is doing stages of filter decomposition when doing large down-sampling. Included in this is the polyphase filterbanks, which again are provided as primitive blocks that need tweaking to work.

This project is to improve our uses of these tools and blocks to make it more obvious to the users as well as automate some of the decisions for optimally using them. Some pointers:

  • When used in GRC, we want to save the results of the tool in a local file or for use in actual blocks.
  • It still currently runs on PyQWT, which is obsolete and needs to be updated to QT4/QT5
  • Add more support for filter design concepts and other filters.
    • Cascaded filters
    • Better support for creating PFB filters

Prerequisites

  • Strong DSP background required.
  • Python and QT knowledge highly useful (at least one of those is a must).

Mentor(s)

  • Marcus Leech


Implement SigMF functionality for GNU Radio

SigMF is the "Signal Metadata Format" that was defined during the 2017 DARPA Hackfest in Brussels. Its purpose is to annotate raw binary dumps of signals with metadata, thus giving meaning to a raw mass of samples.
SigMF is specified and has a minimal reference implementation here: https://github.com/gnuradio/sigmf

GNU Radio needs its own implementation of SigMF that ties into the block structure. The following things need to be written:

  • Source and Sink blocks for SigMF (similar to the current metadata blocks)
  • Converters for files generated with the current metadata file formats
  • Static analysis tools using SigMF

Prerequisites

  • Basic understanding of how to write GNU Radio blocks is required.
  • Also, the student needs to explain that she or he has understood the concepts of SigMF, although SigMF is a very simple, JSON-based file format.
  • Depending on the precise path that the student and the mentor define, experience in GUI development would also be useful.

Outcome

  • The source and sink blocks are by the far the most important outcomes of this project. We estimate it would take about a third of the active coding time to implement those, and have them merged around the midterms.

This leaves plenty of time for further development.

  • The next most important task are the converters, so existing metadata files will continue to be useful. After that, the student should define own tasks based on their interests. A very relevant problem is the ability to effectively visualize metadata in combination with signals.

Mentor(s)

  • Bastian Bloessl, Sebastian Müller


Statistical Toolbox for GRC

A statistical toolbox for GRC would enable GUI-based statistical analysis. Currently, such analysis can be done by writing an independent program (e.g., with Scipy), but there is no actual integration with GNU Radio. By developing the statistical toolbox, we provide blocks for probability distribution fitting, hypothesis testing, extracting statistical parameters for one-dimensional as well as multi-dimensional data. This would significantly expand GNU Radio users' ability to perform datascience analysis and modeling on signal data.

Prerequisites

  • Understanding of existing GNU Radio tools (e.g., GRC), GNU Radio Out-of-Tree Modules, and statistics / datascience modeling.

Outcome

  • An OOT module that provides statistical analysis capabilities for GNU Radio.

Mentor(s)

  • Ben Hilburn


Digital Pre-Distortion

Digital Pre-Distortion (DPD) is a technique allowing transmitters to compensate for non-linear responses in their hardware, most notably the power amplifier. This improves SNR and can allow more spectral and power efficient operation of a given set of hardware.

DPD is widely used and is increasingly necessary as many multicarrier signals such as what are seen in DVB and LTE exhibit high peak to average power ratios (PAPRs). DPD implementations are not widely available in the open source community. This is a deficit that this project hopes to correct. Over the course of the project the student would implement standard DPD algorithms in to a GNU Radio out of tree module so that they can be available for use directly or as reference designs.

Prerequisites

  • Workable C++ proficiency, basic knowledge of radio systems, ideally familiarity with GNU Radio and/or Digital Pre-Distortion

Outcome

  • Implement standard memory-less and memory based DPD algorithms
  • Implement the training algorithms for such DPD application algorithms.
  • Implement a GUI tool or testbench for viewing the AM-AM and AM-PM responses of an amplifier

Mentor(s)

  • Derek Kozel


Application process

Students interested in participating, read the student instructions and the rules of conduct.

  • Please introduce yourself on the GNU Radio mailing list
  • Fill in the formal application for GNU Radio
  • Pick some items from the list above or feel free to suggest another piece of work relevant to this theme. Give us a detailed, week-by-week plan for completing the task over the summer.