Searched refs:importance (Results 1 – 18 of 18) sorted by relevance
36 importance, title = name38 importance, title = 'normal', name40 general_data[(importance, name)] = self.format_extra_data(41 importance, title, value)87 for (importance, name), value in general_data.items():88 data_by_importance[importance].append(210 def format_extra_data(self, importance, title, value): argument268 def format_extra_data(self, importance, title, value): argument
5 ; This tests the importance of keeping track of which types are part of the
53 performance, but hope that this will be of little importance for our
72 system somewhat reduce the importance of this point (f.e. portability
24 # permission weight value from 1 (less importance) to 10 (higher importance).
138 # holds. The explicit names are of no importance.
94 importance. To validate bzip2, I used a modified version of Mark
3013 double* importance; in get_var_importance() local3018 importance = var_importance->data.db; in get_var_importance()3031 importance[split->var_idx] += split->quality; in get_var_importance()
1309 importance
1570 ; and stores can even have ordering importance. Here we have a load which is
2308 of the received data is of non-negligible importance, null
3307 Reorder by "decreasing" order of importance.
6755 some text to clarify the relative importance of the new directives and
731 不當一回事 < not\-regard\-as\-a\-matter\-\(of\-any\-importance\);803 百年大計 < a\-project\-of\-vital\-and\-lasting\-importance;12227 重要性 < importance;21668 不當一回事 > not\-regard\-as\-a\-matter\-\(of\-any\-importance\);21999 百年大計 > a\-project\-of\-vital\-and\-lasting\-importance;24716 重要性 > importance;29897 重視 > importance;
1286 the importance of the message; you can control the verbosity of the
2673 importance is repeated here, so you won't have to constantly look
META-INF/ META-INF/MANIFEST.MF com/ com/android/ com/ ...