react18,Form.List 内容是Table,表格内表单,表单验证标红文字不显示
创作声明:本文部分内容由AI辅助生成(AIGC),仅供参考
Python内容推荐
【CEEMDAN-WOA-LSTM】完备集合经验模态分解-鲸鱼优化-长短时记忆神经网络研究(Python代码实现)
内容概要:本文研究了一种结合完备集合经验模态分解(CEEMDAN)、鲸鱼优化算法(WOA)和长短时记忆神经网络(LSTM)的复合预测模型,并提供了完整的Python代码实现。首先,利用CEEMDAN方法对原始非平稳时间序列信号进行自适应分解,获得一组更平稳的本征模态函数(IMF)分量,有效缓解模态混叠问题,从而降低预测复杂度;其次,引入鲸鱼优化算法(WOA)对LSTM网络的关键超参数(如学习率、隐层节点数、批次大小等)进行全局智能寻优,提升模型的泛化能力和收敛效率;最后,构建多变量输入的LSTM模型对各IMF分量分别进行时间序列建模与预测,并通过重构各分量得到最终的预测结果。该方法显著提高了在高噪声、非线性、非平稳环境下的时间序列预测精度,尤其适用于电力负荷、风电功率、气温等复杂能源系统预测任务。; 适合人群:具备Python编程基础,熟悉NumPy、Pandas、Scikit-learn及深度学习框架(如TensorFlow/PyTorch/Keras)的高校研究生、科研人员,以及从事能源系统预测、智能电网、信号处理、金融时序分析等相关领域的工程技术人员。; 使用场景及目标:①应用于电力系统中的短期负荷预测、可再生能源发电功率预测等高动态性、强波动性的时间序列建模任务;②为提升深度学习模型性能提供一种融合信号预处理与智能参数优化的整体解决方案;③作为智能优化算法与深度学习协同建模的典型范例,可用于教学示范、科研复现或工程项目原型开发。; 阅读建议:建议读者在学习过程中重点关注CEEMDAN的信号分解实现机制、WOA算法的数学原理与参数寻优流程,以及LSTM模型的结构设计与训练策略,结合所提供的完整代码逐模块调试运行,深入理解数据预处理、模型训练与结果后处理之间的逻辑衔接,进而可根据具体应用场景灵活迁移和优化该复合模型。
java面试问题汇总(非常全面)
本文档主要是针对java面试中一些常见的问题,希望大家共同学习
Visual C++ 编程资源大全(英文源码 控件)
1,01.zip<br>3D Text<br>显示3D文字(6KB)<END><br>2,02.zip<br>A button within a button<br>按纽中的按纽(13KB)<END><br>3,03.zip<br>Flat Owner Drawn Buttons<br>浮动的自画按纽(13KB)<END><br>4,04.zip<br>Flat-look Buttons <br>浮动的工具条按纽(6KB)<END><br>5,05.zip<br>Showing disabled combo text in black<br>ComboBox的只读属性(5KB)<END><br>6,06.zip<br>Combobox Color Picker <br>选择颜色的ComboBox(6KB)<END><br>7,07.zip<br>Switch between drop down & drop list mode <br>处理drop down和drop list方式之间的转换(32KB)<END><br>8,08.zip<br>Drop down a popdown window instead of a dropdown list from a combobox 在ComboBox中用Drop down方式代替dropdown list方式(32KB)<END><br>9,09.zip<br>Change listbox width of combo boxes<br>在ComboBox中改变列表框的宽度(2KB)<END><br>10,10.zip<br>Owner Drawn Font Selection ComboBox <br>自画的字体选择ComboBox(5KB)<END><br>11,add.zip<br>This sample was developed on stage at the Washington Software Association's WinSIG meeting on the ninth of September, 1996 using Visual C++ 4.2. (13KB)<END><br>12,apibrow.zip<br>The project demonstrates the use of common control callback items in an MFC applicationthat manages a CListCtrl control in a CListView. (16KB)<END><br>13,colorlb.zip<br>The COLORLB sample shows how to implement an owner-draw list box. (53KB)<END><br>14,comper.zip<br>COMPER is an example of the ATL Composite Control. (123KB)<END><br>15,custfile.zip<br>This sample shows how to add a couple of extra buttons to a CFileDialog. (23KB)<END><br>16,custlist.zip<br>CUSTLIST shows how to use custom draw in a list view control. (23KB)<END><br>17,div.zip<br>This sample shows how floating-point exceptions may be captured and handled in an MFC application. (14KB)<END><br>18,doodads.zip<br>The project demonstrates many Windows common controls, including the extensive use of image lists. (83KB)<END><br>19,doubleedit.zip<br>DOULBEEDIT shows how to sublcass an edit control inside a form view and react to double-clicks on the edit control by handling the WM_LBTNDOUBLECLICK message. (18KB)<END><br>20,dumpsome.zip<br>DUMPSOME is a project for Visual C++ 4.x that shows how to write a CGI server extension which uses MFC and DAO. (8KB)<END><br>21,edpos.zip<br>EDPOS is a MDI-based MFC application that shows an edit control in its primary view. (35KB)<END><br>22,edstream.zip<br>this sample shows how to use the StreamIn() and StreamOut() members of the CRichEditCtrl class in MFC. (36KB)<END><br>23,findrich.zip<br>RICHFIND is a dialog-based MFC application for Visual C++ 6.0. (24KB)<END><br>24,floatlist.zip<br>The FloatList sample is an MFC-based SDI application with an edit view as its main window. (49KB)<END><br>25,fully.zip<br>FULLY shows how to make an MFC application make one of its views go full-screen active. (43KB)<END><br>26,holder.zip<br>HOLDER contains the Internet Explorer web browser control using CHtmlView in an MFC application. (67KB)<END><br>27,langload.zip<br>LANGLOAD shows how to use the LANGUAGE keyword in a resource file to mark language-specific resources. (2KB)<END><br>28,listfind.zip<br>This sample shows how to use the CList<> template. (9KB)<END><br>29,ndbrow.zip<br>This Visual C++ 6 project shows how to create an MDI application that hosts CHtmlView (20KB)<END><br>30,mfctalk.zip<br>MFCTALK was originally published with Mike's article on ISPAI programming with MFC in the May (23KB)<END><br>31,mfctlist.zip<br>MCTTLIST is a dialog-based application that provides the same functionality as the TLIST sample in the SDK. (28KB)<END><br>32,mruless.zip<br>MRULESS shows a way to strip the empty "Recent Files" item off the "File" menu when there are no entries in the MRU. (32KB)<END><br>33,mtprint.zip<br>MTPRINT demonstrates the use of a secondary thread to perform printing in an application that uses MFC's document/view architecture. (21KB)<END><br>34,multitop.zip<br>MULTITOP shows how to write an SDI application which has multiple top level windows and uses the MFC doc/view architecture.(30KB)<END><br>35,njfind16.zip<br>This 16-bit DOS tool traverses all directories on all drives on your machine and finds files which match the template you specify. (33KB)<END><br>36,noform.zip<br>This sample shows how to make an application that doesn't have the doc/view architecture but still offers a form in the client area of the application's main window. (33KB)<END><br>37,odcombo.zip<br>ODCOMBO.ZIP is a VC++ 6.0 dialog-based project that contians an onwer-drawn combo box. (23KB)<END><br>38,picknew.zip<br>It demonstrates calling CDocTemplate::OpenDocumentFile(). (49KB)<END><br>39,primecon.zip<br>PrimeCon is a VC++ 6.0 sample which uses MFC in a console application.(60KB)<END><br>40,q1.zip<br>Q1 is a VC++ 6.0 project that creates two threads. (79KB)<END><br>41,scrl.zip<br>This dialog-based application shows how to use the CListCtrl::Scroll() member. (14KB)<END><br>42,spinrange.zip<br>SpinRange is a VC++ 6.0 project that shows how to subclass a CSpinButtonControl to dramatically extend the range of the control. (24KB)<END><br>43,splits.zip<br>This VC++ 5.0 project shows how to manage views within a splitter window. (36KB)<END><br>44,stealth.zip<br>This SDI application shows how to create an application that doesn't show up in the task bar in Windows 95 or Windows NT 4.0. (29KB)<END><br>45,tenhook.zip<br>Because the Windows dialog manager eats all keystrokes, you'll need to install a Windows keyboard hook if you want to get keyboard input to your dialog without other controls getting in the way. (19KB)<END><br>46,treestore.zip<br>Tree views are capable of storing hierarchical data, which isn't intuitively serialized. (41KB)<END><br>47,writeres.zip<br>This console application shows how to bake resources into console applications. (566KB)<END><br>48,xctrl.zip<br>The XCTRL sample is an ATL "full control" ATL Control. (100KB)<END><br>49,Button_Tute.zip<br>How to get a button control wired-in and working(34KB)<END><br>50,BetterBmpButton_src.zip<br>An improvement on the CBitmapButton class.(22KB)<END><br>51,hoverbutton.zip<br>A simple drop-in class that provides a 'hot' look button using the _TrackMouseEvent function(17KB)<END><br>52,CLedButton_src.zip<br>A button that looks like a LED.(24KB)<END><br>53,EllipticalButtons.zip<br>A class that turns rectangular buttons into elliptic buttons.(29KB)<END><br>54,RoundButtons.zip<br>A class that turns rectangular buttons into round buttons.(17KB)<END><br>55,AniButton.zip<br>A class that show AVIs inside a button.(49KB)<END><br>56,CButtonST26.zip<br>A fully featured owner-draw button class - it's got the lot!(225KB)<END><br>57,coolbtn.zip<br>This article shows the use of a Push button with a drop down menu, similar to the one found in the Office 2000 suite.(31KB)<END><br>58,CustomButtons.zip<br>A class to make working with radio buttons easier, and another for custom drawing buttons(45KB)<END><br>59,CWBButton.zip<br>CWBButton is a resizable bitmap button like GTK+ or Window Blinds.(44KB)<END><br>60,ComboDropWidth.zip<br>A simple tutorial explaining how to set the width of a combo dropdown list so that all items are fully visible(18KB)<END><br>61,ComboBox_Tut_demo.zip<br>An entry level tutorial on using the CComboBox control(65KB)<END><br>62,ListBox_Tut_src.zip<br>An entry level tutorial on using the CListBox control(62KB)<END><br>63,BitmapPickerCombo.zip<br>A combo box that can be used to display bitmaps(26KB)<END><br>64,mccombobox.zip<br>A multicolumn, customizable, editable combobox(27KB)<END><br>65,disableditemscombobox_src.zip<br>combobox with disabled items(3KB)<END><br>66,checkcombo.zip<br>A combo box with check boxes(21KB)<END><br>67,ColourPickerCB.zip<br>A combobox derived class that provides a simple color picker(36KB)<END><br>68,ComboBoxInit_src.zip<br>Learn how to programmatically initialize a combo box.(3KB)<END><br>69,IconComboBox_src.zip<br>2 Freeware MFC icon selection combo box classes(19KB)<END><br>70,ComboCompletion_demo.zip<br>A combobox that autocompletes as you type(17KB)<END><br>71,IDComboDemo.zip<br>An extremely simple but useful CComboBox entension(12KB)<END><br>72,MRUCombo.zip<br>A combobox that encapsulates the functionality of CRecentFileList(29KB)<END><br>73,combobox_flatcombo.zip<br>A drop-in replacement combobox that gives your apps the flat Office-style look(53KB)<END><br>74,readonlycombo_src.zip<br>Show a disabled dropdown style combobox like a read only edit box.(2KB)<END><br>75,VBLikeCombo.zip<br>Creates a combo box similar to those in Visual Basic.(27KB)<END><br>76,ComboTree.zip<br>ComboBox with a tree control drop down(36KB)<END><br>77,multichecklistbox.zip<br>Extends the CCheckListBox class to have multiple check box columns(19KB)<END><br>78,disableditemslistbox_src.zip<br>Listbox with disabled items.(2KB)<END><br>79,ImageLB.zip<br>A list box for viewing images(25KB)<END><br>80,LVCustomDraw.zip<br>Using the custom-draw features in version 4.70 of the common controls to customise the look and feel of list controls(28KB)<END><br>81,ListCtrlDemo.zip<br>Everything you need to know about using the standard list control in your applications(68KB)<END><br>82,filedroplistctrl.zip<br>This article explains how to support file drag and drop in your CWnd-derived object(40KB)<END><br>83,DrivePickerList.zip<br>A control that shows drive names and icons like Explorer(23KB)<END><br>84,ListEditor.zip<br>This article shows you how you can navigate through a multi-column, editable list view(42KB)<END><br>85,LogControl_src.zip<br>Learn how to use printf-like functionality to debug your GUI applications.(46KB)<END><br>86,PropertyListCtrl.zip<br>An object properties list control than can change based on the objects state.(64KB)<END><br>87,supergrid.zip<br>A combination list control and tree control with checkbox capability(87KB)<END><br>88,Listview_callback.zip<br>Shows how to use text callbacks in list controls(16KB)<END><br>89,HeaderCtrlEx.zip<br>How to make the CListCtrl's header Multiline(29KB)<END><br>90,listPrint_demo.zip<br>Printing the contents of a CListCtrl or CListView with multiple pages(56KB)<END><br>91,TreeListCtrlGerolf.zip<br>A custom-drawn tree-list hybrid, with explanations on how the control was developed.(39KB)<END><br>92,PrtTView_demo.zip<br>Code to add printing capabilities to a Tree View(32KB)<END><br>93,treelist.zip<br>A tree control / list control hybrid(81KB)<END><br>94,FileTree_src.zip<br>Implements a tree control similar to the left hand side of Windows Explorer.(46KB)<END><br>95,TreeOpt_src.zip<br>A freeware MFC class to provide a tree options control.(32KB)<END><br>96,ShTree.zip<br>A very simple manager for shared folders using tree control drag & drop (42KB)<END><br>97,NetworkTreeCtrl.zip<br>A CWaitingTreeCtrl-derived class to display network resources(40KB)<END><br>98,ProgressHourglassFX.zip<br>Two animation provider classes to add animation effects to any CWaitingTreeCtrl-derived class(33KB)<END><br>99,ShellTreeCtrl.zip<br>A CWaitingTreeCtrl-derived class to display Shell's resources(39KB)<END><br>100,WaitingTreeCtrl_src.zip<br>A CTreeCtrl derived class that populates the branches of a tree only when necessary, with optional visual effects.(5KB)<END><br>101,PathPicker.zip<br>An article on Browsing my computer and the network using a TreeCtrl(82KB)<END><br>102,Tree2Excel.zip<br>This article is a light sample showing how to iterate and export a tree control content to an Excel file.(44KB)<END><br>103,lbtab.zip<br>A better looking tab control(89KB)<END><br>104,CXTabControl_demo.zip<br>An easier tab control(32KB)<END><br>105,ResizableProperties.zip<br>Two CPropertySheet/CPropertyPage derived classes to implement resizable property sheets or wizard dialogs with MFC(96KB)<END><br>106,saprefs.zip<br>A base class for a prefereneces dialog, similar to that used in Netscape(39KB)<END><br>107,wizardpropertysheet_src.zip<br>A simply class to turn CPropertySheet into wizard mode without needing to alert the property pages within(2KB)<END><br>108,AutoRichEditCtrl.zip<br>CAutoRichEditCtrl - automate rich edit formatting and RTF handling(49KB)<END><br>109,AutomaticSplitter.zip<br>A tutorial that shows how to automatically split a view, and also how to indicate which view has the focus(31KB)<END><br>110,usefulsplitter.zip<br>An extension to MFCs CSplitterWnd that provides splitter locking and dynamic view replacement(25KB)<END><br>111,rulers_src.zip<br>Using fixed panes to add rulers to your view(5KB)<END><br>112,StaticCtrl_Tut_demo.zip<br>An entry level tutorial on using the CStatic control(64KB)<END><br>113,rotated_bevel.zip<br>A bevelline control that displays vertical and horizontal text(83KB)<END><br>114,Ticker.zip<br>A class that provides a news/stock ticker for your MFC applications(47KB)<END><br>115,StaticCounter.zip<br>A control to display time, floating point numbers or integers using an LED digital-style display(41KB)<END><br>116,CStaticTime.zip<br>A control to display times and numbers using an LED digital-style display(52KB)<END><br>117,alexf_histogram.zip<br>A simple histogram control for displaying data(23KB)<END><br>118,static_fader.zip<br>A CStatic class that gently fades text into view(99KB)<END><br>119,CLabel_demo.zip<br>A fully stocked owner drawn CStatic class(52KB)<END><br>120,DigiString.zip<br>A control to display text or numbers with a 14 or 7 segment display(176KB)<END><br>121,cstatic_filespec.zip<br>Lightweight class for displaying long filespecs that may need to be truncated(16KB)<END><br>122,tip_static.zip<br>A tip-of-the-day control that uses a cool sliding effect to show each tip(133KB)<END><br>123,UsingCtrlsInDialogs_Tut_demo.zip<br>An entry level tutorial on using one of the Windows Common Controls in a dialog(42KB)<END><br>124,CmdUIDemo.zip<br>A C++/MFC sample how to implement UI notifications for user-defined controls(15KB)<END><br>125,SubclassDemo.zip<br>An introduction to subclassing the Windows common controls using MFC(19KB)<END><br>126,CustomControl.zip<br>An introduction to creating custom controls using MFC(22KB)<END><br>127,graph2d.zip<br>A comprehensive set of classes for displaying 2 dimensional data(386KB)<END><br>128,3dMeter_demo.zip<br>An Analog Meter Control for displaying real-time data(42KB)<END><br>129,analog_meter.zip<br>A control that displays a numerical value as an analog meter(45KB)<END><br>130,oscope.zip<br>A control that graphically displays numerical information(31KB)<END><br>131,swing_demo.zip<br>A set of MFC classes the duplicate the Java Swing look and feel(76KB)<END><br>132,ReportCtrl.zip<br>An Outlook 98/2000 Style SuperGrid Report Control that tries to overcome some of the weaknesses of other implementations.(179KB)<END><br>133,controls_pager.zip<br>This article presents a wrapper class for the pager control(28KB)<END><br>134,RulerCtrl.zip<br>A simple ruler control to allow users to set margins or indents(21KB)<END><br>135,CSizer.zip<br>A class that provides the ability to move and size controls at run-time (34KB)<END><br>136,controls_avi_demo.zip<br>Demonstrates the use of the windows animation control(145KB)<END><br>137,CMapPin_src.zip<br>A Freeware MFC class to implement Map pins.(286KB)<END><br>138,CFCtrl.zip<br>The simplest way to change color, font or set blinking mode for any standard control(53KB)<END><br>139,CPushPin_src.zip<br>A Freeware MFC PushPin button class.(15KB)<END><br>140,CWndSlider.zip<br>An article on using an Outlook style window slider control.(98KB)<END><br>141,cxwndAnimate_demo.zip<br>An animation control that uses a bitmap imagelist instead of an AVI file(25KB)<END><br>142,hyperlink.zip<br>A simple drop-in hyperlink control(28KB)<END><br>143,ViewObjSnap.zip<br>How to take a snapshot of an OCX without using HWNDs.(38KB)<END><br>144,lbspin.zip<br>A spin button whose arrows automatically disable themselves when they are at their maximum or minimum value.(27KB)<END><br>145,SubclassWnd_demo.zip<br>A plug in class that allows you to intercept and handle messages for any window class(266KB)<END><br>146,resize_at_runtime_demo.zip<br>A method to allow the user to visually resize and position any control at run time(15KB)<END><br>147,RoundSliderCtrl.zip<br>A round slider control to allow users to adjust an angle or similar values(90KB)<END><br>148,EasyFavorite.zip<br>An application demonstrating the windows Thumbnail control(42KB)<END><br>149,TGroupBox.zip<br>A very simple group box replacement to enhance your user interface(3KB)<END><br>150,WndImg.zip<br>An easy-to-use control to display bitmaps (stretch, scale, tile)(128KB)<END><br>151,URLCell_src.zip<br>A new class that adds hyperlink support to the MFC Grid Control(3KB)<END><br>152,gridctrl.zip<br>A fully featured MFC grid control for displaying tabular data. The grid is a custom control derived from CWnd(381KB)<END><br>153,GridTreeCtrl.zip<br>A set of classes derived from CGridCtrl that embed a tree control, button controls, and virtual cells within the grid(221KB)<END><br>154,gridctrl_demo220.zip<br>Explains how to use comboboxes to edit cells in the MFC Grid Control(203KB)<END><br>155,AddHTMLy.zip<br>A quick and simple example of using MSHTML to modify the DOM(36KB)<END><br>156,Process_HTMLFORM.zip<br>A simple method to processing HTML forms From a CHtmlView(60KB)<END><br>157,ColorButton.zip<br>A simple modification to Chris Maunder's "Office 97 style Colour Picker" control(44KB)<END><br>158,ColorSpace_demo.zip<br>A replacement color picker control allowing you full visual control over RGB and HSB selections(288KB)<END><br>159,ColorDlg.zip<br>A simple color chooser dialog that uses slifer controls to allow the user to combine different RGB values(37KB)<END><br>160,choicelistbutton_demo.zip<br>A dropdown menu button with checkbox menu items(25KB)<END><br>161,HotList.zip<br>A control for selecting items from a list, with tool tips and mouse tracking(33KB)<END><br>162,colour_picker.zip<br>A simple drop in color chooser control(54KB)<END><br>163,progresswnd.zip<br>A popup window containing a progress control and cancel button - no resource file needed(34KB)<END><br>164,ProgressCtrlX.zip<br>An enhanced progress control that supports gradient shading, formatted text, 'snake' and reverse modes, and vertical modes(80KB)<END><br>165,GradientProgressCtrl.zip<br>Subclasses the standard CProgressCtrl to allow for gradient fills. Supports vertical progress controls as well.(52KB)<END><br>166,piectrl.zip<br>A progress control with a difference(149KB)<END><br>167,text_progressctrl_demo.zip<br>A smooth progress control with text(15KB)<END><br>168,ProgressBar.zip<br>An easy way to add a progress control to a status bar(33KB)<END><br>169,ProgressTimeToComplete.zip<br>A progress control that tells the user how long an operation has left to complete(26KB)<END><br>170,IProgressDialog_demo.zip<br>A wrapper class for the progress dialog provided by IE 5.(20KB)<END><br>171,rotary.zip<br>A rotary knob similar to that used in the Windows 2000 CD Player(67KB)<END><br>172,SizeDemo.zip<br>An MS-Word like drop down window for creating tables(37KB)<END><br>173,ToolTipEx.zip<br>A drop-in multiline extendable tooltip control(1052KB)<END><br>174,Multiline_Titletips_demo.zip<br>A class that allows you to display data for a control that is otherwise not large enough to display the full text(23KB)<END><br>175,CHtmlView_Search_demo.zip<br>Could be used to create a Visual C++ like search combo for CHtmlViews...<br>Update: Now you can highlight all matching words!(36KB)<END><br>176,AssociationGrid.zip<br>Grid control with vertical column headers.(85KB)<END><br>
a project model for the FreeBSD Project.7z
A project model for the FreeBSD Project Niklas Saers Copyright © 2002-2005 Niklas Saers [ Split HTML / Single HTML ] Table of Contents Foreword 1 Overview 2 Definitions 2.1. Activity 2.2. Process 2.3. Hat 2.4. Outcome 2.5. FreeBSD 3 Organisational structure 4 Methodology model 4.1. Development model 4.2. Release branches 4.3. Model summary 5 Hats 5.1. General Hats 5.1.1. Contributor 5.1.2. Committer 5.1.3. Core Team 5.1.4. Maintainership 5.2. Official Hats 5.2.1. Documentation project manager 5.2.2. CVSup Mirror Site Coordinator 5.2.3. Internationalisation 5.2.4. Postmaster 5.2.5. Quality Assurance 5.2.6. Release Coordination 5.2.7. Public Relations & Corporate Liaison 5.2.8. Security Officer 5.2.9. Source Repository Manager 5.2.10. Election Manager 5.2.11. Web site Management 5.2.12. Ports Manager 5.2.13. Standards 5.2.14. Core Secretary 5.2.15. GNATS Administrator 5.2.16. Bugmeister 5.2.17. Donations Liaison Officer 5.2.18. Admin 5.3. Process dependent hats 5.3.1. Report originator 5.3.2. Bugbuster 5.3.3. Mentor 5.3.4. Vendor 5.3.5. Reviewers 5.3.6. CVSup Mirror Site Admin 6 Processes 6.1. Adding new and removing old committers 6.2. Adding/Removing an official CVSup Mirror 6.3. Committing code 6.4. Core election 6.5. Development of new features 6.6. Maintenance 6.7. Problem reporting 6.8. Reacting to misbehaviour 6.9. Release engineering 7 Tools 7.1. Concurrent Versions System (CVS) 7.2. CVSup 7.3. GNATS 7.4. Mailman 7.5. Perforce 7.6. Pretty Good Privacy 7.7. Secure Shell 8 Sub-projects 8.1. The Ports Subproject 8.2. The FreeBSD Documentation Project References List of Figures 3-1. The FreeBSD Project's structure 3-2. The FreeBSD Project's structure with committers in categories 4-1. Jørgenssen's model for change integration 4-2. The FreeBSD release tree 4-3. The overall development model 5-1. Overview of official hats 6-1. Process summary: adding a new committer 6-2. Process summary: removing a committer 6-3. Process summary: adding a CVSup mirror 6-4. Process summary: A committer commits code 6-5. Process summary: A contributor commits code 6-6. Process summary: Core elections 6-7. Jørgenssen's model for change integration 6-8. Process summary: problem reporting 6-9. Process summary: release engineering 8-1. Number of ports added between 1996 and 2005 Foreword Up until now, the FreeBSD project has released a number of described techniques to do different parts of work. However, a project model summarising how the project is structured is needed because of the increasing amount of project members. [1] This paper will provide such a project model and is donated to the FreeBSD Documentation project where it can evolve together with the project so that it can at any point in time reflect the way the project works. It is based on [Saers, 2003]. I would like to thank the following people for taking the time to explain things that were unclear to me and for proofreading the document. Andrey A. Chernov <ache@freebsd.org> Bruce A. Mah <bmah@freebsd.org> Dag-Erling Smørgrav <des@freebsd.org> Giorgos Keramidas<keramida@freebsd.org> Ingvil Hovig <ingvil.hovig@skatteetaten.no> Jesper Holck<jeh.inf@cbs.dk> John Baldwin <jhb@freebsd.org> John Polstra <jdp@freebsd.org> Kirk McKusick <mckusick@freebsd.org> Mark Linimon <linimon@freebsd.org> Marleen Devos Niels Jørgenssen<nielsj@ruc.dk> Nik Clayton <nik@freebsd.org> Poul-Henning Kamp <phk@freebsd.org> Simon L. Nielsen <simon@freebsd.org> Chapter 1 Overview A project model is a means to reduce the communications overhead in a project. As shown by [Brooks, 1995], increasing the number of project participants increases the communication in the project exponentionally. FreeBSD has during the past few year increased both its mass of active users and committers, and the communication in the project has risen accordingly. This project model will serve to reduce this overhead by providing an up-to-date description of the project. During the Core elections in 2002, Mark Murray stated “I am opposed to a long rule-book, as that satisfies lawyer-tendencies, and is counter to the technocentricity that the project so badly needs.” [FreeBSD, 2002B]. This project model is not meant to be a tool to justify creating impositions for developers, but as a tool to facilitate coordination. It is meant as a description of the project, with an overview of how the different processes are executed. It is an introduction to how the FreeBSD project works. The FreeBSD project model will be described as of July 1st, 2004. It is based on the Niels Jørgensen's paper [Jørgensen, 2001], FreeBSD's official documents, discussions on FreeBSD mailing lists and interviews with developers. After providing definitions of terms used, this document will outline the organisational structure (including role descriptions and communication lines), discuss the methodology model and after presenting the tools used for process control, it will present the defined processes. Finally it will outline major sub-projects of the FreeBSD project. [FreeBSD, 2002A, Section 1.2 and 1.3] give the vision and the architectural guidelines for the project. The vision is “To produce the best UNIX-like operating system package possible, with due respect to the original software tools ideology as well as usability, performance and stability.” The architectural guidelines help determine whether a problem that someone wants to be solved is within the scope of the project Chapter 2 Definitions 2.1. Activity An “activity” is an element of work performed during the course of a project [PMI, 2000]. It has an output and leads towards an outcome. Such an output can either be an input to another activity or a part of the process' delivery. 2.2. Process A “process” is a series of activities that lead towards a particular outcome. A process can consist of one or more sub-processes. An example of a process is software design. 2.3. Hat A “hat” is synonymous with role. A hat has certain responsibilities in a process and for the process outcome. The hat executes activities. It is well defined what issues the hat should be contacted about by the project members and people outside the project. 2.4. Outcome An “outcome” is the final output of the process. This is synonymous with deliverable, that is defined as “any measurable, tangible, verifiable outcome, result or item that must be produced to complete a project or part of a project. Often used more narrowly in reference to an external deliverable, which is a deliverable that is subject to approval by the project sponsor or customer” by [PMI, 2000]. Examples of outcomes are a piece of software, a decision made or a report written. 2.5. FreeBSD When saying “FreeBSD” we will mean the BSD derivative UNIX-like operating system FreeBSD, whereas when saying “the FreeBSD Project” we will mean the project organisation. Chapter 3 Organisational structure While no-one takes ownership of FreeBSD, the FreeBSD organisation is divided into core, committers and contributors and is part of the FreeBSD community that lives around it. Figure 3-1. The FreeBSD Project's structure Number of committers has been determined by going through CVS logs from January 1st, 2004 to December 31st, 2004 and contributors by going through the list of contributions and problem reports. The main resource in the FreeBSD community is its developers: the committers and contributors. It is with their contributions that the project can move forward. Regular developers are referred to as contributors. As by January 1st, 2003, there are an estimated 5500 contributors on the project. Committers are developers with the privilege of being able to commit changes. These are usually the most active developers who are willing to spend their time not only integrating their own code but integrating code submitted by the developers who do not have this privilege. They are also the developers who elect the core team, and they have access to closed discussions. The project can be grouped into four distinct separate parts, and most developers will focus their involvement in one part of FreeBSD. The four parts are kernel development, userland development, ports and documentation. When referring to the base system, both kernel and userland is meant. This split changes our triangle to look like this: Figure 3-2. The FreeBSD Project's structure with committers in categories Number of committers per area has been determined by going through CVS logs from January 1st, 2004 to December 31st, 2004. Note that many committers work in multiple areas, making the total number higher than the real number of committers. The total number of committers at that time was 269. Committers fall into three groups: committers who are only concerned with one area of the project (for instance file systems), committers who are involved only with one sub-project and committers who commit to different parts of the code, including sub-projects. Because some committers work on different parts, the total number in the committers section of the triangle is higher than in the above triangle. The kernel is the main building block of FreeBSD. While the userland applications are protected against faults in other userland applications, the entire system is vulnerable to errors in the kernel. This, combined with the vast amount of dependencies in the kernel and that it is not easy to see all the consequences of a kernel change, demands developers with a relative full understanding of the kernel. Multiple development efforts in the kernel also requires a closer coordination than userland applications do. The core utilities, known as userland, provide the interface that identifies FreeBSD, both user interface, shared libraries and external interfaces to connecting clients. Currently, 162 people are involved in userland development and maintenance, many being maintainers for their own part of the code. Maintainership will be discussed in the Maintainership section. Documentation is handled by The FreeBSD Documentation Project and includes all documents surrounding the FreeBSD project, including the web pages. There were during 2004 101 people making commits to the FreeBSD Documentation Project. Ports is the collection of meta-data that is needed to make software packages build correctly on FreeBSD. An example of a port is the port for the web-browser Mozilla. It contains information about where to fetch the source, what patches to apply and how, and how the package should be installed on the system. This allows automated tools to fetch, build and install the package. As of this writing, there are more than 12600 ports available. [2] , ranging from web servers to games, programming languages and most of the application types that are in use on modern computers. Ports will be discussed further in the section The Ports Subproject. Chapter 4 Methodology model 4.1. Development model There is no defined model for how people write code in FreeBSD. However, Niels Jørgenssen has suggested a model of how written code is integrated into the project. Figure 4-1. Jørgenssen's model for change integration The “development release” is the FreeBSD-CURRENT ("-CURRENT") branch and the “production release” is the FreeBSD-STABLE branch ("-STABLE") [Jørgensen, 2001]. This is a model for one change, and shows that after coding, developers seek community review and try integrating it with their own systems. After integrating the change into the development release, called FreeBSD-CURRENT, it is tested by many users and developers in the FreeBSD community. After it has gone through enough testing, it is merged into the production release, called FreeBSD-STABLE. Unless each stage is finished successfully, the developer needs to go back and make modifications in the code and restart the process. To integrate a change with either -CURRENT or -STABLE is called making a commit. Jørgensen found that most FreeBSD developers work individually, meaning that this model is used in parallel by many developers on the different ongoing development efforts. A developer can also be working on multiple changes, so that while he is waiting for review or people to test one or more of his changes, he may be writing another change. As each commit represents an increment, this is a massively incremental model. The commits are in fact so frequent that during one year [3] , 85427 commits were made, making a daily average of 233 commits. Within the “code” bracket in Jørgensen's figure, each programmer has his own working style and follows his own development models. The bracket could very well have been called “development” as it includes requirements gathering and analysis, system and detailed design, implementation and verification. However, the only output from these stages is the source code or system documentation. From a stepwise model's perspective (such as the waterfall model), the other brackets can be seen as further verification and system integration. This system integration is also important to see if a change is accepted by the community. Up until the code is committed, the developer is free to choose how much to communicate about it to the rest of the project. In order for -CURRENT to work as a buffer (so that bright ideas that had some undiscovered drawbacks can be backed out) the minimum time a commit should be in -CURRENT before merging it to -STABLE is 3 days. Such a merge is referred to as an MFC (Merge From Current). It is important to notice the word “change”. Most commits do not contain radical new features, but are maintenance updates. The only exceptions from this model are security fixes and changes to features that are deprecated in the -CURRENT branch. In these cases, changes can be committed directly to the -STABLE branch. In addition to many people working on the project, there are many related projects to the FreeBSD Project. These are either projects developing brand new features, sub-projects or projects whose outcome is incorporated into FreeBSD [4]. These projects fit into the FreeBSD Project just like regular development efforts: they produce code that is integrated with the FreeBSD Project. However, some of them (like Ports and Documentation) have the privilege of being applicable to both branches or commit directly to both -CURRENT and -STABLE. There is no standards to how design should be done, nor is design collected in a centralised repository. The main design is that of 4.4BSD. [5] As design is a part of the “Code” bracket in Jørgenssen's model, it is up to every developer or sub-project how this should be done. Even if the design should be stored in a central repository, the output from the design stages would be of limited use as the differences of methodologies would make them poorly if at all interoperable. For the overall design of the project, the project relies on the sub-projects to negotiate fit interfaces between each other rather than to dictate interfacing. 4.2. Release branches The releases of FreeBSD is best illustrated by a tree with many branches where each major branch represents a major version. Minor versions are represented by branches of the major branches. In the following release tree, arrows that follow one-another in a particular direction represent a branch. Boxes with full lines and diamonds represent official releases. Boxes with dotted lines represent the development branch at that time. Security branches are represented by ovals. Diamonds differ from boxes in that they represent a fork, meaning a place where a branch splits into two branches where one of the branches becomes a sub-branch. For example, at 4.0-RELEASE the 4.0-CURRENT branch split into 4-STABLE and 5.0-CURRENT. At 4.5-RELEASE, the branch forked off a security branch called RELENG_4_5. Figure 4-2. The FreeBSD release tree The latest -CURRENT version is always referred to as -CURRENT, while the latest -STABLE release is always referred to as -STABLE. In this figure, -STABLE refers to 4-STABLE while -CURRENT refers to 5.0-CURRENT following 5.0-RELEASE. [FreeBSD, 2002E] A “major release” is always made from the -CURRENT branch. However, the -CURRENT branch does not need to fork at that point in time, but can focus on stabilising. An example of this is that following 3.0-RELEASE, 3.1-RELEASE was also a continuation of the -CURRENT-branch, and -CURRENT did not become a true development branch until this version was released and the 3-STABLE branch was forked. When -CURRENT returns to becoming a development branch, it can only be followed by a major release. 5-STABLE is predicted to be forked off 5.0-CURRENT at around 5.3-RELEASE. It is not until 5-STABLE is forked that the development branch will be branded 6.0-CURRENT. A “minor release” is made from the -CURRENT branch following a major release, or from the -STABLE branch. Following and including, 4.3-RELEASE[6], when a minor release has been made, it becomes a “security branch”. This is meant for organisations that do not want to follow the -STABLE branch and the potential new/changed features it offers, but instead require an absolutely stable environment, only updating to implement security updates. [7] Each update to a security branch is called a “patchlevel”. For every security enhancement that is done, the patchlevel number is increased, making it easy for people tracking the branch to see what security enhancements they have implemented. In cases where there have been especially serious security flaws, an entire new release can be made from a security branch. An example of this is 4.6.2-RELEASE. 4.3. Model summary To summarise, the development model of FreeBSD can be seen as the following tree: Figure 4-3. The overall development model The tree of the FreeBSD development with ongoing development efforts and continuous integration. The tree symbolises the release versions with major versions spawning new main branches and minor versions being versions of the main branch. The top branch is the -CURRENT branch where all new development is integrated, and the -STABLE branch is the branch directly below it. Clouds of development efforts hang over the project where developers use the development models they see fit. The product of their work is then integrated into -CURRENT where it undergoes parallel debugging and is finally merged from -CURRENT into -STABLE. Security fixes are merged from -STABLE to the security branches. Chapter 5 Hats Many committers have a special area of responsibility. These roles are called hats [Losh, 2002]. These hats can be either project roles, such as public relations officer, or maintainer for a certain area of the code. Because this is a project where people give voluntarily of their spare time, people with assigned hats are not always available. They must therefore appoint a deputy that can perform the hat's role in his or her absence. The other option is to have the role held by a group. Many of these hats are not formalised. Formalised hats have a charter stating the exact purpose of the hat along with its privileges and responsibilities. The writing of such charters is a new part of the project, and has thus yet to be completed for all hats. These hat descriptions are not such a formalisation, rather a summary of the role with links to the charter where available and contact addresses, 5.1. General Hats 5.1.1. Contributor A Contributor contributes to the FreeBSD project either as a developer, as an author, by sending problem reports, or in other ways contributing to the progress of the project. A contributor has no special privileges in the FreeBSD project. [FreeBSD, 2002F] 5.1.2. Committer A person who has the required privileges to add his code or documentation to the repository. A committer has made a commit within the past 12 months. [FreeBSD, 2000A] An active committer is a committer who has made an average of one commit per month during that time. It is worth noting that there are no technical barriers to prevent someone, once having gained commit privileges to the main- or a sub-project, to make commits in parts of that project's source the committer did not specifically get permission to modify. However, when wanting to make modifications to parts a committer has not been involved in before, he/she should read the logs to see what has happened in this area before, and also read the MAINTAINER file to see if the maintainer of this part has any special requests on how changes in the code should be made 5.1.3. Core Team The core team is elected by the committers from the pool of committers and serves as the board of directors of the FreeBSD project. It promotes active contributors to committers, assigns people to well-defined hats, and is the final arbiter of decisions involving which way the project should be heading. As by July 1st, 2004, core consisted of 9 members. Elections are held every two years. 5.1.4. Maintainership Maintainership means that that person is responsible for what is allowed to go into that area of the code and has the final say should disagreements over the code occur. This involves involves proactive work aimed at stimulating contributions and reactive work in reviewing commits. With the FreeBSD source comes the MAINTAINERS file that contains a one-line summary of how each maintainer would like contributions to be made. Having this notice and contact information enables developers to focus on the development effort rather than being stuck in a slow correspondence should the maintainer be unavailable for some time. If the maintainer is unavailable for an unreasonably long period of time, and other people do a significant amount of work, maintainership may be switched without the maintainer's approval. This is based on the stance that maintainership should be demonstrated, not declared. Maintainership of a particular piece of code is a hat that is not held as a group. 5.2. Official Hats The official hats in the FreeBSD Project are hats that are more or less formalised and mainly administrative roles. They have the authority and responsibility for their area. The following illustration shows the responsibility lines. After this follows a description of each hat, including who it is held by. Figure 5-1. Overview of official hats All boxes consist of groups of committers, except for the dotted boxes where the holders are not necessarily committers. The flattened circles are sub-projects and consist of both committers and non-committers of the main project. 5.2.1. Documentation project manager The FreeBSD Documentation Project architect is responsible for defining and following up documentation goals for the committers in the Documentation project. Hat held by: The DocEng team <doceng@FreeBSD.org>. The DocEng Charter. 5.2.2. CVSup Mirror Site Coordinator The CVSup Mirror Site Coordinator coordinates all the CVSup Mirror Site Admins to ensure that they are distributing current versions of the software, that they have the capacity to update themselves when major updates are in progress, and making it easy for the general public to find their closest CVSup mirror. Hat currently held by: John Polstra <jdp@FreeBSD.org>. 5.2.3. Internationalisation The Internationalisation hat is responsible for coordinating the localisation efforts of the FreeBSD kernel and userland utilities. The translation effort are coordinated by The FreeBSD Documentation Project. The Internationalisation hat should suggest and promote standards and guidelines for writing and maintaining the software in a fashion that makes it easier to translate. Hat currently available. 5.2.4. Postmaster The Postmaster is responsible for mail being correctly delivered to the committers' email address. He is also responsible for ensuring that the mailing lists work and should take measures against possible disruptions of mail such as having troll-, spam- and virus-filters. Hat currently held by: David Wolfskill <dhw@FreeBSD.org>. 5.2.5. Quality Assurance The responsibilities of this role are to manage the quality assurance measures. Hat currently held by: Robert Watson <rwatson@FreeBSD.org>. 5.2.6. Release Coordination The responsibilities of the Release Engineering Team are Setting, publishing and following a release schedule for official releases Documenting and formalising release engineering procedures Creation and maintenance of code branches Coordinating with the Ports and Documentation teams to have an updated set of packages and documentation released with the new releases Coordinating with the Security team so that pending releases are not affected by recently disclosed vulnerabilities. Further information about the development process is available in the release engineering section. Hat held by: the Release Engineering team <re@FreeBSD.org>, currently headed by Murray Stokely <murray@FreeBSD.org>. The Release Engineering Charter. 5.2.7. Public Relations & Corporate Liaison The Public Relations & Corporate Liaison's responsibilities are: Making press statements when happenings that are important to the FreeBSD Project happen. Being the official contact person for corporations that are working close with the FreeBSD Project. Take steps to promote FreeBSD within both the Open Source community and the corporate world. Handle the “freebsd-advocacy” mailing list. This hat is currently not occupied. 5.2.8. Security Officer The Security Officer's main responsibility is to coordinate information exchange with others in the security community and in the FreeBSD project. The Security Officer is also responsible for taking action when security problems are reported and promoting proactive development behaviour when it comes to security. Because of the fear that information about vulnerabilities may leak out to people with malicious intent before a patch is available, only the Security Officer, consisting of an officer, a deputy and two Core team members, receive sensitive information about security issues. However, to create or implement a patch, the Security Officer has the Security Officer Team <security-team@FreeBSD.org> to help do the work. Hat held by: the Security Officer <security-officer@FreeBSD.org>, currently headed by Colin Percival <cperciva@FreeBSD.org>. The Security Officer and The Security Officer Team's charter. 5.2.9. Source Repository Manager The Source Repository Manager is the only one who is allowed to directly modify the repository without using the CVS tool. It is his/her responsibility to ensure that technical problems that arise in the repository are resolved quickly. The source repository manager has the authority to back out commits if this is necessary to resolve a CVS technical problem. Hat held by: the Source Repository Manager <cvs@FreeBSD.org>, currently headed by Peter Wemm <peter@FreeBSD.org>. 5.2.10. Election Manager The Election Manager is responsible for the Core election process. The manager is responsible for running and maintaining the election system, and is the final authority should minor unforseen events happen in the election process. Major unforseen events have to be discussed with the Core team Hat held only during elections. 5.2.11. Web site Management The Web site Management hat is responsible for coordinating the rollout of updated web pages on mirrors around the world, for the overall structure of the primary web site and the system it is running upon. The management needs to coordinate the content with The FreeBSD Documentation Project and acts as maintainer for the “www” tree. Hat held by: the FreeBSD Webmasters <www@FreeBSD.org>. 5.2.12. Ports Manager The Ports Manager acts as a liaison between The Ports Subproject and the core project, and all requests from the project should go to the ports manager. Hat held by: the Ports Management Team <portmgr@FreeBSD.org>, 5.2.13. Standards The Standards hat is responsible for ensuring that FreeBSD complies with the standards it is committed to , keeping up to date on the development of these standards and notifying FreeBSD developers of important changes that allows them to take a proactive role and decrease the time between a standards update and FreeBSD's compliancy. Hat currently held by: Garrett Wollman <wollman@FreeBSD.org>. 5.2.14. Core Secretary The Core Secretary's main responsibility is to write drafts to and publish the final Core Reports. The secretary also keeps the core agenda, thus ensuring that no balls are dropped unresolved. Hat currently held by: Joel Dahl <joel@FreeBSD.org>. 5.2.15. GNATS Administrator The GNATS Administrator is responsible for ensuring that the maintenance database is in working order, that the entries are correctly categorised and that there are no invalid entries. Hat currently held by: Ceri Davies <ceri@FreeBSD.org> and Mark Linimon <linimon@FreeBSD.org>. 5.2.16. Bugmeister The Bugmeister is the person in charge of the problem report group. Hat currently held by: Ceri Davies <ceri@FreeBSD.org> and Mark Linimon <linimon@FreeBSD.org>. 5.2.17. Donations Liaison Officer The task of the donations liason officer is to match the developers with needs with people or organisations willing to make a donation. The Donations Liason Charter is available here Hat held by: the Donations Liaison Office <donations@FreeBSD.org>, currently headed by Michael W. Lucas <mwlucas@FreeBSD.org>. 5.2.18. Admin (Also called “FreeBSD Cluster Admin”) The admin team consists of the people responsible for administrating the computers that the project relies on for its distributed work and communication to be synchronised. It consists mainly of those people who have physical access to the servers. Hat held by: the Admin team <admin@FreeBSD.org>, currently headed by Mark Murray <markm@FreeBSD.org> 5.3. Process dependent hats 5.3.1. Report originator The person originally responsible for filing a Problem Report. 5.3.2. Bugbuster A person who will either find the right person to solve the problem, or close the PR if it is a duplicate or otherwise not an interesting one. 5.3.3. Mentor A mentor is a committer who takes it upon him/her to introduce a new committer to the project, both in terms of ensuring the new committers setup is valid, that the new committer knows the available tools required in his/her work and that the new committer knows what is expected of him/her in terms of behaviour. 5.3.4. Vendor The person(s) or organisation whom external code comes from and whom patches are sent to. 5.3.5. Reviewers People on the mailing list where the request for review is posted. 5.3.6. CVSup Mirror Site Admin A CVSup Mirror Site Admin has accesses to a server that he/she uses to mirror the CVS repository. The admin works with the CVSup Mirror Site Coordinator to ensure the site remains up-to-date and is following the general policy of official mirror sites. Chapter 6 Processes The following section will describe the defined project processes. Issues that are not handled by these processes happen on an ad-hoc basis based on what has been customary to do in similar cases. 6.1. Adding new and removing old committers The Core team has the responsibility of giving and removing commit privileges to contributors. This can only be done through a vote on the core mailing list. The ports and documentation sub-projects can give commit privileges to people working on these projects, but have to date not removed such privileges. Normally a contributor is recommended to core by a committer. For contributors or outsiders to contact core asking to be a committer is not well thought of and is usually rejected. If the area of particular interest for the developer potentially overlaps with other committers' area of maintainership, the opinion of those maintainers is sought. However, it is frequently this committer that recommends the developer. When a contributor is given committer status, he is assigned a mentor. The committer who recommended the new committer will, in the general case, take it upon himself to be the new committers mentor. When a contributor is given his commit bit, a PGP-signed email is sent from either Core Secretary, Ports Manager or nik@freebsd.org to both admins@freebsd.org, the assigned mentor, the new committer and core confirming the approval of a new account. The mentor then gathers a password line, SSH 2 public key and PGP key from the new committer and sends them to Admin. When the new account is created, the mentor activates the commit bit and guides the new committer through the rest of the initial process. Figure 6-1. Process summary: adding a new committer When a contributor sends a piece of code, the receiving committer may choose to recommend that the contributor is given commit privileges. If he recommends this to core, they will vote on this recommendation. If they vote in favour, a mentor is assigned the new committer and the new committer has to email his details to the administrators for an account to be created. After this, the new committer is all set to make his first commit. By tradition, this is by adding his name to the committers list. Recall that a committer is considered to be someone who has committed code during the past 12 months. However, it is not until after 18 months of inactivity have passed that commit privileges are eligible to be revoked. [FreeBSD, 2002H] There are, however, no automatic procedures for doing this. For reactions concerning commit privileges not triggered by time, see section 1.5.8. Figure 6-2. Process summary: removing a committer When Core decides to clean up the committers list, they check who has not made a commit for the past 18 months. Committers who have not done so have their commit bits revoked. It is also possible for committers to request that their commit bit be retired if for some reason they are no longer going to be actively committing to the project. In this case, it can also be restored at a later time by core, should the committer ask. Roles in this process: Core team Contributor Committer Maintainership Mentor [FreeBSD, 2000A] [FreeBSD, 2002H] [FreeBSD, 2002I] 6.2. Adding/Removing an official CVSup Mirror A CVSup mirror is a replica of the official CVSup master that contains all the up-to-date source code for all the branches in the FreeBSD project, ports and documentation. Adding an official CVSup mirror starts with the potential CVSup Mirror Site Admin installing the “cvsup-mirror” package. Having done this and updated the source code with a mirror site, he now runs a fairly recent unofficial CVSup mirror. Deciding he has a stable environment, the processing power, the network capacity and the storage capacity to run an official mirror, he mails the CVSup Mirror Site Coordinator who decides whether the mirror should become an official mirror or not. In making this decision, the CVSup Mirror Site Coordinator has to determine whether that geographical area needs another mirror site, if the mirror administrator has the skills to run it reliably, if the network bandwidth is adequate and if the master server has the capacity to server another mirror. If CVSup Mirror Site Coordinator decides that the mirror should become an official mirror, he obtains an authentication key from the mirror admin that he installs so the mirror admin can update the mirror from the master server. Figure 6-3. Process summary: adding a CVSup mirror When a CVSup mirror administrator of an unofficial mirror offers to become an official mirror site, the CVSup coordinator decides if another mirror is needed and if there is sufficient capacity to accommodate it. If so, an authorisation key is requested and the mirror is given access to the main distribution site and added to the list of official mirrors. Tools used in this process: CVSup SSH 2 Hats involved in this process: CVSup Mirror Site Coordinator CVSup Mirror Site Admin 6.3. Committing code The committing of new or modified code is one of the most frequent processes in the FreeBSD project and will usually happen many times a day. Committing of code can only be done by a “committer”. Committers commit either code written by themselves, code submitted to them or code submitted through a problem report. When code is written by the developer that is non-trivial, he should seek a code review from the community. This is done by sending mail to the relevant list asking for review. Before submitting the code for review, he should ensure it compiles correctly with the entire tree and that all relevant tests run. This is called “pre-commit test”. When contributed code is received, it should be reviewed by the committer and tested the same way. When a change is committed to a part of the source that has been contributed from an outside Vendor, the maintainer should ensure that the patch is contributed back to the vendor. This is in line with the open source philosophy and makes it easier to stay in sync with outside projects as the patches do not have to be reapplied every time a new release is made. After the code has been available for review and no further changes are necessary, the code is committed into the development branch, -CURRENT. If the change applies for the -STABLE branch or the other branches as well, a “Merge From Current” ("MFC") countdown is set by the committer. After the number of days the committer chose when setting the MFC have passed, an email will automatically be sent to the committer reminding him to commit it to the -STABLE branch (and possibly security branches as well). Only security critical changes should be merged to security branches. Delaying the commit to -STABLE and other branches allows for “parallel debugging” where the committed code is tested on a wide range of configurations. This makes changes to -STABLE to contain fewer faults and thus giving the branch its name. Figure 6-4. Process summary: A committer commits code When a committer has written a piece of code and wants to commit it, he first needs to determine if it is trivial enough to go in without prior review or if it should first be reviewed by the developer community. If the code is trivial or has been reviewed and the committer is not the maintainer, he should consult the maintainer before proceeding. If the code is contributed by an outside vendor, the maintainer should create a patch that is sent back to the vendor. The code is then committed and the deployed by the users. Should they find problems with the code, this will be reported and the committer can go back to writing a patch. If a vendor is affected, he can choose to implement or ignore the patch. Figure 6-5. Process summary: A contributor commits code The difference when a contributor makes a code contribution is that he submits the code through the send-pr program. This report is picked up by the maintainer who reviews the code and commits it. Hats included in this process are: Committer Contributor Vendor Reviewer [FreeBSD, 2001] [Jørgensen, 2001] 6.4. Core election Core elections are held at least every two years. [8] Nine core members are elected. New elections are held if the number of core members drops below seven. New elections can also be held should at least 1/3 of the active committers demand this. When an election is to take place, core announces this at least 6 weeks in advance, and appoints an election manager to run the elections. Only committers can be elected into core. The candidates need to submit their candidacy at least one week before the election starts, but can refine their statements until the voting starts. They are presented in the candidates list. When writing their election statements, the candidates must answer a few standard questions submitted by the election manager. During elections, the rule that a committer must have committed during the 12 past months is followed strictly. Only these committers are eligible to vote. When voting, the committer may vote once in support of up to nine nominees. The voting is done over a period of four weeks with reminders being posted on “developers” mailing list that is available to all committers. The election results are released one week after the election ends, and the new core team takes office one week after the results have been posted. Should there be a voting tie, this will be resolved by the new, unambiguously elected core members. Votes and candidate statements are archived, but the archives are not publicly available. Figure 6-6. Process summary: Core elections Core announces the election and selects an election manager. He prepares the elections, and when ready, candidates can announce their candidacies through submitting their statements. The committers then vote. After the vote is over, the election results are announced and the new core team takes office. Hats in core elections are: Core team Committer Election Manager [FreeBSD, 2000A] [FreeBSD, 2002B] [FreeBSD, 2002G] 6.5. Development of new features Within the project there are sub-projects that are working on new features. These projects are generally done by one person [Jørgensen, 2001]. Every project is free to organise development as it sees fit. However, when the project is merged to the -CURRENT branch it must follow the project guidelines. When the code has been well tested in the -CURRENT branch and deemed stable enough and relevant to the -STABLE branch, it is merged to the -STABLE branch. The requirements of the project are given by developer wishes, requests from the community in terms of direct requests by mail, Problem Reports, commercial funding for the development of features, or contributions by the scientific community. The wishes that come within the responsibility of a developer are given to that developer who prioritises his time between the request and his wishes. A common way to do this is maintain a TODO-list maintained by the project. Items that do not come within someone's responsibility are collected on TODO-lists unless someone volunteers to take the responsibility. All requests, their distribution and follow-up are handled by the GNATS tool. Requirements analysis happens in two ways. The requests that come in are discussed on mailing lists, both within the main project and in the sub-project that the request belongs to or is spawned by the request. Furthermore, individual developers on the sub-project will evaluate the feasibility of the requests and determine the prioritisation between them. Other than archives of the discussions that have taken place, no outcome is created by this phase that is merged into the main project. As the requests are prioritised by the individual developers on the basis of doing what they find interesting, necessary or are funded to do, there is no overall strategy or priorisation of what requests to regard as requirements and following up their correct implementation. However, most developers have some shared vision of what issues are more important, and they can ask for guidelines from the release engineering team. The verification phase of the project is two-fold. Before committing code to the current-branch, developers request their code to be reviewed by their peers. This review is for the most part done by functional testing, but also code review is important. When the code is committed to the branch, a broader functional testing will happen, that may trigger further code review and debugging should the code not behave as expected. This second verification form may be regarded as structural verification. Although the sub-projects themselves may write formal tests such as unit tests, these are usually not collected by the main project and are usually removed before the code is committed to the current branch. [9] 6.6. Maintenance It is an advantage to the project to for each area of the source have at least one person that knows this area well. Some parts of the code have designated maintainers. Others have de-facto maintainers, and some parts of the system do not have maintainers. The maintainer is usually a person from the sub-project that wrote and integrated the code, or someone who has ported it from the platform it was written for. [10] The maintainer's job is to make sure the code is in sync with the project the code comes from if it is contributed code, and apply patches submitted by the community or write fixes to issues that are discovered. The main bulk of work that is put into the FreeBSD project is maintenance. [Jørgensen, 2001] has made a figure showing the life cycle of changes. Figure 6-7. Jørgenssen's model for change integration Here “development release” refers to the -CURRENT branch while “production release” refers to the -STABLE branch. The “pre-commit test” is the functional testing by peer developers when asked to do so or trying out the code to determine the status of the sub-project. “Parallel debugging” is the functional testing that can trigger more review, and debugging when the code is included in the -CURRENT branch. As of this writing, there were 269 committers in the project. When they commit a change to a branch, that constitutes a new release. It is very common for users in the community to track a particular branch. The immediate existence of a new release makes the changes widely available right away and allows for rapid feedback from the community. This also gives the community the response time they expect on issues that are of importance to them. This makes the community more engaged, and thus allows for more and better feedback that again spurs more maintenance and ultimately should create a better product. Before making changes to code in parts of the tree that has a history unknown to the committer, the committer is required to read the commit logs to see why certain features are implemented the way they are in order not to make mistakes that have previously either been thought through or resolved. 6.7. Problem reporting FreeBSD comes with a problem reporting tool called “send-pr” that is a part of the GNATS package. All users and developers are encouraged to use this tool for reporting problems in software they do not maintain. Problems include bug reports, feature requests, features that should be enhanced and notices of new versions of external software that is included in the project. Problem reports are sent to an email address where it is inserted into the GNATS maintenance database. A Bugbuster classifies the problem and sends it to the correct group or maintainer within the project. After someone has taken responsibility for the report, the report is being analysed. This analysis includes verifying the problem and thinking out a solution for the problem. Often feedback is required from the report originator or even from the FreeBSD community. Once a patch for the problem is made, the originator may be asked to try it out. Finally, the working patch is integrated into the project, and documented if applicable. It there goes through the regular maintenance cycle as described in section maintenance. These are the states a problem report can be in: open, analyzed, feedback, patched, suspended and closed. The suspended state is for when further progress is not possible due to the lack of information or for when the task would require so much work that nobody is working on it at the moment. Figure 6-8. Process summary: problem reporting A problem is reported by the report originator. It is then classified by a bugbuster and handed to the correct maintainer. He verifies the problem and discusses the problem with the originator until he has enough information to create a working patch. This patch is then committed and the problem report is closed. The roles included in this process are: Report originator Maintainership Bugbuster [FreeBSD, 2002C]. [FreeBSD, 2002D] 6.8. Reacting to misbehaviour [FreeBSD, 2001] has a number of rules that committers should follow. However, it happens that these rules are broken. The following rules exist in order to be able to react to misbehaviour. They specify what actions will result in how long a suspension the committer's commit privileges. Committing during code freezes without the approval of the Release Engineering team - 2 days Committing to a security branch without approval - 2 days Commit wars - 5 days to all participating parties Impolite or inappropriate behaviour - 5 days [Lehey, 2002] For the suspensions to be efficient, any single core member can implement a suspension before discussing it on the “core” mailing list. Repeat offenders can, with a 2/3 vote by core, receive harsher penalties, including permanent removal of commit privileges. (However, the latter is always viewed as a last resort, due to its inherent tendency to create controversy). All suspensions are posted to the “developers” mailing list, a list available to committers only. It is important that you cannot be suspended for making technical errors. All penalties come from breaking social etiquette. Hats involved in this process: Core team Committer 6.9. Release engineering The FreeBSD project has a Release Engineering team with a principal release engineer that is responsible for creating releases of FreeBSD that can be brought out to the user community via the net or sold in retail outlets. Since FreeBSD is available on multiple platforms and releases for the different architectures are made available at the same time, the team has one person in charge of each architecture. Also, there are roles in the team responsible for coordinating quality assurance efforts, building a package set and for having an updated set of documents. When referring to the release engineer, a representative for the release engineering team is meant. When a release is coming, the FreeBSD project changes shape somewhat. A release schedule is made containing feature- and code-freezes, release of interim releases and the final release. A feature-freeze means no new features are allowed to be committed to the branch without the release engineers' explicit consent. Code-freeze means no changes to the code (like bugs-fixes) are allowed to be committed without the release engineers explicit consent. This feature- and code-freeze is known as stabilising. During the release process, the release engineer has the full authority to revert to older versions of code and thus "back out" changes should he find that the changes are not suitable to be included in the release. There are three different kinds of releases: .0 releases are the first release of a major version. These are branched of the -CURRENT branch and have a significantly longer release engineering cycle due to the unstable nature of the -CURRENT branch .X releases are releases of the -STABLE branch. They are scheduled to come out every 4 months. .X.Y releases are security releases that follow the .X branch. These come out only when sufficient security fixes have been merged since the last release on that branch. New features are rarely included, and the security team is far more involved in these than in regular releases. For releases of the -STABLE-branch, the release process starts 45 days before the anticipated release date. During the first phase, the first 15 days, the developers merge what changes they have had in -CURRENT that they want to have in the release to the release branch. When this period is over, the code enters a 15 day code freeze in which only bug fixes, documentation updates, security-related fixes and minor device driver changes are allowed. These changes must be approved by the release engineer in advance. At the beginning of the last 15 day period a release candidate is created for widespread testing. Updates are less likely to be allowed during this period, except for important bug fixes and security updates. In this final period, all releases are considered release candidates. At the end of the release process, a release is created with the new version number, including binary distributions on web sites and the creation of a CD-ROM images. However, the release is not considered "really released" until a PGP-signed message stating exactly that, is sent to the mailing list freebsd-announce; anything labelled as a "release" before that may well be in-process and subject to change before the PGP-signed message is sent. [11]. The releases of the -CURRENT-branch (that is, all releases that end with “.0”) are very similar, but with twice as long timeframe. It starts 8 weeks prior to the release with announcement of the release time line. Two weeks into the release process, the feature freeze is initiated and performance tweaks should be kept to a minimum. Four weeks prior to the release, an official beta version is made available. Two weeks prior to release, the code is officially branched into a new version. This version is given release candidate status, and as with the release engineering of -STABLE, the code freeze of the release candidate is hardened. However, development on the main development branch can continue. Other than these differences, the release engineering processes are alike. .0 releases go into their own branch and are aimed mainly at early adopters. The branch then goes through a period of stabilisation, and it is not until the Release Engineering Team> decides the demands to stability have been satisfied that the branch becomes -STABLE and -CURRENT targets the next major version. While this for the majority has been with .1 versions, this is not a demand. Most releases are made when a given date that has been deemed a long enough time since the previous release comes. A target is set for having major releases every 18 months and minor releases every 4 months. The user community has made it very clear that security and stability cannot be sacrificed by self-imposed deadlines and target release dates. For slips of time not to become too long with regards to security and stability issues, extra discipline is required when committing changes to -STABLE. Figure 6-9. Process summary: release engineering These are the stages in the release engineering process. Multiple release candidates may be created until the release is deemed stable enough to be released. [FreeBSD, 2002E] Chapter 7 Tools The major support tools for supporting the development process are CVS, CVSup, Perforce, GNATS, Mailman and OpenSSH. Except for CVSup, these are externally developed tools. These tools are commonly used in the open source world. 7.1. Concurrent Versions System (CVS) Concurrent Versions System or simply “CVS” is a system to handle multiple versions of text files and tracking who committed what changes and why. A project lives within a “repository” and different versions are considered different “branches”. 7.2. CVSup CVSup is a software package for distributing and updating collections of files across a network. It consists of a client program, cvsup, and a server program, cvsupd. The package is tailored specifically for distributing CVS repositories, and by taking advantage of CVS' properties, it performs updates much faster than traditional systems. 7.3. GNATS GNATS is a maintenance database consisting of a set of tools to track bugs at a central site. It supports the bug tracking process for sending and handling bugs as well as querying and updating the database and editing bug reports. The project uses one of its many client interfaces, “send-pr”, to send “Problem Reports” by email to the projects central GNATS server. The committers have also web and command-line clients available. 7.4. Mailman Mailman is a program that automates the management of mailing lists. The FreeBSD Project uses it to run 16 general lists, 60 technical lists, 4 limited lists and 5 lists with CVS commit logs. It is also used for many mailing lists set up and used by other people and projects in the FreeBSD community. General lists are lists for the general public, technical lists are mainly for the development of specific areas of interest, and closed lists are for internal communication not intended for the general public. The majority of all the communication in the project goes through these 85 lists [FreeBSD, 2003A, Appendix C]. 7.5. Perforce Perforce is a commercial software configuration management system developed by Perforce Systems that is available on over 50 operating systems. It is a collection of clients built around the Perforce server that contains the central file repository and tracks the operations done upon it. The clients are both clients for accessing the repository and administration of its configuration. 7.6. Pretty Good Privacy Pretty Good Privacy, better known as PGP, is a cryptosystem using a public key architecture to allow people to digitally sign and/or encrypt information in order to ensure secure communication between two parties. A signature is used when sending information out many recipients, enabling them to verify that the information has not been tampered with before they received it. In the FreeBSD Project this is the primary means of ensuring that information has been written by the person who claims to have written it, and not altered in transit. 7.7. Secure Shell Secure Shell is a standard for securely logging into a remote system and for executing commands on the remote system. It allows other connections, called tunnels, to be established and protected between the two involved systems. This standard exists in two primary versions, and only version two is used for the FreeBSD Project. The most common implementation of the standard is OpenSSH that is a part of the project's main distribution. Since its source is updated more often than FreeBSD releases, the latest version is also available in the ports tree. Chapter 8 Sub-projects Sub-projects are formed to reduce the amount of communication needed to coordinate the group of developers. When a problem area is sufficiently isolated, most communication would be within the group focusing on the problem, requiring less communication with the groups they communicate with than were the group not isolated. 8.1. The Ports Subproject A “port” is a set of meta-data and patches that are needed to fetch, compile and install correctly an external piece of software on a FreeBSD system. The amount of ports have grown at a tremendous rate, as shown by the following figure. Figure 8-1. Number of ports added between 1996 and 2005 Figure 8-1 is taken from the FreeBSD web site. It shows the number of ports available to FreeBSD in the period 1995 to 2005. It looks like the curve has first grown exponentionally, and then since the middle of 2001 grown linerly. As the external software described by the port often is under continued development, the amount of work required to maintain the ports is already large, and increasing. This has led to the ports part of the FreeBSD project gaining a more empowered structure, and is more and more becoming a sub-project of the FreeBSD project. Ports has its own core team with the Ports Manager as its leader, and this team can appoint committers without FreeBSD Core's approval. Unlike in the FreeBSD Project, where a lot of maintenance frequently is rewarded with a commit bit, the ports sub-project contains many active maintainers that are not committers. Unlike the main project, the ports tree is not branched. Every release of FreeBSD follows the current ports collection and has thus available updated information on where to find programs and how to build them. This, however, means that a port that makes dependencies on the system may need to have variations depending on what version of FreeBSD it runs on. With an unbranched ports repository it is not possible to guarantee that any port will run on anything other than -CURRENT and -STABLE, in particular older, minor releases. There is neither the infrastructure nor volunteer time needed to guarantee this. For efficiency of communication, teams depending on Ports, such as the release engineering team, have their own ports liaisons. 8.2. The FreeBSD Documentation Project The FreeBSD Documentation project was started January 1995. From the initial group of a project leader, four team leaders and 16 members, they are now a total of 44 committers. The documentation mailing list has just under 300 members, indicating that there is quite a large community around it. The goal of the Documentation project is to provide good and useful documentation of the FreeBSD project, thus making it easier for new users to get familiar with the system and detailing advanced features for the users. The main tasks in the Documentation project are to work on current projects in the “FreeBSD Documentation Set”, and translate the documentation to other languages. Like the FreeBSD Project, documentation is split in the same branches. This is done so that there is always an updated version of the documentation for each version. Only documentation errors are corrected in the security branches. Like the ports sub-project, the Documentation project can appoint documentation committers without FreeBSD Core's approval. [FreeBSD, 2003B]. The Documentation project has a primer. This is used both to introduce new project members to the standard tools and syntaxes and acts as a reference when working on the project. References [Brooks, 1995] Frederick P. Brooks, 1975, 1995, 0201835959, Addison-Wesley Pub Co, The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition). [Saers, 2003] Niklas Saers, 2003, A project model for the FreeBSD Project: Candidatus Scientiarum thesis. [Jørgensen, 2001] Niels Jørgensen, 2001, Putting it All in the Trunk: Incremental Software Development in the FreeBSD Open Source Project. [PMI, 2000] Project Management Institute, 1996, 2000, 1-880410-23-0, Project Management Institute, Pennsylvania, PMBOK Guide: A Guide to the Project Management Body of Knowledge, 2000 Edition. [FreeBSD, 2000A] 2002, Core Bylaws. [FreeBSD, 2002A] 2002, FreeBSD Developer's Handbook. [FreeBSD, 2002B] 2002, Core team election 2002. [Losh, 2002] Warner Losh, 2002, Working with Hats. [FreeBSD, 2002C] Dag-Erling Smørgrav and Hiten Pandya, 2002, The FreeBSD Documentation Project, Problem Report Handling Guidelines. [FreeBSD, 2002D] Dag-Erling Smørgrav, 2002, The FreeBSD Documentation Project, Writing FreeBSD Problem Reports. [FreeBSD, 2001] 2001, The FreeBSD Documentation Project, Committers Guide. [FreeBSD, 2002E] Murray Stokely, 2002, The FreeBSD Documentation Project, FreeBSD Release Engineering. [FreeBSD, 2003A] The FreeBSD Documentation Project, FreeBSD Handbook. [FreeBSD, 2002F] 2002, The FreeBSD Documentation Project, Contributors to FreeBSD. [FreeBSD, 2002G] 2002, The FreeBSD Project, Core team elections 2002. [FreeBSD, 2002H] 2002, The FreeBSD Project, Commit Bit Expiration Policy: 2002/04/06 15:35:30. [FreeBSD, 2002I] 2002, The FreeBSD Project, New Account Creation Procedure: 2002/08/19 17:11:27. [FreeBSD, 2003B] 2002, The FreeBSD Documentation Project, FreeBSD DocEng Team Charter: 2003/03/16 12:17. [Lehey, 2002] Greg Lehey, 2002, Greg Lehey, Two years in the trenches: The evolution of a software project. Notes [1] This goes hand-in-hand with Brooks' law that “adding another person to a late project will make it later” since it will increase the communication needs Brooks, 1995. A project model is a tool to reduce the communication needs. [2] Statistics are generated by counting the number of entries in the file fetched by portsdb by April 1st, 2005. portsdb is a part of the port sysutils/portupgrade. [3] The period from January 1st, 2004 to December 31st, 2004 was examined to find this number. [4] For instance, the development of the Bluetooth stack started as a sub-project until it was deemed stable enough to be merged into the -CURRENT branch. Now it is a part of the core FreeBSD system. [5] According to Kirk McKusick, after 20 years of developing UNIX operating systems, the interfaces are for the most part figured out. There is therefore no need for much design. However, new applications of the system and new hardware leads to some implementations being more beneficial than those that used to be preferred. One example is the introduction of web browsing that made the normal TCP/IP connection a short burst of data rather than a steady stream over a longer period of time. [6] The first release this actually happened for was 4.5-RELEASE, but security branches were at the same time created for 4.3-RELEASE and 4.4-RELEASE. [7] There is a terminology overlap with respect to the word "stable", which leads to some confusion. The -STABLE branch is still a development branch, whose goal is to be useful for most people. If it is never acceptable for a system to get changes that are not announced at the time it is deployed, that system should run a security branch. [8] The first Core election was held September 2000 [9] More and more tests are however performed when building the system &
基于进化多目标优化的多模态优化(EMO-MMO)的Matlab实现.rar
基于进化多目标优化的多模态优化(EMO-MMO)的Matlab实现.rar
科技中介服务机构如何提升服务效率并降低运营成本?.docx
科易网基于行业知识库+行业大数据+科技资源要素+AI模型,以AI,赋能技术转移、成果转化、技术经理人培训、知识产权管理、区域产业分析与布局、地方科技招商、创新创业大赛等场景,推出科技创新领域的AI工具、场景化服务和数智化解决方案,推动科技创新与产业创新智能化发展。
用于电力系统谐波抑制的无源谐波滤波器研究(Simulink仿真实现)
用于电力系统谐波抑制的无源谐波滤波器研究(Simulink仿真实现)内容概要:本文围绕电力系统中的谐波抑制问题,重点研究了无源谐波滤波器的设计与应用,并通过Simulink工具进行了系统建模仿真。文中详细阐述了无源滤波器的工作原理、结构设计及其在抑制特定次谐波方面的有效性,结合实际电力系统背景,分析了谐波产生的机理及对电网质量的影响。通过构建完整的仿真模型,验证了所设计滤波器在改善电流波形、降低总谐波畸变率(THD)等方面的性能表现,并对不同工况下的滤波效果进行了对比分析,体现了其在工程实践中的可行性与优越性。; 适合人群:具备电力系统、电气工程及其自动化等相关专业背景,熟悉Simulink仿真环境,从事电能质量治理、谐波分析与抑制研究的研究生、科研人员及工程技术人员。; 使用场景及目标:①掌握无源谐波滤波器的基本设计方法与参数选型原则;②学习利用Simulink搭建电力系统谐波分析与滤波仿真模型;③理解谐波抑制技术在实际电网中的应用场景与技术难点;④为后续开展有源滤波器(APF)或混合滤波系统研究奠定基础。; 阅读建议:建议读者结合文中提供的仿真模型结构图与关键参数设置,动手复现仿真过程,深入理解滤波器接入前后系统电流电压波形变化,重点关注FFT分析结果与THD指标的改善情况,同时可尝试调整负载类型或滤波支路参数以探究其对滤波性能的影响。
手眼标定工具,内参、双目标定
手眼标定工具,内参、双目标定
政府科技管理者如何精准识别重点产业的技术需求并推动成果转化?.docx
政府科技管理者如何精准识别重点产业的技术需求并推动成果转化?
产业园区运营负责人如何利用平台实现企业与科研机构的高效对接?.docx
科易网基于行业知识库+行业大数据+科技资源要素+AI模型,以AI,赋能技术转移、成果转化、技术经理人培训、知识产权管理、区域产业分析与布局、地方科技招商、创新创业大赛等场景,推出科技创新领域的AI工具、场景化服务和数智化解决方案,推动科技创新与产业创新智能化发展。
高校技术转移办公室人员如何提高科技成果的市场化识别效率?.docx
科易网基于行业知识库+行业大数据+科技资源要素+AI模型,以AI,赋能技术转移、成果转化、技术经理人培训、知识产权管理、区域产业分析与布局、地方科技招商、创新创业大赛等场景,推出科技创新领域的AI工具、场景化服务和数智化解决方案,推动科技创新与产业创新智能化发展。
电网不平衡下三相PWM整流器功率平衡控制仿真(Simulink仿真实现)
内容概要:本文针对电网不平衡条件下三相PWM整流器的功率平衡控制问题,提出并实现了有效的控制策略,旨在抑制因电网电压不对称引起的功率波动,提升系统运行的稳定性和电能质量。研究通过Simulink搭建完整的系统仿真模型,深入分析了不平衡电网下整流器的数学建模方法与控制目标,重点采用了双闭环控制结构、正负序分量分离技术和功率补偿机制,实现对有功与无功功率的精确调节。文中详细阐述了控制器的设计过程,包括电流内环与电压外环的协调控制、正负序电流的独立调节以及功率平衡算法的实现路径,最终通过仿真结果验证了所提控制策略在抑制功率脉动、维持直流侧电压稳定等方面的优异性能。; 适合人群:电气工程、自动化、电力电子与电力系统等相关专业的硕士、博士研究生,高等院校教师,以及从事新能源发电、电能质量治理和电力电子装置研发的工程技术人员。; 使用场景及目标:①为高校及科研机构开展复杂电网环境下电力电子变换器控制算法的研究提供理论依据与仿真验证平台;②指导工业界开发高性能、高可靠性的PWM整流器产品,特别是在风力发电、光伏并网、电机驱动等领域应对电网扰动的实际工程应用;③支撑相关领域科研项目的申报、高水平论文的撰写及关键技术攻关。; 阅读建议:建议读者结合提供的Simulink仿真模型进行实操学习,重点关注正负序分离模块、双闭环控制器参数整定及功率补偿环节的实现逻辑,可通过调整电网不平衡度、负载变化等工况,进一步测试控制系统的动态响应与鲁棒性,深化对控制机理的理解。
政府科技管理者在推动科技成果落地过程中,如何精准匹配企业与高校技术成果.docx
政府科技管理者在推动科技成果落地过程中,如何精准匹配企业与高校技术成果
【养老机构护理管理】基于C++与Qt的护理等级评估与变更记录系统设计 项目介绍 基于C++与Qt的养老机构护理等级评估与变更记录系统设计与实现(含模型描述及部分示例代码)
内容概要:本文介绍了一个基于C++与Qt开发的养老机构护理等级评估与变更记录系统的设计与实现。系统采用分层架构,涵盖界面层、业务服务层、算法层、数据访问层和文件服务层,利用SQLite实现本地结构化数据存储,支持老人信息管理、自动化评分、护理等级判定、变更审核、风险预警及历史追溯等功能。核心模型包括加权综合评分算法、护理等级映射规则、状态机驱动的变更审核流程以及基于规则的风险预警机制。系统通过事务机制保障数据一致性,支持CSV与MAT格式的数据导出,提升了评估的标准化、及时性与可追溯性,助力养老机构管理数字化转型。; 适合人群:具备C++编程基础、熟悉Qt框架和SQLite数据库的软件开发者或计算机专业学生,以及关注智慧养老系统设计的技术研究人员。; 使用场景及目标:①应用于养老机构实现护理等级的科学化、标准化评估与动态管理;②为智慧医疗类桌面应用开发提供可复用的架构设计与算法实现参考;③支持护理数据分析、趋势预测与管理决策的数据导出需求; 阅读建议:此资源包含完整的模型描述与关键代码示例,适合结合实际项目进行学习与二次开发,建议重点关注分层架构设计、事务处理机制与算法实现逻辑,并可根据实际业务需求调整评分权重、等级阈值与预警规则。
SpringBoot和Vue企业访客预约登记与门禁联动管理系统源码
包含前后端源码、SQL初始化脚本和启动说明。JDK 17、Spring Boot、Vue;默认H2演示数据库。
【顶级EI复现】新扩展移相角下的双有源桥DC-DC 变换器优化控制策略(Simulink仿真实现)
【顶级EI复现】新扩展移相角下的双有源桥DC-DC 变换器优化控制策略(Simulink仿真实现)内容概要:本文围绕“新扩展移相角下的双有源桥DC-DC变换器优化控制策略”展开研究,旨在通过Simulink仿真实现对现有控制策略的改进与复现。文章重点介绍了双有源桥(DAB)变换器的工作原理及其在电力电子系统中的关键作用,特别是在实现高效能量双向传输方面的优势。针对传统移相控制存在的软开关范围窄、回流功率大等问题,提出了一种新的扩展移相角控制策略,以拓宽零电压开关(ZVS)范围并降低系统损耗。文中详细阐述了该优化控制策略的设计思路、数学建模过程及仿真模型搭建方法,并通过Matlab/Simulink平台进行了仿真验证,展示了其在不同工况下的动态响应特性与稳态性能。结果表明,所提方法能有效提升变换器效率与功率密度,具有良好的工程应用前景。; 适合人群:从事电力电子、新能源变换系统、电力系统自动化等相关领域的科研人员与工程技术人员,尤其适合熟悉Matlab/Simulink仿真工具并有一定DC-DC变换器控制基础的研究生及高年级本科生。; 使用场景及目标:① 掌握双有源桥DC-DC变换器的基本拓扑结构与工作机理;② 学习并复现已发表于顶级EI期刊的先进控制策略;③ 利用Simulink进行电力电子系统建模与仿真,提升科研实践能力;④ 为后续开展更高阶的电力变换器优化控制研究提供技术储备。; 阅读建议:建议读者结合文中提供的仿真模型与关键参数设置,动手实践Simulink建模流程,重点关注控制逻辑的实现细节与波形分析,同时参考相关参考文献深入理解底层物理机制与数学推导过程。
用于计算系统状态的卡尔曼最优增益和最小均方误差(MMSE)估计研究(Matlab代码实现)
内容概要:本文围绕用于计算系统状态的卡尔曼最优增益和最小均方误差(MMSE)估计展开研究,系统阐述了卡尔曼滤波在动态系统状态估计中的核心作用。通过Matlab代码实现,详细展示了卡尔曼滤波算法中最优增益的递推计算过程与MMSE估计的数学推导,涵盖了状态预测、协方差更新、卡尔曼增益求解及状态修正等关键步骤。研究强调了算法在处理噪声干扰、提高状态估计精度方面的有效性,并结合具体算例验证了其实现过程与性能表现。; 适合人群:具备一定信号处理、控制理论或统计估计基础,从事自动化、电子信息、通信、导航等相关领域的科研人员及工程技术人员,尤其适合研究生及以上学历或有相关项目开发经验的专业人士。; 使用场景及目标:①深入理解卡尔曼滤波器的工作原理及其在状态估计中的数学本质;②掌握利用Matlab实现卡尔曼滤波算法的具体方法,应用于目标跟踪、导航系统、传感器融合、金融时间序列分析等实际工程问题;③为开展更复杂的扩展卡尔曼滤波(EKF)、无迹卡尔曼滤波(UKF)等非线性估计研究奠定基础。; 阅读建议:建议读者结合Matlab代码逐行调试,对照理论公式理解每一步的物理意义,并尝试修改系统模型参数或噪声水平以观察算法性能变化,从而加深对卡尔曼滤波鲁棒性与适应性的认识。
最优潮流二阶锥松弛在配电网最优潮流计算中的应用(Matlab代码实现)
内容概要:本文系统阐述了二阶锥松弛(Second-Order Cone Relaxation, SOCR)技术在配电网最优潮流(Optimal Power Flow, OPF)计算中的应用,并提供了基于Matlab的完整代码实现。针对配电网最优潮流问题所具有的非凸、非线性特性导致的传统算法易陷入局部最优、求解效率低下的难题,文章提出采用二阶锥松弛方法,通过将原始非凸的支路潮流方程精确松弛为二阶锥形式的约束条件,成功将原NP-hard问题转化为可在多项式时间内高效求解的二阶锥规划(SOCP)问题,从而能够可靠地获得全局最优解或高质量的紧致下界。文中详细论述了该松弛方法的数学建模过程、凸化原理、可行性判定准则及其在保证解的物理可行性方面的有效性,并利用标准IEEE配电系统算例进行了仿真验证,充分证明了该方法在计算速度、收敛鲁棒性和求解精度上的显著优势。; 适合人群:具备电力系统分析、现代优化理论(特别是凸优化)基础知识,以及熟练使用Matlab进行科学计算的研究生、高校科研人员和电力系统领域的工程师。; 使用场景及目标:①解决高比例分布式电源接入背景下配电网面临的复杂最优潮流计算与运行优化问题;②深入学习和掌握现代凸松弛技术(如SOCR、SDR)的理论精髓及其在电力系统非凸优化问题中的工程化应用方法,提升解决实际工程难题的能力; 阅读建议:在学习过程中,应紧密结合文中的数学推导与提供的Matlab代码,重点理解从非凸模型到凸模型的转化逻辑与实现技巧,建议动手复现所有算例,并尝试将其应用于不同的网络拓扑结构和运行工况,以全面评估该方法的适用范围、性能边界及潜在局限性。
ollama-latest-part-003
ollama-latest-part-003
高校技术转移办公室人员如何高效完成成果转化项目的评估与推荐?.docx
科易网基于行业知识库+行业大数据+科技资源要素+AI模型,以AI,赋能技术转移、成果转化、技术经理人培训、知识产权管理、区域产业分析与布局、地方科技招商、创新创业大赛等场景,推出科技创新领域的AI工具、场景化服务和数智化解决方案,推动科技创新与产业创新智能化发展。
最新推荐







