| Conditions | 34 |
| Total Lines | 158 |
| Lines | 0 |
| Ratio | 0 % |
Small methods make your code easier to understand, in particular if combined with a good name. Besides, if your method is small, finding a good name is usually much easier.
For example, if you find yourself adding comments to a method's body, this is usually a good sign to extract the commented part to a new method, and use the comment as a starting point when coming up with a good name for this new method.
Commonly applied refactorings include:
If many parameters/temporary variables are present:
Complex classes like zipline.gens.AlgorithmSimulator._process_snapshot() often do a lot of different things. To break such a class down, we need to identify a cohesive component within that class. A common approach to find such a component is to look for fields/methods that share the same prefixes, or suffixes.
Once you have determined the fields that belong together, you can apply the Extract Class refactoring. If the component makes sense as a sub-class, Extract Subclass is also a candidate, and is often faster.
| 1 | # |
||
| 160 | list(algo.blotter.open_orders.keys()))) |
||
| 161 | |||
| 162 | if len(sids_we_care_about) > 0: |
||
| 163 | splits = data_portal.get_splits(sids_we_care_about, |
||
| 164 | midnight_dt) |
||
| 165 | if len(splits) > 0: |
||
| 166 | algo.blotter.process_splits(splits) |
||
| 167 | perf_tracker.position_tracker.handle_splits(splits) |
||
| 168 | |||
| 169 | def handle_benchmark(date): |
||
| 170 | algo.perf_tracker.all_benchmark_returns[date] = \ |
||
| 171 | self.benchmark_source.get_value(date) |
||
| 172 | |||
| 173 | with self.processor, ZiplineAPI(self.algo): |
||
| 174 | for dt, action in self.clock: |
||
| 175 | if action == BAR: |
||
| 176 | every_bar(dt) |
||
| 177 | elif action == DAY_START: |
||
| 178 | once_a_day(dt) |
||
| 179 | elif action == DAY_END: |
||
| 180 | # End of the day. |
||
| 181 | handle_benchmark(normalize_date(dt)) |
||
| 182 | yield self._get_daily_message(dt, algo, algo.perf_tracker) |
||
| 183 | elif action == MINUTE_END: |
||
| 184 | handle_benchmark(dt) |
||
| 185 | minute_msg, daily_msg = \ |
||
| 186 | self._get_minute_message(dt, algo, algo.perf_tracker) |
||
| 187 | |||
| 188 | yield minute_msg |
||
| 189 | |||
| 190 | if daily_msg: |
||
| 191 | yield daily_msg |
||
| 192 | |||
| 193 | risk_message = algo.perf_tracker.handle_simulation_end() |
||
| 194 | yield risk_message |
||
| 195 | |||
| 196 | @staticmethod |
||
| 197 | def _get_daily_message(dt, algo, perf_tracker): |
||
| 198 | """ |
||
| 199 | Get a perf message for the given datetime. |
||
| 200 | """ |
||
| 201 | perf_message = perf_tracker.handle_market_close_daily(dt) |
||
| 202 | perf_message['daily_perf']['recorded_vars'] = algo.recorded_vars |
||
| 203 | return perf_message |
||
| 204 | |||
| 205 | @staticmethod |
||
| 206 | def _get_minute_message(dt, algo, perf_tracker): |
||
| 207 | """ |
||
| 208 | Get a perf message for the given datetime. |
||
| 209 | """ |
||
| 210 | rvars = algo.recorded_vars |
||
| 211 | |||
| 212 | minute_message, daily_message = perf_tracker.handle_minute_close(dt) |
||
| 213 | minute_message['minute_perf']['recorded_vars'] = rvars |
||
| 214 | |||
| 215 | if daily_message: |
||
| 216 | daily_message["daily_perf"]["recorded_vars"] = rvars |
||
| 217 | |||
| 218 | return minute_message, daily_message |
||
| 219 |